Task: Budget Non-Functional Requirements with the Operations

This task describes a flowdown technique for deriving non-functional requirements.

Disciplines: System Engineering Architecture

To augment these white-box descriptions with locality decisions, process decisions, worker decisions, and white-box budget requirements.

Inputs

Mandatory:

System Operation
System-Wide Requirements

Optional:

None

Outputs

System Operation

Link Operations to non-functional requirements

Apportion black-box step budgeted requirements to white-box steps. This allocation helps determine the performance requirements for both the subsystem and the associated locality. In the case of a passive subsystem, it is an input into latency analysis of the invoking process (which might have other responsibilities).

Update traceability records

Update the Traceability Record to capture the traceability between operations (or an associated system level/component) and associated non-functional requirements.