8/15/2019 OOSE_Week 05 - Domain Model

1/10

1

Domain model: visualizingconcepts

 Applying UML and Patterns

-Craig Larman

8/15/2019 OOSE_Week 05 - Domain Model

2/10

2

Domain Model Relationships

Domain Model

Use Case Model

Interaction Diagrams

Glossary

Design

Requirements

Business Model

Classes, attributes,

associations

Domain

objects

Elaboration on some terms

8/15/2019 OOSE_Week 05 - Domain Model

3/10

3

A Domain Model illustrates meaningful conceptual classes in a problem

domain. is a representation of real-world concepts not software

components. is !"# a set of diagrams describing software classes or

software ob$ects and t%eir responsibilities. &t may s%ow'

( concepts

( associations between concepts ( attributes of concepts

8/15/2019 OOSE_Week 05 - Domain Model

4/10

)

Domain Model

UML Notation &llustrated using a set of class diagrams for w%ic% no operations are

defined. 

 A *omain Model is a description of t%ings

in t%e real world.

( A *omain Model is not a description oft%e software design.( A concept is an idea

  t%ing or ob$ect.

8/15/2019 OOSE_Week 05 - Domain Model

5/10

+

A Domain Model is not a

Software Artifact

,ale

*ate

#ime

,ales *atabase

,ale

*ate#ime

Print

 A Conceptual class' ,oftware Artifacts'

/s.

8/15/2019 OOSE_Week 05 - Domain Model

6/10

0

Steps to create a

Domain Model

&dentify Candidate Conceptual classes

*raw t%em in a *omain Model

 Add associations necessary to record t%erelations%ips t%at must be retained

 Add attributes necessary for information to

be preser/ed Apply eisting Analysis Patterns

8/15/2019 OOSE_Week 05 - Domain Model

7/10

Monopoly oncepts

!candidates"

Monopoly Game Player Piece

Die Board quare

8/15/2019 OOSE_Week 05 - Domain Model

8/10

Monopoly #ame domain model

Larman$ %igure &'()

8/15/2019 OOSE_Week 05 - Domain Model

9/10

   A

  n  o   t   h  e  r

   *  +  a  m  p

   l  e

8/15/2019 OOSE_Week 05 - Domain Model

10/10

1

,he Ne+t#en -.S !partial" Domain

Model