| Next revision | Previous revision |
| fxdemo:02-part:12-logical-traceability-model:12-1-overview:start [2026/07/03 13:27] – created owen | fxdemo:02-part:12-logical-traceability-model:12-1-overview:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:02-part:start | Go To Top ]] | [[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 artefacts, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations. | 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 [[fxdemo:99_part_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 artefacts, deployment artefacts, test scenarios, runtime observations, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records. | 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, modelling notation, requirements-management system, issue tracker, metadata format, or evidence store. Implementation and governance profiles select mechanisms that realise logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] for a specific implementation context. | 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. | Figure 12-1 summarises the logical traceability chain. |
| └── Part 2 Logical Element / PIM | └── Part 2 Logical Element / PIM |
| └── Domain Logical Profile Element | └── Domain Logical Profile Element |
| └── Implementation Artefact / PSM | └── Implementation Artifact / PSM |
| └── Deployment Artefact | └── Deployment Artifact |
| └── Evidence | └── Evidence |
| Figure 12-1: Logical traceability chain from concept to evidence | Figure 12-1: Logical traceability chain from concept to evidence |