Domain model diagram examples.
Same tool, four requests. Every drawing below is a real render.
Rather start from a finished drawing? Browse 75 uml class diagram templates →
What a domain model diagram is.
A domain model diagram shows the important concepts in a business area and the relationships between them. Its classes represent things the people involved recognise, such as a customer, order, repair, reward or invoice.
Unlike an implementation-focused class diagram, a domain model leaves out most technical details. It helps stakeholders agree on vocabulary, rules and ownership before a database or application design is settled.
- Standard
- OMG UML 2.5.1 §9–§11
- Also follows
- ISO/IEC 19505-2:2012 · Classification / Classifiers / Associations
- Engine
- schematex-umlclass
- Editable
- Double-click text, drag nodes
- Export
- SVG · PNG · PDF
Who uses domain model diagrams.
A shared vocabulary for workshops, requirements and acceptance criteria before development begins.
The people, records and business rules behind a feature such as a loyalty program or repair claim.
A model that separates business concepts from framework, API and storage choices.
How to make a domain model diagram in three steps.
Describe it
One paragraph is enough to start.
See the drawing
Drawn by the right engine.
Say what changes
Every edit keeps a version.
Common questions
What is a domain model diagram?
A domain model diagram represents the main business concepts in a system and their relationships. It helps a team understand the subject area before deciding on technical implementation details.
What should I include in a domain model?
Include the concepts that carry business meaning, their important properties and the relationships or constraints between them. Focus on terms stakeholders use, rather than screens, database tables or technical services.
How do I show multiplicity in a domain model?
Put a multiplicity such as 1, 0..1, * or 1..* beside a relationship end. It states how many instances can take part in that relationship, for example one customer placing many orders.
How is a domain model different from a class diagram?
A domain model concentrates on conceptual business objects and their meaning. A class diagram can add implementation details such as methods, visibility, interfaces and technical design patterns.
Who should contribute to a domain model?
Product managers, domain experts, analysts, designers and engineers can all contribute. The goal is a model that uses language each group understands and can challenge.
Other drawings for the same work.
Map your domain model.
Free account, no card. Start with the concepts your team uses every day.
Open the editor