Domain Model
- •
What it is
- •
a visual representation of the conceptual classes (real-world things) in a problem domain — also called a conceptual model or analysis object model
- •
- •
What it shows
- •
conceptual classes/objects, associations between them, and their attributes
- •
- •
What it explicitly does NOT show
- •
software artifacts (windows, databases) or responsibilities/methods — a domain model is not a software design
- •
- •
Distinguish from a data model
- •
a data model shows what persists in storage; a domain model can include attributeless or purely behavioral conceptual classes that a data modeler would exclude
- •
- •
How to build one (bounded by the current iteration's requirement)
- •
find Conceptual Classes
- •
draw them as classes in a UML class diagram (no operations)
- •
add associations that need to be remembered
- •
add attributes needed to fulfill information requirements
- •
- •
- •