Differences

This shows you the differences between two versions of the page.

--- fxdemo:01-part:10-conceptual-traceability-model:10-2-traceability-across-layers [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:10-2-traceability-across-layers to fxdemo:01-part:10-conceptual-traceability-model:10-2-traceability-across-layers owen
+++ fxdemo:01-part:10-conceptual-traceability-model:10-2-traceability-across-layers [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-Traceability across layers preserves architectural meaning as later parts specialise, realise, deploy, and evidence the conceptual architecture.
+[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] across layers preserves architectural meaning as later parts specialize, realize, deploy, and provide [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] for the conceptual architecture.
-Each layer has a distinct traceability responsibility:
+Each layer has a distinct [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] responsibility:
-Table 10.2-1:	Traceability responsibilities across architectural layers
+Table 10.2-1: Traceability responsibilities across architectural layers
 ^ Layer ^ Traceability responsibility ^
 | Conceptual Architecture | Defines stable concepts and conceptual boundaries. |
-| Logical Architecture / PIM | Specialises conceptual elements into platform-independent logical structures, relationships, and constraints. |
+| Logical Architecture / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] | Specializes conceptual elements into platform-independent logical structures, relationships, and constraints. |
-| Implementation Profile / PSM | Maps logical elements to selected implementation technologies and artefacts. |
+| Implementation Profile / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Model (PSM)]] | Maps logical elements to selected implementation technologies and artifacts. |
-| Deployment Profile | Describes how implementation artefacts run in a concrete environment. |
+| Deployment Profile | Describes how implementation artifacts run in a concrete environment. |
-| Evidence | Supports claims about architecture, implementation, deployment, execution, interpretation, governance, or review. |
+| [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | Supports claims about architecture, implementation, deployment, execution, [[dido:99_annexes:annex-b-terms-and-definitions:i:interpretation|Interpretation]], [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]], or review. |
+[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] keeps these layers connected without allowing one layer to redefine another. A logical element may specialize a conceptual element. An implementation artifact may realize a logical element. A deployment artifact may execute or configure an implementation artifact. [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] may support a claim about any of these layers.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>
-Traceability keeps these layers connected without allowing one layer to redefine another. A logical element may specialise a conceptual element. An implementation artefact may realise a logical element. A deployment artefact may execute or configure an implementation artefact. Evidence may support a claim about any of these layers.