DoDAF Viewpoints and Models
SV-5b: Operational Activity to Systems Traceability Matrix
The SV-5b addresses the linkage between described in SV-1 Systems Functionality Description and Operational Activities specified in OV-5a Operational Activity Decomposition Tree or OV-5b Operational Activity Model. The SV-5b depicts the mapping of systems and, optionally, the capabilities and performers that provide them to operational activities. The SV-5b identifies the transformation of an operational need into a purposeful action performed by a system or solution.
During requirements definition, the SV-5b plays a particularly important role in tracing the architectural elements associated with system requirements to those associated with user requirements.
The intended usage of the SV-5b includes:
- Tracing system requirements to user requirements.
- Tracing solution options to requirements.
- Identification of overlaps or gaps.
An SV-5b is a specification of the relationships between the set of operational activities applicable to an Architectural Description and the set of systems applicable to that Architectural Description. The relationship between operational activities and systems can also be expected to be many-to-many (i.e., one activity may be supported by multiple systems, and one system may support multiple activities). The system shown in the SV-5b may be those associated with resources. More focused SV-5b models might be used to specifically trace system to operational activities if desired.
The SV-5b is generally presented as a matrix of the relationship between systems and activities and can be a summary of the Operational Activity to System Function Traceability Matrix (SV-5a). The SV-5b can show requirements traceability with Operational Activities on one axis of a matrix, the System Functions on the other axis, and with an X, date, or phase in the intersecting cells, where appropriate.
An alternate version of the tabular SV-5b model can allow the implementation status of each system to be shown. In this variant model, each system-to-operational activity mapping is described by a traffic light symbol that may indicate the status of the system support. DoDAF V2.0 does not prescribe a presentation technique. These symbols are usually colored circles with the following possible representations:
- Red may indicate that the system is planned but not developed.
- Yellow may indicate that partial system functionality has been provided (or full functionality provided but system has not been fielded).
- Green may indicate that full system functionality has been provided to the field.
- A blank cell may indicate that there is no system support planned for an Operational Activity, or that a relationship does not exist between the Operational Activity and the System Function.
Care should be taken when publishing a SV-5b with status information. Any presentation should clearly state the date of publication, so that users can see when status information is old.
The SV-5b may be further annotated with Capabilities, Performers executing Activities, and capabilities and performers that conduct the functions. This can be used to identify which systems can support a particular capability. The architect may also wish to hide the systems in a SV-5b so that the table simply shows the mapping from performers executing activities, and capabilities and performers to Operational Activities.
SV-1 Systems Interface Description
SV-2 Systems Resource Flow Description
SV-3 Systems-Systems Matrix
SV-4 Systems Functionality Description
SV-5a Operational Activity to Systems Function Traceability Matrix
SV-5b Operational Activity to Systems Traceability Matrix
SV-6 Systems Resource Flow Matrix
SV-7 Systems Measures Matrix
SV-8 Systems Evolution Description
SV-9 Systems Technology & Skills Forecast
Introduction to SV-10a, SV10b, and SV-10c
SV-10a Systems Rules Model
SV-10b Systems State Transition Description
SV-10c Systems Event-Trace Description