traceability-manager

Bidirectional requirements traceability is maintained by mapping requirements, tasks, APIs, validation evidence, and policies into a typed relationship graph using a controlled vocabulary. This generates a Markdown traceability model snapshot that governs coverage validation and change impact analysis.

Orphan detection in requirements traceability identifies requirements, tasks, APIs, validations, or policies that lack required link structures. It classifies requirements by coverage level and flags unlinked artifacts to ensure complete governance across the bidirectional traceability model.

Change impact analysis is performed by tracing forward and backward through typed bidirectional links to identify the complete set of affected artifacts. This ensures accurate tracking of implementations, validations, and policies before executing project changes.

The best way to structure an RTM for validation coverage is using a controlled vocabulary of typed links like originates-from, refines, implements, and validated-by. This explicit typed-link approach keeps relationships governable and produces consistent Markdown traceability plans.

Yes, you can use typed links to govern requirements-to-validation coverage across multiple artifact types. The traceability model enforces explicit typed-link vocabulary rules, classifies coverage levels, and reports orphans across requirements, tasks, APIs, validations, and policies.

You should not use a typed link traceability model when your project lacks defined requirements, implementation artifacts, or validation evidence to map. Without existing artifacts to link, the model cannot perform coverage classification, orphan reporting, or forward and backward impact tracing.