13.7 Traceability Requirements

Go to Conceptual Requirements

This section identifies the normative requirements for traceability established by Part 1. The canonical requirement statements are maintained in Annex C: Requirements, Part 1.

Table 13.7-1: Part 1 traceability requirements.

Requirement ID	Statement
P1-REQ-13-7-001	The Conceptual Architecture SHALL define Traceability across conceptual elements, logical elements, implementation artifacts, deployment artifacts, and Evidence.
P1-REQ-13-7-002	A Logical Architecture / PIM element SHALL trace to the conceptual element it specializes, refines, constrains, or relates.
P1-REQ-13-7-003	An Implementation Profile / PSM artifact SHALL trace to the logical element it realizes.
P1-REQ-13-7-004	A Deployment Artifact SHALL trace to the implementation artifact it deploys, configures, executes, or exposes.
P1-REQ-13-7-005	Evidence SHALL trace to the claim, behavior, artifact, configuration, execution condition, review conclusion, or Governance and Authority decision it supports.
P1-REQ-13-7-006	Traceability SHALL support forward review from conceptual concern to Evidence.
P1-REQ-13-7-007	Traceability SHALL support backward review from Evidence to conceptual concern.
P1-REQ-13-7-008	Traceability SHALL support impact analysis across conceptual, logical, implementation, deployment, and Evidence layers.
P1-REQ-13-7-009	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.