dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P1-REQ-13-7-009 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-01:start|Return to Part 1 Requirements]]
 +
 +===== Statement =====
 +
 +[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 relationships
 +  * One-to-many trace relationships
 +  * Many-to-one trace relationships
 +  * Many-to-many trace relationships
 +  * Impact analysis relationships
 +  * Evidence 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 appropriate
 +  * Traceability supports many-to-one relationships where appropriate
 +  * Traceability does not force artificial simplification
 +  * Traceability relationships represent actual architectural relationships
 +
 +===== Traceability =====
 +
 +Related source section:
 +
 +  * [[fxdemo:01-part:13-conceptual-requirements:13-7-traceability-requirements]]
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-006:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start]]
 +  * [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-008:start]]
 +
 +===== Status =====
 +
 +Draft
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>