CMMI for Acquisition Blog Special Series: 01st 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–ACQ, 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 Acquisition Requirements Development (ARD) Process Area, what would be your response

CMMI FAQ 0

16th February, 2017

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

Acquisition Requirements Development (ARD) process area is to collect, study and examine the requirements of the end user and the requirements mentioned in the contract.

Activities

Acquisition Requirements Development involves the following activities

• Develop the end user/customer requirements by collecting them with different methods, prioritizing them
• Establish contractual requirements and allocate them to relevant stakeholders
• To maintain the balance, conduct the analysis of requirements by establishing the details of the operations and functionality using scenarios and concepts
• Also validate the requirements using different methods like simulations, prototyping, demonstrations etc.

Inputs

Following are some examples of input to the Acquisition Requirements Development:

• Contract
• Statement of Work
• Request for Proposal (RFP)
• Details of stakeholders

Outputs

Outputs created during the implementation of the Acquisition Requirements Development activities are as under:

• Response to RFP
• Software Requirement Specification Document, Use cases
• Prototype, Demo of the functionality
• Prioritized customer/contractual requirements
• Details of Customer constraints on the conduct of verification/validations
• Details of Internal/External interface
• Risk assessment conducted for requirements
• Proposed requirements changes

The above is not an exhaustive coverage of the Acquisition Requirements Development (ARD) CMMI Process Area but is substantive enough to create a good foundation of the Acquisition Requirements Development process in an organization.