traceability-check

End-to-end SDD traceability checking analyzes your REQ, UC, WF, API, BDD, INV, and ADR artifacts to validate complete traceability. It cross-references IDs across these artifacts and generates a report flagging missing connections and broken links.

Finding orphaned definitions and undefined references requires cross-referencing IDs across your SDD artifact chain. The checker surfaces definitions that are not consumed downstream and references that lack definitions, reporting them without modifying your source files.

Validating that a requirement is fully traced involves cross-referencing its ID through the SDD chain. The checker enforces ID definition patterns and validates that a REQ-001 is properly linked through UC, WF, API, BDD, INV, and ADR artifacts, highlighting any missing links.

The traceability checker does not modify source files when scanning for broken links. It operates in a read-only manner to analyze your SDD artifacts, enforcing ID definition patterns and reporting orphaned definitions and undefined references safely.

Identifying gaps in the SDD traceability chain is best handled by cross-referencing IDs across REQ, UC, WF, API, BDD, INV, and ADR artifacts. This approach validates complete traceability and surfaces missing connections to prevent orphaned references.

You can enforce ID definition patterns for SDD artifacts using a traceability checker. It analyzes your REQ, UC, WF, API, BDD, INV, and ADR files to validate that IDs follow defined patterns and reports any definitions that deviate from these standards.