Trace links overview

Note: This topic documents the native, generic Active Workspace trace-link mechanism (Active Workspace Fundamentals / Getting Started Guide book), which is the underlying capability that pillar-specific applications (Model-Based Systems Engineering, Requirements Management, Program Planning, Schedule Manager, etc.) build on and surface through their own commands and views. It is not tied to any one pillar.

Traceability provides a connection between data objects. For Model-Based Systems Engineering, this means connecting our structure elements together.

Trace links establish the traceability among structure elements and in which one object takes precedence over another. A trace link establishes a directional relationship between two objects.

For example, creating links between requirements, between system model blocks, and between each other. When the requirements and system modeling are complete, users have complete traceability from requirements, to functions, to logical and physical objects allowing users to see the decision, requirements and alternatives that lead to a particular design alternative.

The trace link Start (defining object such as a requirement), is the trace link source. The End (the complying object such as a system model block), is the target. In this relationship, the Start defines a condition with which the other End must comply, that is, must partially or completely fulfill.