Skip to content

Domain Model

In software engineering, a domain model is a conceptual model of the domain that incorporates both behavior and data.

Version
v1 · 2026-09-28 · History
Domain-specific #
9043
Domain group
Applied Sciences & Engineering
Origin domain
Computer Science & Software Engineering
Subdomains
Software Engineering, Conceptual Modeling → Computer Science & Software Engineering

Core Idea

Domain Model is treated here as the recurring computer science and information systems identity summarized by this source-grounded definition: In software engineering, a domain model is a conceptual model of the domain that incorporates both behavior and data. In software engineering, a domain model is a conceptual model of the domain that incorporates both behavior and data. In ontology engineering, a domain model is a formal representation of a knowledge domain with concepts, roles, datatypes, individuals, and rules, typically grounded in a description logic.

How would you explain it like I'm…

The Picture Plan

Before making a pretend store game, you draw a picture of the store. You show the things in it, like shoppers, shelves, and money, how they connect, and what they do, like shoppers buying things. You don't worry yet about how the computer will work. That picture is the plan everyone agrees on.

Real-World Blueprint

A domain model is a drawing or description of the real-world area a program is about, like a school, a bank, or a library. It shows the important things (students, classes, books), how they are connected, and what they do (a student borrows a book). It includes both the information and the actions. It is kept separate from the details of how the program will actually store data or run, so the meaning of the business stays clear.

Conceptual Model of the Domain

In software engineering, a domain model is a conceptual model of the subject area a system deals with, and it includes both data and behavior. It captures the key concepts of the business, their relationships and the roles they play, but it deliberately ignores design and implementation issues like how data is stored or how tasks run at the same time. In UML it is often drawn as a class diagram, where classes are concepts and associations are relationships. In an entity-relationship (ER) diagram, entities are concepts and cardinality and optionality describe how they relate. The main rule is to keep the business meaning clear and rich instead of bending it to fit technical design. In ontology engineering the term has a related meaning: a formal representation of a knowledge domain using concepts, roles, datatypes, individuals and rules.

 

A Domain Model, in software engineering, is a conceptual model of a domain that incorporates both behavior and data. It is explicitly chosen to be independent of design and implementation concerns such as concurrency or data storage. In UML it is typically expressed as a class diagram: classes represent concepts, associations represent relationships, and association role types represent the roles instances take in various situations. In ER notation, entities represent concepts, and cardinality and optionality characterize their relationships. In ontology engineering, the term denotes a formal representation of a knowledge domain with concepts, roles, datatypes, individuals and rules, typically grounded in a description logic. Whatever the notation, the richness and clarity of business meaning should not be compromised by expressing it in a form driven by implementation. A diagram that only shares the name or a familiar example, or that captures data without behavior, does not qualify.

Scope of Application

  • Overview. In the field of computer science a conceptual model aims to express the meaning of terms and concepts used by domain experts to discuss the problem, and to find the correct.

  • Overview. Conceptual modeling in computer science should not be confused with other modeling disciplines within the broader field of conceptual models such as data modelling, logical modelling and physical modelling.

  • Overview. The conceptual model attempts to clarify the meaning of various, usually ambiguous terms, and ensure that confusion caused by different interpretations of the terms and concepts cannot occur.

  • Overview. Once the domain concepts have been modeled, the model becomes a stable basis for subsequent development of applications in the domain.

  • Overview. Regardless of the notation used, it is important not to compromise the richness and clarity of the business meaning depicted in the conceptual model by expressing it directly in a form.

Clarity

A clear use of Domain Model names the carrier, the operative relation, and the conditions under which the source treats the identity as present. The minimal definition is In software engineering, a domain model is a conceptual model of the domain that incorporates both behavior and data.

Manages Complexity

Domain Model compresses multiple computer science and information systems details into a stable diagnostic relation. The source shows both the central mechanism—the conceptual model attempts to clarify the meaning of various, usually ambiguous terms, and ensure that confusion caused by different interpretations of the terms and concepts cannot occur.—and the practical consequence—the conceptual model is explicitly chosen to be independent of design or implementation concerns, for example.

Abstract Reasoning

  1. Type the carrier. Identify the computer science and information systems entities to which the claim applies.
  2. State the relation. Use the source-grounded identity: In software engineering, a domain model is a conceptual model of the domain that incorporates both behavior and data.
  3. Check operation and conditions. In UML notation, the conceptual model is often described with a class diagram in which classes represent concepts, associations represent relationships between concepts and role types of an association represent role types taken by instances of the modelled concepts.

Knowledge Transfer

Within the home domain. Knowledge about Domain Model transfers literally when a new case preserves the same carrier type, relation, and recognition test. In the field of computer science a conceptual model aims to express the meaning of terms and concepts used by domain experts to discuss the problem, and to find the correct relationships between different concepts. Conceptual modeling in computer science should not be confused with other modeling disciplines within the broader field of conceptual models such as data modelling, logical modelling and physical modelling. Beyond the.

Relationships to Other Abstractions

Local relationship map for Domain ModelParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Domain ModelDOMAINPrime abstraction: Representation — is a kind ofRepresentationPRIME

Current abstraction Domain Model Domain-specific

Parents (1) — more general patterns this builds on

  • Domain Model is a kind of Representation Prime

    A software domain model is a representation of a domain's entities, data, behavior, and relations; the live Conceptual Model alias belongs to the narrower Mental Model Prime and is not used as its genus.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Domain Model sits in a moderately populated region (53rd percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Unclustered & Miscellaneous (2551 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08