CMMI Blog Special Series: 8th 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 steps, inputs and outputs of Requirements Development (RD) Process Area, what would be your response:

CMMI FAQ 0

21st September, 2015

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

The purpose of Requirements Development (RD) Process Area of CMMI ML 3 is to elicit, analyze and establish customer, product and product component requirements.

Requirements Management process area also works with RD to Manage Requirements, Changes to Requirements and Traceability to ensure alignment of work products.

Requirements are the basis for design in development projects. This process area addresses all customer requirements including implicit, explicit requirements and other requirements related to responsiveness, safety, reliability and maintainability, etc., rather than only product level requirements.

The Requirements Development (RD) process area describes three types of requirements:

• Customer Requirements
• Product Requirements
• Product Component Requirements.

Examples of inputs for the Requirements Development process area are:

• Sign – Off Proposal / Contract Document / Statement of Work
• Request For Proposal (RFP) document
• Project Management Plan (PMP)
• Technical Solution Document

Examples of Outputs of RD process area

• Software Requirement Specification (SRS)
• Functional Requirement Specification (FRS) document
• Review Sheet of SRS / FRS
• Acceptance Test Results.

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

Source: CMMI for Development