====== 12.7 Traceability from Part 1 to Part 2 ======
[[fxdemo:01-part:start | Go to Top ]]

Part 2 should maintain explicit [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to Part 1.

[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from each major logical element to its conceptual source allows reviewers to verify that the logical architecture preserves the conceptual architecture and prepares a clear basis for implementation profiles, deployment profiles, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] plans.

Table 12.7-1 provides examples of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from Part 1 concepts to Part 2 logical elements.

Table 12.7-1: Examples of traceability from conceptual elements to logical elements

^ Part 1: Conceptual Element ^ Part 2: logical treatment ^
| [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] | Logical Node |
| [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]] | Logical identity model for Nodes |
| [[dido:99_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]] | Logical responsibility assigned to a Logical Node |
| [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] | Logical plane model and plane participation rules |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] | Logical endpoint or interaction point |
| [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]] | Logical information structure |
| [[dido:99_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]] | Logical message, record, event, assertion, or command instance |
| [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | Logical evidence class or evidence claim |
| [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] | Logical trace relationship |


----

<WRAP centeralign>

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

</WRAP>