P1-REQ-13-7-009

Return to Part 1 Requirements

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

Part 1, Section 13.7: Traceability Requirements.

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.

This requirement applies to traceability relationships across the architecture lifecycle.

It applies specifically to:

• One-to-one trace relationships
• One-to-many trace relationships
• Many-to-one trace relationships
• Many-to-many trace relationships
• Impact analysis relationships
• Evidence support relationships

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 appropriate
• Traceability supports many-to-one relationships where appropriate
• Traceability does not force artificial simplification
• Traceability relationships represent actual architectural relationships

Related source section:

• 13.7 Traceability Requirements

Related requirement identifiers:

• P1-REQ-13-7-001
• P1-REQ-13-7-006
• P1-REQ-13-7-007
• P1-REQ-13-7-008

Draft