Logical Model (LM)

Return to Terms and Definitions

Discussion

A logical model describes a system from a selected architectural viewpoint without defining implementation artefacts.

A system architecture contains multiple logical models when different architectural concerns require separate treatment. These concerns include information structure, persistence, messaging, service behaviour, user interaction, governance, policy control, security, evidence, audit, and logging.

A Platform Independent Model comprises one or more logical models. Each logical model addresses a distinct architectural concern at the platform-independent level. A Platform Specific Model maps a logical model to selected platform features.

Definition

model of a system from a selected architectural viewpoint, independent of implementation artefacts

Source

Adapted for the FX Demo Reference Architecture

Note

A logical model defines architecture-level structure, behaviour, relationships, constraints, and obligations for a selected concern.

A logical model is not an implementation artefact. Source code, generated code, database schemas, interface definition files, configuration files, build scripts, deployment files, logs, and runtime components are implementation artefacts.

Logical models organise architectural concerns. Platform-specific models organise selected technology realisations of those concerns.

Example

A persistence logical model defines the information structures, relationships, constraints, retention obligations, and query responsibilities required for stored information.

A relational database Platform Specific Model realises the persistence logical model using tables, columns, keys, constraints, indexes, and SQL views.

A graph database Platform Specific Model realises the same persistence logical model using nodes, edges, properties, labels, graph constraints, and graph queries.