16.9 Logical Traceability Requirements

Go To Logical Requirements

This section identifies the normative requirements established for the Logical Traceability Model. The canonical requirement statements are maintained in Annex C: Requirements, Part 2, Section 16.9.

Table 16-8: Logical Traceability requirements.

Requirement ID	Statement
P2-REQ-16-9-001	The Logical Architecture / PIM SHALL define a Logical Traceability Model.
P2-REQ-16-9-002	The Logical Traceability Model SHALL define Traceability from Part 1 conceptual elements to Part 2 logical elements.
P2-REQ-16-9-003	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.
P2-REQ-16-9-004	Logical Node Traceability SHALL relate a Logical Node to its identities, roles, responsibilities, endpoints, interactions, Runtime Planes, governance relationships, and Evidence expectations.
P2-REQ-16-9-005	Logical Endpoint Traceability SHALL relate a Logical Communication Endpoint to participating Logical Nodes, Communication Roles, information structures, Runtime Planes, governance constraints, and Evidence expectations.
P2-REQ-16-9-006	Logical Data Structure Traceability SHALL relate logical information structures and instances to definitions, Logical Nodes, endpoints, Runtime Planes, governance constraints, Logical Information Lineage, and Evidence expectations.
P2-REQ-16-9-007	Logical Runtime Plane Traceability SHALL relate logical interactions and information exchanges to their Logical Runtime Plane classification.
P2-REQ-16-9-008	Logical Interaction Traceability SHALL relate a logical interaction pattern to Logical Nodes, roles, endpoints, information structures, Runtime Planes, governance constraints, and Evidence expectations.
P2-REQ-16-9-009	Logical Evidence Traceability SHALL relate logical elements and interactions to Evidence expectations for later realization, deployment, testing, and review.
P2-REQ-16-9-010	Logical Traceability SHALL support forward review from the conceptual concern to the logical model.
P2-REQ-16-9-011	Logical Traceability SHALL support backward review from logical element to conceptual source.
P2-REQ-16-9-012	Logical Traceability SHALL support later traceability from logical elements to Domain Logical Profile elements, implementation artifacts, deployment artifacts, test scenarios, runtime observations, and Evidence records.
P2-REQ-16-9-013	Logical Traceability SHALL NOT require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.