Requirements

graph TD
    RN("Receive stakeholder needs"):::sh --> GR("Gather requirements"):::lead
    GR --> TP("Test plan development"):::engr
    TP --> ReqApproval{"Lead approval"}:::lead
    ReqApproval --> |Revision<br/>required| GR
    ReqApproval --> |Approved| ReqOK[[Design]]

    click ReqOK "/process/design/"

    classDef lead fill:green,opacity:0.6,stroke:darkgreen,stroke-width:2px,color:black
    classDef engr fill:dodgerblue,opacity:0.6,stroke:navy,stroke-width:2px,color:black
    classDef sh fill:orange,opacity:0.6,stroke:darkorange,stroke-width:2px,color:black

Requirements answer the question: what does the system need to do? It does not answer the question of how does the system do this?

The requirements process is dependent on the objectives and therefore determined on a per-project basis. Yet, the following general process still applies:

  1. Engineers define requirements with the help of stakeholders.
  2. Leads review these requirements, and iterate with engineers and other stakeholders as needed until each requirement is approved.
  3. Test plans for each requirement is designed at the same time as requirements are defined: if a requirement cannot be tested, it isn't a requirement.

The Lead, the stakeholders and the program schedule will determine which requirements fit in which version, and each version guides the development cycle. As such, requirements shall be decomposed into small enough work units to allow for iterative development.

Last update: 2022-10-03