Volere

A mindmap to collect and structure information in the early stages of a project based on the Volere Template by the Atlantic Systems Guild. Please check out their website for more details and license restrictions on the use of the template.

Get Started. It's Free
or sign up with your email address
Rocket clouds
Volere by Mind Map: Volere

1. Project Drivers

1.1. 1. The Purpose of the Project

1.1.1. 1a. The User Business or Background of the Project Effort

1.1.2. 1b. Goals of the Project

1.2. 2. The Client, the Customer, and Other Stakeholders

1.2.1. 2a. The Client

1.2.2. 2b. The Customer

1.2.3. 2c. Other Stakeholders

1.3. 3. Users of the Product

1.3.1. 3a. The Hands-On Users of the Product

1.3.2. 3b. Priorities Assigned to Users

1.3.3. 3c. User Participation

1.3.4. 3d. Maintenance Users and Service Technicians

2. Project Constraints

2.1. 4. Mandated Constraints

2.1.1. 4a. Solution Constraints

2.1.2. 4b. Implementation Environment of the Current System

2.1.3. 4c. Partner or Collaborative Applications

2.1.4. 4d. Off-the-Shelf Software

2.1.5. 4e. Anticipated Workplace Environment

2.1.6. 4f. Schedule Constraints

2.1.7. 4g. Budget Constraints

2.2. 5. Naming Conventions and Definitions

2.2.1. 5a. Definitions of All Terms, Including Acronyms, Used in the Project

2.2.2. 5b. Data Dictionary for Any Included Models

2.3. 6. Relevant Facts and Assumptions

2.3.1. 6a. Facts

2.3.2. 6b. Assumptions

3. Functional Requirements

3.1. 7. The Scope of the Work

3.1.1. 7a. The Current Situation

3.1.2. 7b. The Context of the Work

3.1.3. 7c. Work Partitioning

3.2. 8. The Scope of the Product

3.2.1. 8a. Product Boundary

3.2.2. 8b. Product Use Case List

3.2.3. 8c. Individual Product Use Cases

3.3. 9. Functional and Data Requirements

3.3.1. 9a. Functional Requirements

3.3.2. 9b. Data Requirements

4. Non Functional Requirements

4.1. 10. Look and Feel Requirements

4.1.1. 10a. Appearance Requirements

4.1.2. 10b. Style Requirements

4.2. 11. Usability and Humanity Requirements

4.2.1. 11a. Ease of Use Requirements

4.2.2. 11b. Personalization and Internationalization Requirements

4.2.3. 11c. Learning Requirements

4.2.4. 11d. Understandability and Politeness Requirements

4.2.5. 11e. Accessibility Requirements

4.3. 12. Performance Requirements

4.3.1. 12a. Speed and Latency Requirements

4.3.2. 12b. Safety-Critical Requirements

4.3.3. 12c. Precision or Accuracy Requirements

4.3.4. 12d. Reliability and Availability Requirements

4.3.5. 12e. Robustness or Fault-Tolerance Requirements

4.3.6. 12f. Capacity Requirements

4.3.7. 12g. Scalability or Extensibility Requirements

4.3.8. 12h. Longevity Requirements

4.4. 13. Operational and Environmental Requirements

4.4.1. 13a. Expected Physical Environment

4.4.2. 13b. Requirements for Interfacing with Adjacent Systems

4.4.3. 13c. Productization Requirements

4.4.4. 13d. Release Requirements

4.5. 14. Maintainability and Support Requirements

4.5.1. 14a. Maintenance Requirements

4.5.2. 14b. Supportability Requirements

4.5.3. 14c. Adaptability Requirements

4.6. 15. Security Requirements

4.6.1. 15a. Access Requirements

4.6.2. 15b. Integrity Requirements

4.6.3. 15c. Privacy Requirements

4.6.4. 15d. Audit Requirements

4.6.5. 15e. Immunity Requirements

4.7. 16. Cultural and Political Requirements

4.7.1. 16a. Cultural Requirements

4.7.2. 16b. Political Requirements

4.8. 17. Legal Requirements

4.8.1. 17a. Compliance Requirements

4.8.2. 17b. Standards Requirements

5. Project Issues

5.1. 18. Open Issues

5.2. 19. Off-the-Shelf Solutions

5.2.1. 19a. Ready-Made Products

5.2.2. 19b. Reusable Components

5.2.3. 19c. Products That Can Be Copied

5.3. 20. New Problems

5.3.1. 20a. Effects on the Current Environment

5.3.2. 20b. Effects on the Installed Systems

5.3.3. 20c. Potential User Problems

5.3.4. 20d. Limitations in the Anticipated Implementation Environment That May Inhibit the New Product

5.3.5. 20e. Follow-Up Problems

5.4. 21. Tasks

5.4.1. 21a. Project Planning

5.4.2. 21b. Planning of the Development Phases

5.5. 22. Migration to the New Product

5.5.1. 22a. Requirements for Migration to the New Product

5.5.2. 22b. Data That Has to Be Modified or Translated for the New System

5.6. 23. Risks

5.7. 24. Costs

5.8. 25. User Documentation and Training

5.8.1. 25a. User Documentation Requirements

5.8.2. 25b. Training Requirements

5.9. 26. Waiting Room

5.10. 27. Ideas for Solutions