SWD 392 - Software
Architecture and Design
SWD392
Static Modeling
Design Concepts Objects and Classes
● Objects represent ‘’thing’’ in real world
- Provide understanding of real world
- Form basis for a computer solution
● An Object (object instance) is a single ‘’thing’’
- E.g., an account, an employee
● A Class (object class) is a collection of objects with the same
characteristics
- E.g., account, employee
● Atrribute
- Data value held by objects in class
- E.g., account number, balance
Example of classes and objects
Static Modeling
• Define structural relationships between classes
• Depict classes and their relationships on class diagram
• Relationships between classes
• Associations
• Composition / Aggregation
• Generalization / Specialization
• Static Modeling during Analysis
• System Context Class Diagram
o Depict external classes and system boundary
• Static Modeling of Entity classes
o Persistent classes that store data
UML notation for relationship on class diagram
UML notation for relationship on class diagram
What is Associations
Example
Numerically specified
One-to-one association association
Example
Optional (zero, one, or many) association
Association Class
Composition/Aggregation Hierarchy
Example of composition hierarchy
Example of aggregation hierarchy
Generalization / Specialization Hierarchy
Generalization / Specialization Hierarchy
Conceptual static model for Banking System
Software System Context Class Diagram
Banking System software context class diagram
Static Modeling of Entity Classes
Conceptual static model for Banking System - entity classes
Conceptual static model for Banking System
Steps in Using COMET/UML
Thanks!
Does anyone have any questions?
CREDITS: This presentation template was
created by Slidesgo, including icons by
Flaticon, infographics & images by Freepik
Please keep this slide for attribution