Skip to content

Traceability#

Traceability is the act of ensuring your Requirements (and other objects) maintain the appropriate relationships to other relevant artifacts important to the success of your project. Typically, a Systems Engineer is most interested in ensuring the Requirements (the highest level engineering artifacts) have the correct relationships with downstream objects, such as derived Requirements, allocated Parts, and Verifications.

Understanding Traceability#

Why Traceability Matters#

Traceability is essential for:

  • Compliance: Demonstrating that all requirements have been addressed
  • Change Impact Analysis: Understanding the downstream effects of requirement changes
  • Verification Coverage: Ensuring all requirements are properly verified
  • System Integration: Tracking how requirements flow through the architecture
  • Audit Trail: Providing evidence for certification and reviews

Types of Traces in SysGit#

[Content to be added - different relationship types and their meanings]

Traceability Views#

SysGit currently enables two primary approaches to Traceability:

  • Verification Matrix
  • Trace Matrix

Verification Matrix#

The Verification Matrix is used to ensure all Requirements correctly map to their ultimate Verifications. This is incredibly useful for ensuring the business needs of the organization map into the engineering activities of the team. A Verification is used to ensure that the ultimate physical creation correctly meets the intent of the Requirement.

The Verification Matrix presents this mapping in a tabular format, helping users quickly identify which requirements have been covered and where gaps in verification remain.

For more information, please visit the SEBoK section on the Systems Engineering Vee.

Gap Analysis#

[Content to be added - identifying unverified requirements]

Coverage Reporting#

[Content to be added - generating coverage reports]

Trace Matrix#

The Trace Matrix in SysGit is a powerful tool for visualizing the relationships across your project's systems model. Unlike the Verification Matrix, which focuses specifically on the link between Requirements and their Verifications, the Trace Matrix provides a broader and more flexible overview of how objects across the SysML model relate to one another.

This matrix answers questions like:

  • Which Requirements are satisfied by which Parts?
  • Which Requirements are decomposed into sub-requirements?
  • Which Requirements are verified by which artifacts?
  • Are there Requirements that lack verification coverage?

Interface Overview#

The matrix allows users to select two object types—for example, Requirements vs Parts, or Requirements vs Verifications—and view the relationships between them. The rows represent one object type (e.g., Requirements), and the columns represent another (e.g., Verifications). An arrow and letter indicates the presence of a relationship (e.g., "is verified by"), its type, and its direction.

Each cell in the matrix provides traceability feedback that can be clicked to navigate directly to the linked item. This makes it especially useful during peer reviews, compliance audits, or when onboarding new team members who need to understand the system's structure quickly.

Filtering and Navigation#

[Content to be added - how to filter and navigate the trace matrix]

Impact Analysis#

Finding Downstream Impacts#

[Content to be added - understanding impact of requirement changes]

Change Propagation#

[Content to be added - how changes flow through the system]

Traceability Best Practices#

By maintaining a well-structured trace matrix, teams gain confidence that all engineering activities—requirements, design elements, tests—are aligned and synchronized, reducing the likelihood of integration errors, compliance gaps, or redundant work.

[Content to be added - additional best practices]

See Also#