16.9 Logical Traceability Requirements

Go To Top

1. The Logical Architecture / PIM SHALL define a Logical Traceability Model.
2. The Logical Traceability Model SHALL define Traceability from Part 1 conceptual elements to Part 2 logical elements.
3. The Logical Traceability Model SHALL define Logical Node Traceability, Logical Endpoint Traceability, Logical Data Structure Traceability, Logical Runtime Plane Traceability, Logical Interaction Traceability, and Logical Evidence Traceability.
4. Logical Node Traceability SHALL relate a Logical Node to its identities, roles, responsibilities, endpoints, interactions, Runtime Planes, governance relationships, and Evidence expectations.
5. Logical Endpoint Traceability SHALL relate a Logical Communication Endpoint to participating Nodes, Communication Roles, information structures, Runtime Planes, governance constraints, and Evidence expectations.
6. Logical Data Structure Traceability SHALL relate logical information structures and instances to definitions, Nodes, endpoints, Runtime Planes, governance constraints, lineage, and Evidence expectations.
7. Logical Runtime Plane Traceability SHALL relate logical interactions and information exchanges to their Logical Runtime Plane classification.
8. Logical Interaction Traceability SHALL relate a logical interaction pattern to Nodes, roles, endpoints, information structures, Runtime Planes, governance constraints, and Evidence expectations.
9. Logical Evidence Traceability SHALL relate logical elements and interactions to Evidence expectations for later realisation, deployment, testing, and review.
10. Logical Traceability SHALL support forward review from the conceptual concern to the logical model.
11. Logical Traceability SHALL support backward review from logical element to conceptual source.
12. Logical Traceability SHALL support later traceability from logical elements to Domain Logical Profile elements, implementation artefacts, deployment artefacts, test scenarios, runtime observations, and Evidence records.
13. Logical Traceability SHALL NOT require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.