You are here:

Six steps of requirements engineering


Requirements engineering is a sub-process of the systems engineering process.

Step One of this procedure is Requirements Development. There are six essential processes to developing requirements that don’t alter regardless on which model is utilized. In terms of methodology, all models are comparable. They just represent them graphically in a new way.

Above you can see a graphical step by step visualisation of the process.

Step 1: Gather & Develop Requirements

Gathering, analyzing, and developing requirements from the Concept of Operations (CONOPS), stakeholder needs, objectives, and other external requirements is the first step. Following the documentation of requirements, they are prioritized, de-conflicted, and validated with stakeholders.

Step 2: Write and Document Requirements

The second phase is to record the functional and performance requirements in the relevant requirements documents, such as the Initial Capabilities Document (ICD), Capability Development Document (CDD), Capability Production Document (CPD), and System Requirements Document (SRD). Requirements must be specified in order to create a baseline from which to develop a system and manage any modifications. For DoD initiatives, the Capability Development Tracking and Manager (CDTM) tool can be used to establish requirements.

Step 3: Check Completeness

The third step is to verify that a complete set of requirements has been developed and documented that defines all the system functionality and its associated performance, environmental, and other non-functional requirements needed to satisfy the stakeholder needs. Requirements tracking is an important tool in this step.

Step 4: Analyze, Refine, and Decompose Requirements

Requirements analysis is the first major step in the systems engineering process. In this step, each requirement is examined to determine if it meets the attributes of a good requirement. Each requirement is then decomposed into a refined set of requirements that are assigned to subsystems and documented in the Weapon System Specification (WSS). Newly derived requirements are expected to emerge from this process, which continues until all requirements are defined and analyzed.

Step 5: Verify and Validate Requirements

In the fifth step, each requirement must be verified and confirmed to ensure that they are the correct requirements. This ensures that the requirements meet the overall goals of the system and the needs of all stakeholders.


Step 6: Manage Requirements

In the sixth step, the requirements are accepted and a baseline is created by the stakeholders. All changes to requirements are controlled through the configuration management process.

Next Steps in the Systems Engineering Process Next Systems Engineering Step: Functional Analysis and Mapping Functional analysis and mapping is the top-down process of translating just-developed system-level requirements into detailed functional and performance design criteria. The result of this process is a defined architecture with associated system requirements traceable to each system function.




At databyte, we live this process in every project! Because we are convinced that only with a solid analysis can successful results be achieved.

Contact us today to talk about your project. We look forward to hearing from you!