FIT2001 Lecture Notes - Lecture 7: Class Diagram
L7 - Investigating and documenting system requirements - Domain &
Class modelling
Domain Modelling
A model of ‘things’ in a system that analysts need to keep information about in the business
problem domain. A live collaborative artefact, refine and updated throughout the systems
development.
A UML class diagram which represents ‘things’ as a class of objects.
How to Develop one
1. Identifying the list of things
○Noun identifying the use case description
○Brainstorm the things that are important to stakeholders
2. Find associations among the classes
○A relationship between instances of ‘things that indicate some meaningful
connection
○Simple Association is relationship specifies a non-aggregate and non-composite
simple association between two classes
3. Find the number of association between classes - Multiplicity of Associations
Cardinality
Multiplicity Indicator
Meaning
0..1
Zero or one
1
One only
Document Summary
L7 - investigating and documenting system requirements - domain & A model of things" in a system that analysts need to keep information about in the business problem domain. A live collaborative artefact, refine and updated throughout the systems development. A uml class diagram which represents things" as a class of objects. Brainstorm the things that are important to stakeholders: find associations among the classes. A relationship between instances of things that indicate some meaningful connection. Simple association is relationship specifies a non-aggregate and non-composite simple association between two classes: find the number of association between classes - multiplicity of associations. One to n (cid:840) n >1(cid:841: check of association classes - add them in. Used to capture characteristics of an association between two classes. Characteristics belong to the relationship between the classes. Attribute -\ a piece of information about a thing. Identifier/key - an attribute that uniquely identify a thing.