CMM - L 2 - Repeatable - Requirement Management

Requirement Management

The purpose of Requirements Management is to establish a common understanding between the customer and the project team.

Requirements Management involves establishing and maintaining an agreement with the customer on the requirements for the software project. This agreement is referred to as the "system requirements allocated to the software." To achieve this control, the software engineering group reviews the initial and revised system requirements allocated to software to resolve issues before they are incorporated into the software project. Whenever the system requirements allocated to software are changed, the affected software plans, work products, and activities are adjusted to remain consistent with the updated requirements
Please note Software Engineering Group means the project team.

There are two goals in this KPA:

Goal 1: System requirements allocated to software are controlled to establish a baseline for software engineering and management use.

Goal 2: Software plans, products, and activities are kept consistent with the system requirements allocated to software

If we look at the various activities that are performed, the summary is as below:

The software requirements are reviewed by the team, and the requirements are used as the basis for further planning. Any changes to the requirements are reviewed. (Impact analysis, Change management process). Change cannot be avoided, but the impact to the schedule and plan must be comprehended and managed.

Next - Software Project Planning