Software Construction: Domain Driven Design

Domain Driven Design

• Domain Driven Design focuses on solving organizational problems through code, prioritizing resources on the business logic of an application.
• The domain refers to the world of the business, including rules, processes, and existing systems.

Domain Model

• A domain model is a structured visual representation of interconnected concepts or real-world objects.
• It incorporates vocabulary, key concepts, behavior, and relationships of all entities within the domain.
• The domain model should be accessible and understandable by everyone involved in the project.
• A domain model can be represented through diagrams, code examples, or written documentation.
• Class diagrams are commonly used to illustrate domain models, showing:
  • Domain objects or conceptual classes
  • Associations between conceptual classes
  • Attributes of conceptual classes

The Model

• The model represents the solution to the problem, often simplifying the bigger picture to focus on important aspects.
• The model and domain model shape each other.
• The domain model is the backbone of the language used by all team members.
• The domain model is distilled knowledge.

General Steps in Domain Modelling

• Prepare a problem statement for the system being developed.
• Identify classes and objects.
• Develop a data dictionary.
• Identify associations between classes.
• Identify attributes of classes and association classes.
• Structure objects using inheritance.
• Verify access paths for likely queries.
• Iterate and refine the model.

Relationship Notations for Classes in UML

• No specific details provided in the text.