Differences

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

--- dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-013 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-013 [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
+====== P2-REQ-16-9-013 ======
+[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
+===== Statement =====
+Logical [[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 2, Section 16.9: Logical Traceability Requirements.
+===== Rationale =====
+Architectural relationships are not always one-to-one. A single conceptual concern may refine into several logical elements, and multiple logical elements may contribute to a common implementation or evidence artifact. Allowing many-to-one and one-to-many relationships ensures that the Traceability Model accurately reflects the architecture rather than forcing artificial mappings that obscure architectural intent.
+===== Applies To =====
+This requirement applies to the Logical Traceability Model.
+It applies specifically to:
+  * Traceability relationships;
+  * Conceptual elements;
+  * Logical elements;
+  * Domain Logical Profiles; and
+  * Implementation Profiles.
+===== Verification =====
+Verification SHALL confirm that the Logical Traceability Model supports the architectural relationships actually present.
+Verification activities should include review checks confirming that:
+  * one-to-many relationships are permitted where appropriate;
+  * many-to-one relationships are permitted where appropriate;
+  * artificial mappings are avoided; and
+  * traceability accurately represents the architecture.
+===== Traceability =====
+This requirement supports accurate traceability throughout the architecture lifecycle without imposing unnecessary structural constraints.
+Related requirement identifiers:
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-010]]
+  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-9-012]]
+  * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-008]]
+Related source section:
+  * [[fxdemo:02-part:16-logical-requirements:16-9-logical-traceability-requirements:start]]
+===== Status =====
+Draft
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>