Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:c:conceptual_model to dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:c:conceptual_model [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Conceptual Model (CM) ======
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]
 ===== Discussion =====
@@ Line 7: / Line 7: @@
 A conceptual model describes the relevant concepts in a problem domain and the relationships among those concepts.
-Within the FX Demo Reference Architecture, a conceptual model establishes shared meaning before logical modelling, platform-specific modelling, or implementation work begins. It identifies domain concepts, policy concepts, governance concepts, information concepts, roles, relationships, constraints, assumptions, and boundaries.
+Within the FX Demo Reference Architecture, a conceptual model establishes shared meaning before logical modeling, platform-specific modeling, or implementation work begins. It identifies domain concepts, policy concepts, governance concepts, information concepts, roles, relationships, constraints, assumptions, and boundaries.
-A conceptual model supports agreement about meaning. It does not define implementation artefacts, platform features, software structures, database structures, middleware structures, deployment structures, or runtime components.
+A conceptual model supports agreement about meaning. It does not define implementation artifacts, platform features, software structures, database structures, middleware structures, deployment structures, or runtime components.
 ===== Definition =====
@@ Line 23: / Line 23: @@
 A conceptual model defines domain-level meaning and scope.
-A conceptual model precedes Logical Models, Platform-Independent Models, Platform-Specific Models, and implementation artefacts in the architectural refinement chain.
+A conceptual model precedes Logical Models, Platform-Independent Models, Platform-Specific Models, and implementation artifacts in the architectural refinement chain.
-Conceptual models organise domain meaning. Logical models organise architectural concerns. Platform-specific models organise selected technology realisations of those concerns.
+Conceptual models organize domain meaning. Logical models organize architectural concerns. Platform-specific models organize selected technology realisations of those concerns.
 ===== Example =====
@@ Line 31: / Line 31: @@
 A conceptual model identifies jurisdiction, sovereignty, residency, governed release, release evidence, reporting party, receiving authority, policy authority, and policy decision as domain concepts.
-A logical model organises those concepts into architectural viewpoints such as policy control, information exchange, evidence, audit, and governance.
+A logical model organizes those concepts into architectural viewpoints such as policy control, information exchange, evidence, audit, and governance.