Task: Create and Validate Output Requirements
This task describe the necessary steps to generate and validate output requirements that the development team need to produce for its level.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

There are two sets of output requirements that must be generated:

  • Requirements to the lower level
  • Requirements to other team(s) at the same level

Each of these sets of requirements must be of appropriate quality, use consistent terminology, and must be complete in that they must satisfy all the input requirements. They must be traced back to the input requirements so that impact analysis can be performed as part of change management. The requirements must be organised in such a way that it is clear for whom each requirement is intended. The process does not define how to do this, but possible approaches include pre-allocation, appropriate section headings in a single document (specification) or individual specifications targeted at particular groups.

Once the output requirements are generated, the development team is also responsible for validating the requirements. There are many ways in which validation can be accomplished, of which the most common (but not the only way), is to use reviews. The first thing is to prepare a validation plan and then executes it to generate the appropriate evidence of validation. Validation must check on the quality and completeness of the requirements. It must ensure that all input requirements have been met and that there are no output requirements that cannot be justified by tracing them back to one or more input requirements.

The following sections will discuss the details for the steps taken in this task.

Create Requirements for Lower Level:

Working from the Input Requirements to this level and the design material, create requirements for the development teams at the level below. These requirements must be placed in an appropriate specification structure together with appropriate descriptive material and assumptions.

As each requirement is written, identify which of the Input Requirements to this level it addresses, so that a traceability matrix can be created.

Often these requirements will be collected into groups that are specifically targeted (allocated) at a specific lower level team. Alternatively, the set of requirements will be produced as a single set and then allocated to teams during the Agree requirements from this level process.

Create requirements for the lower level

Create requirements for the lower level

Create Requirements for Other Team(s):

Development teams must provide information to the other development teams. These requirements are primarily derived from the Design material, but also take note of the input requirements to this level. As each requirement is written, identify which of the Input Requirements to this level it addresses, so that a traceability matrix can be created.

Create requirements for other team

Create requirements for other team

Validate Requirements:

There are several aspects to requirement validation. Validation includes the following:

  • Ensuring that output requirements from this level are individually correct.
  • Ensuring that the output requirements from this level are contextually correct and together are necessary and sufficient to satisfy the requirements that are input to this level.
  • Ensuring that output requirements from this level are properly traced back to the input requirements to this level.
  • Ensuring that the Product Verification and Integration Verification plans are sensible and appropriate for each requirement.

There are several facets to the validation of a requirement and clearly not all of these can be achieved in the early stages of a project. Therefore, it is important that a phased approach be taken. It is assumed in the rest of this process description that the initial approval from the level above can be obtained when only the first three of the above items are present.

There is a need for a standard checklist of criteria that an individually correct requirement should have. The following list contains some examples of criteria that a good requirement should satisfy:

  • It should be a single sentence containing a single requirement.
  • It should use simple direct language.
  • It should be unambiguous i.e. impossible to misinterpret.
  • It should be at the right level of abstraction i.e. not too detailed.
  • It should not accidentally pre-empt the lower level design. (It is quite correct for this level to impose a design constraint, but this should be done intentionally!)

In addition, there is a need to assess the complete set of requirements for completeness in satisfying the input requirements to this level. This completeness includes the need to satisfy all the input requirements, but it is also necessary for the specification containing the requirements to be understandable and complete in terms of:

  • Having a clear and relevant structure.
  • Stating assumptions.
  • Providing relevant descriptive material to set the background and any specific domain knowledge that has been assumed in the solution at this level.

Note: Standard document templates can be a useful way of addressing some of these aspects.

Validate output requirements

Validate output requirements


 

Steps
Generate requirements for lower level
  1. Using modelling and analysis of the design architecture, generate uniquely identified requirements (derived either from input requirements to this level or from the design architecture) that form a part of the Product Breakdown.
  2. Referring to the design, allocate requirements to the team that is responsible for satisfying them.
  3. Identify the intended MoC for Product Verification for each requirement that is being input to this level below.
  4. Generate a Requirements Baseline for the Requirements from this level to each Team at the level below.
Generate requirements for other team
  1. Generate uniquely identified requirements (derived either from input requirements to this level or from the design architecture) for each Transverse team. Requirements that are input to this level may themselves contain derived requirements from other Transverse teams.
  2. Identify the intended MoC for Product Verification for each requirement that is being input to a Transverse team.
  3. Generate a Requirements Baseline for the Requirements from this level to a Transverse team.
Validate output requirements
  1. Generate the Requirement Validation Plan.
  2. Establish review criteria.
    • Ensure each unique requirement is syntactically correct.
    • Ensure the requirements are contextually correct.
    • Ensure the requirements output from this level are traceable to requirements that are input to this level.
  3. Execute the Requirements Validation plan.
  4. Create a Requirements Baseline.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable