12.1 Overview [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 12.1 Overview ======
[[fxdemo:02-part:start | Go To Top ]]

The Logical Traceability Model defines how the distributed, node-based Logical Architecture / PIM preserves relationships among Part 1 conceptual elements, Part 2 logical elements, domain-profile specialisations, implementation mappings, deployment artifacts, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.

Logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] allows authors and reviewers to follow a concern from conceptual meaning to logical structure. It also prepares later parts to trace logical elements to implementation artifacts, deployment artifacts, test scenarios, runtime observations, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records.

The Logical Traceability Model does not prescribe a traceability tool, repository structure, modeling notation, requirements-management system, issue tracker, metadata format, or evidence store. Implementation and governance profiles select mechanisms that realize logical [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] for a specific implementation context.

Figure 12-1 summarises the logical traceability chain.
  Part 1 Conceptual Element
  └── Part 2 Logical Element / PIM
      └── Domain Logical Profile Element
          └── Implementation Artifact / PSM
              └── Deployment Artifact
                  └── Evidence
Figure 12-1:	Logical traceability chain from concept to evidence


----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>