Requirements Development

Requirements Management

Requirements Management is the process of documenting, analyzing, tracing, prioritizing, and controlling changes to requirements. It’s a continuous process and is conducted throughout a system’s life cycle and confirmed at each technical review.

Purpose of Requirements Management

The purpose is to assure that the requirements continue to meet the needs and expectations of its customers and stakeholders. [2]

Benefits of Requirements Management

  • Improved quality control
  • Reduced life-cycle costs
  • decrease in item defects
  • Increase schedule reliability
  • Easier Traceability
  • Increased stakeholder confidence
  • better configuration management

Requirements Management Plan (RMP)

The requirements management plan (RMP) details how the program manager and project personnel will receive, analyze, document, control, and manage all the requirements on a program.  The plan will define the project objectives, documentation process, requirements analyzing, tracing, prioritization, and controlling. The RMP will also detail the gathering process, roles and responsibilities, tools, and traceability.

Requirements Management Process


Requirements should be documented throughout a program from concept development thru disposal. Requirements in the DoD are documented in the:

Requirements should be maintained in a relational database, numbering standards, or other methods that show relationships. There are a number of relational databases on the market that systems engineers can use that include:


The goal of requirements analysis is to determine the needs that make up a system to satisfy an overall need from the customer. It examines, evaluates, and translates needs into a set of functional and performance requirements that are the basis for the Functional Analysis and Allocation.


DoD Requirements Management provides traceability back to user-defined capabilities documented in the Initial Capabilities Document (ICD), Capability Development Document (CDD), and Capability Production Document (CPD). A good requirements management system should allow for traceability from the lowest level component in the Weapons System Specification (WSS) all the way back to the ICD. Relational databases are a good tool in doing this. The Program Manager (PM) and Chief Systems Engineer should institute a Requirements Management process to do the following: [1]

  • Maintain the traceability of all requirements from capabilities needs through design and test,
  • Document all changes to those requirements, and
  • Record the rationale for those changes


One characteristic of excellent requirements management is that the requirements are prioritized. When customer expectations are high, timelines are short, and resources are limited, a program manager wants to make sure the system contains the most essential requirements. These requirements are expressed as:

AcqLinks and References:

Updated: 8/2/2021

Rank: G32

Leave a Reply