Conceptual Model (CM)

Return to Terms and Definitions

Discussion

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 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 artifacts, platform features, software structures, database structures, middleware structures, deployment structures, or runtime components.

Definition

model that represents concepts in a domain and relationships among those concepts

Source

Adapted for the FX Demo Reference Architecture

Note

A conceptual model defines domain-level meaning and scope.

A conceptual model precedes Logical Models, Platform-Independent Models, Platform-Specific Models, and implementation artifacts in the architectural refinement chain.

Conceptual models organize domain meaning. Logical models organize architectural concerns. Platform-specific models organize selected technology realisations of those concerns.

Example

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 organizes those concepts into architectural viewpoints such as policy control, information exchange, evidence, audit, and governance.