CMMI Blog Special Series: 4th Part: This blog series on the cmmiconsultantblog.com is a systematic and structured coverage of CMMI Process Areas starting from Maturity Level 2 to Maturity Level 3: using CMMI –DEV, Version 1.3, as the Reference CMMI Model: As CMMI Consultant, during CMMI Consulting assignment if you are asked about the inputs and outputs of Requirements Management (REQM) Process Area, what would be your response:

CMMI FAQ 0

18th July, 2015

For the above-mentioned question, CMMI consultants may take inputs from the following inputs.

The purpose of CMMI Process Area on Requirement Management Process (REQM) is to manage the project’s product and products component requirements. Requirements Management (REQM) involves the following:

• Establishing and maintaining an agreement with the customer on the requirements
• Managing changes to requirements
• Ensuring consistency between the requirements

Following are the Inputs for the CMMI Process Area on Requirements Management (REQM) are:

• Customer Requirements are received in form of Request for Proposal, Scope of Work, and Process Work Statement, etc.
• Signed off proposal / Contract Document
• Minutes of Meeting with the customer

Following are the Outputs created during the implementation of CMMI Process Area of Requirements Management:

• Software Requirements Specifications document
• Approval Mail/ Sign off mail from the customer
• Change request form
• Change Request Log
• Requirement Traceability Matrix

The above is not an exhaustive coverage of the Requirements Management (REQM), CMMI Process Areas but is substantive enough to create a good foundation of the Requirements Management process in an organization.

Source: CMMI for Development