CMMI - Level 2 - Requirement Management Part1

CMMI – Level 2 – Requirement Management   Part1

Process Areas in the Level 2 - Managed

• Requirement Management
• Project Planning
• Project Monitoring and Control
• Supplier Agreement Management
• Measurement and Analysis
• Process and Product Quality Assurance
• Configuration Management

PA Requirement Management

Specific Goal:
SG1 Manage Requirement

Specific Practices:
SP 1.1 Obtain an understanding of Requirements (a stage of static checking before requirement study)
      Sub-practices:

1. Define the criteria for distinguishing requirement provider.
2. Define the criteria for accepting the requirement.
3. Analyze requirement to see whether criteria is met.
4. Reach an understanding of the requirements.

    
      Typical Work Product:

1. Lists of criteria for distinguishing appropriate requirements provider.
2. Lists of criteria for accepting the requirements.
3. Results of analyses against criteria.
4. An agreed-to set of requirements.

SP 1.2 Obtain commitments to the requirements (requirement study stage)
      Sub-practices:

1. Assess the impact of requirements
2. Record the commitments

     Typical Work Product:

1. Requirements impact assessment
2. Requirements / Requirement changes commitment

SP 1.3 Manage Requirement Changes
      Sub-practices:

1. Record all requirements and requirement changes.
2. Record all changes history.
3. Evaluate the impact of the changes from the standpoint of the relevant stakeholders. (comments: this is mentioned in the official CMMI documents, but actually the practice actually has finished in SP2 seems no need to do it again in the SP 1.3)
4. Make the requirements and change data available to the project.



Typical Work Products

1. Requirement status
2. Requirement database
3. Requirement decision database

SP 1.4 Maintain Bidirectional Traceability of Requirements
 Sub-practice:

1. Maintain requirements traceability to ensure that the source of lower lever requirement is documented.
2. Maintain requirements traceability from a requirement to its derived requirements as well as to its allocation of functions, objects, people, processes and work product.
3. Maintain horizontal traceability from function to function.
4. Generate the requirements traceability matrix. (comments: duplicated with point 1,2,3)

     Typical Work Products

1. Requirements traceability matrix
2. Requirements tracking system

SP 1.5 Identify Inconsistencies between Project Work and Requirements
     Sub-practice:

1. Review the project plan, work products for consistency with the requirements and the changes made to them.
2. Identify the source of the inconsistency.
3. Identify changes need to be done on project plan, work product based on the requirements changes.
4. Take the corrective actions.

     Typical Work Products

1. Documentation of inconsistencies in project plan and work product.
2. Documentation of the corrective actions.

The above documents can be included in the system analyze document.