Task: Agree Input Requirements
In this task, the development team will identify and agree on requirements which they will commit to deliver.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

The input requirements for the development team at this level come from three different sources:

  • Requirements from Level Above
  • Requirements from Specialist Domain
  • Requirements from Other Teams at the same level

For each different sources, there is a slightly different approach to handle reviewing and agreeing the requirements in order for the development team to produce the input requirements for this level. The following paragraphs will provide details for each approach.

Requirements from Level Above:

This process identifies those requirements at the level above that are relevant to the development of the specific team at this level. The process uses an allocation (often termed “pre-allocation”) approach in which the team at the level above makes a proposed allocation for the requirements that should be given to the team at this level. An alternative approach could allow teams at a specific level to ‘bid’ for requirements at the level above to ‘satisfy’. The team at this level will then negotiate their acceptance (or otherwise) of these requirements.

The team at this level may wish to change the wording of any relevant N+1 requirement. This can be because it is unclear as currently worded and the change can lead to a common understanding of the intent. The team at this level can also suggest changes because they know from experience that it may be impossible to implement a requirement, or that the cost/risk would be too high.

Agree Requirements from Level Above

Agree requirements from Level Above

Requirements from Specialists Domain:

The development team must seek out all sources of specialist requirements. This includes Certification, Safety, Supportability, Producibility, Design Guidelines and other Directives.

This process step requires the specialist domain authorities to contribute by indicating the requirements that must be satisfied at a specific level in the development hierarchy. It may be necessary to provide an alternative formulation of the wording of the “requirements” where they originate from international standards etc. This reformulation is for clarification purposes and must not dilute or distort the intent of the standard. The specialist domain authority is responsible for ensuring that the rewording will be acceptable to the relevant authorities, for documenting the justification for the wording that is agreed and for showing traceability.

Agree requirements from specialist domain

Agree Requirements from Specialist Domain

Requirements from Other Teams at the same level:

The development team must seek out all requirements placed on them by other development teams.This process step requires the issuing development team to make it clear which team they consider responsible for satisfying any requirements they have generated for other teams.

Agree requirements from Other Team

Agree Requirements from Other Team


Steps
Determine the Requirements set being cascaded to the development team at this level.
Agree individual Requirements.
Agree the rationale for each requirement.
Is the need for the requirement really justified?
Agree intended MoC for each requirement.
Sign agreed requirements.
Once agreement has been reached, sign (Authorise) the document or specification. (This is where Project Management authorise what has technically been agreed). Signing shall involve all related parties, including team from this level, team above, other teams, domain specialists, etc.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable