Requirements OverviewRequirements development is a set of activities that will produce requirements for the system and sub-systems. The systems engineering standard [EIA 632] defines “requirement” as “something that governs what, how well, and under what conditions a product will achieve a given purpose.” Requirements define the functions, performance, and environment of the system under development to a level that can be built:

In the Department of Defense (DoD) the requirements process is governed by the Joint Capabilities Integration and Development System (JCIDS) Process. The JCIDS Process ensures the capabilities required by the DoD are identified and their functional and performance requirements are developed. The main engineering disciple that develops and controls requirements development is Systems Engineering (SE). Requirements development is Step One: Requirements Analysis of the Systems Engineering Process. The four (4) main requirements documents that are produced on a typical DoD program during a specific Acquisition Phase are:

Actual Requirements Development
There is no set standard way to develop requirements but they are normally developed follow the same basic six (6) steps. These requirements development steps don’t really change depending on which SE model is used. All models are similar in their approach but they just usually depict the step differently graphically. The main model that is used is the Systems Engineering “Vee” where requirements development is depicted on the left side. Below is a list of the basic steps of requirements development.

Other topics that Stakeholders, Program Manager (PM) and Systems Engineers need to know about Requirements Development are:

AcqLinks and References:

Updated: 7/27/2017

Print Friendly, PDF & Email