Requirement management

Requirement management

Itteratief requirement proces

The requirement proces

Requirements template

• PROJECT DRIVERS:
  1. The Purpose of the Product
  2. Client, Customer, Stakeholders
  3. Users of the Product
• PROJECT CONSTRAINTS:
  1. Mandated Constraints
  2. Naming Conventions and Definitions
  3. Relevant Facts and Assumptions
• FUNCTIONAL REQUIREMENTS:
  1. The Scope of the Work
  2. The Scope of the Product
  3. Functional and Data Requirements
• NON-FUNCTIONAL REQUIREMENTS:
  1. Look and Feel
  2. Usability and Humanity
  3. Performance
  4. Operational
  5. Maintainability and Support
  6. Security
  7. Cultural and Political
  8. Legal
• PROJECT ISSUES:
  1. Open Issues
  2. Off-the-shelf Solutions
  3. New Problems
  4. Tasks
  5. Migration to the New Product
  6. Risks
  7. Costs
  8. User Documentation
  9. Waiting Room
  10. Ideas for Solutions

Snow card

- `Requirement #`: Unique identifier
- `Requirement type`: One of the types in the Volère template
- `Event / use case #`: Events or use cases based upon this requirement
- `Description`: Natural language intent of the requirement
- `Rationale`: (Business) reason behind requirement’s existence
- `Originator`: Stakeholder who raised the requirement
- `Fit criterion`: Acceptance criterion (SMART) for the solution
- `Customer satisfaction`: The degree of happiness if this requirement is implemented
- `Customer dissatisfaction`: The degree of unhappiness if this requirement is not implemented
- `Conflicts`: Requirements conflicting with this one
- `Supporting materials`: Documentation like rules and regulations and so on
- `History`: When is the requirement created and updated by whom