Logical Traceability SHALL NOT require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.
Part 2, Section 16.9: Logical Traceability Requirements.
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.
This requirement applies to the Logical Traceability Model.
It applies specifically to:
Verification SHALL confirm that the Logical Traceability Model supports the architectural relationships actually present.
Verification activities should include review checks confirming that:
This requirement supports accurate traceability throughout the architecture lifecycle without imposing unnecessary structural constraints.
Related requirement identifiers:
Related source section:
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.