CT015-3-2 Design Methods

Object Oriented Analysis and

Modelling Part 1
 Learning Objectives

At the end of this lecture, you should be

able to :
- Understand UML Model and Diagram
- Creating UML diagrams in models

Module Code and Module Title Title of Slides #

 UML

Unified Modeling Language

A standard language for specifying,
visualizing, constructing, and documenting
the artifacts of software systems.
Developed to provide standardized
graphical language and notations for
describing object oriented model

Module Code and Module Title Title of Slides #

 UML Model
Use models to:
Specify structure, behavior, or both
Visualize an existing system to improve understanding
Automate system development (Model-Driven Development)
UML model files (.emx) contain:
Model elements
Diagrams
Profile information
User preferences
Workspace information

Module Code and Module Title Title of Slides #

 Developing multiple model

You can model a system using

multiple models
How many models to use
depends on:
The modelled system and model complexity
Team development and configuration
management considerations
Organizational standards and practices
Your own preference

Module Code and Module Title Title of Slides #

 UML Diagrams
UML diagrams graphically depict a view of a part of your
model or code
Different diagrams represent different views of the system
you are developing
A model element appears in zero or more diagrams

Module Code and Module Title Title of Slides #

 UML diagram versus UML model

A model can contain one or more diagrams.

A diagram presents a view of parts of a model.
A model element that appears only once in your
model can appear in one or more diagrams.
Different diagrams present different contexts.

Module Code and Module Title Title of Slides #

 UML Diagrams Types

Module Code and Module Title Title of Slides #

 How many diagrams do you
need?
Depends on the artifacts being modeled and the needs of
users
Use diagrams to visualize the system from different
perspectives
No complex system can be understood in its entirety from
only one perspective
Model elements can appear in zero or more diagrams
A class can:
Appear in zero or more class diagrams
Be represented in a state machine diagram
Have instances that appear on a sequence diagram
Each diagram provides a different perspective
Module Code and Module Title Title of Slides #
 Creating UML diagrams

Use diagrams to represent different views of the system

or application:
UML diagrams
Non-UML (freeform) diagrams
Create diagrams in:
Models
Model elements
Packages
Components
And so on

Module Code and Module Title Title of Slides #

 Freeform diagrams and geometric
shapes
Freeform diagrams can include UML and non-UML
elements
Default diagram included when creating UML packages
Display geometric shapes and other non-UML notation
Use for sketches and other informal modeling

Module Code and Module Title Title of Slides #

 Review : Diagram editor

Module Code and Module Title Title of Slides #

 Review

What is UML?
List all UML diagram.
What is free form diagrams?

Module Code and Module Title Title of Slides #

 Q&A

Module Code and Module Title Title of Slides #