P1-REQ-13-7-009

Return to Part 1 Requirements

Statement

Traceability SHALL NOT require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.

Source

Part 1, Section 13.7: Traceability Requirements.

Rationale

Architecture traceability often includes one-to-many, many-to-one, and many-to-many relationships. A single conceptual concern may refine into multiple logical elements. Multiple implementation artifacts may realize one logical element. Multiple evidence records may support one claim.

This requirement prevents artificial simplification that obscures actual architectural relationships and weakens review, impact analysis, and evidence support.

Applies To

This requirement applies to traceability relationships across the architecture lifecycle.

It applies specifically to:

One-to-one trace relationshipsOne-to-many trace relationshipsMany-to-one trace relationshipsMany-to-many trace relationshipsImpact analysis relationshipsEvidence support relationships

Verification

Verification SHALL confirm that Traceability does not require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.

Verification activities include review checks confirming that:

Traceability supports one-to-many relationships where appropriateTraceability supports many-to-one relationships where appropriateTraceability does not force artificial simplificationTraceability relationships represent actual architectural relationships

Traceability

Related source section:

Related requirement identifiers:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.