| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/07/07 16:57] – owen | fxdemo:01-part:11-conceptual-rules-and-constraints:11-11-conceptual-constraints-summary [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| |
| - Conceptual elements remain distinct from one another. | - Conceptual elements remain distinct from one another. |
| - Conceptual architecture does not prescribe execution granularity, deployment granularity, communication technology, interface style, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data|Data]] serialisation format, or runtime packaging. | - Conceptual architecture does not prescribe execution granularity, deployment granularity, communication technology, interface style, [[dido:99_annexes:annex-b-terms-and-definitions:d:data|Data]] serialisation format, or runtime packaging. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify business and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:semantics|Semantic]] scope, not [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] boundaries. | - [[dido:99_annexes:annex-b-terms-and-definitions:c:classification_path|Classification]] values identify business and [[dido:99_annexes:annex-b-terms-and-definitions:s:semantic|Semantic]] scope, not [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime]] boundaries. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] classify architectural purpose, not implementation mechanisms. | - [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]] classify architectural purpose, not implementation mechanisms. |
| - Implementation mappings realise concepts; they do not redefine them. | - Implementation mappings realize concepts; they do not redefine them. |
| - Deployment artefacts execute implementations; they do not redefine concepts or logical elements. | - Deployment artifacts execute implementations; they do not redefine concepts or logical elements. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supports claims; it does not replace claims. | - [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] supports claims; it does not replace claims. |
| - [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] preserves relationships across layers. | - [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] preserves relationships across layers. |
| - Local profiles preserve parent meaning unless they explicitly define a controlled extension. | - Local profiles preserve parent meaning unless they explicitly define a controlled extension. |
| |