Scribd
Upload
16 views24 pages

03-Week UMLSWE316

Uploaded by

Diaa Uliyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views24 pages

03-Week UMLSWE316

Uploaded by

Diaa Uliyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

Revisiting the

Unified Modeling Language (UML)

Dr. Aakash Ahmad Abbasi


Assistant Professor | [email protected]

College of Computer Science and Engineering


University of Ha’il, KSA
Lecture Agenda
▪ What is UML and Why UML?
▪ Types of UML Diagrams
▪ Structural & Behavioural Diagrams
▪ Package Diagram
▪ Deployment, Component Diagrams
▪ Activity, State Transition Diagram
What is Unified Modeling Language (UML)?
▪ The Unified Modeling Language emerged in 1993 and is a set of 13
different diagram types that may be used to model software systems.

▪ A major revision (UML 2.0) was finalized in 2004. The UML is universally
accepted as the standard approach for developing Object-oriented
models of software systems.

▪ UML 2 has many types of diagrams which are divided into two
categories namely Structural Diagrams and Behavioural Diagrams.
Why UML?
 Different diagrams describe various facets of the model

 Several diagrams of the same kind may coexist

 Each diagram shows a projection of the model

 Incoherence between diagrams (of the same or of different


kind(s)) correspond to an ill-formed model
Types of UML Diagrams
Types of UML Diagrams
Structural Diagrams
▪ Structure diagrams define the static architecture of a model. They are used to
model the 'things' that make up a model - the classes, objects, interfaces and
physical components. In addition, they are used to model the relationships
and dependencies between elements.
Behavioral Modeling Diagrams
▪ Behavior diagrams capture the varieties of interaction and instantaneous
states within a model as it 'executes' over time; tracking how the system will
act in a real-world environment, and observing the effects of an operation or
event, including its results.
Overview of UML Notations
Overview of UML notations 1/4

• Actor:
Overview of UML notations 1/4
• Actor:

• Use Case
Overview of UML notations 2/4

• Relation
among
Actors:
Overview of UML notations 2/4
• Relation
among
Actors:

• Relation
among
Use Cases
Overview of UML notations 3/4

• Classes:
Overview of UML notations 3/4
• Classes:

• Relations
Overview of UML notations 3/4
• Classes:

• Relations
Overview of UML notations 3/4
• Classes:

• Relations
Overview of UML notations 3/4
• Classes:

Association Composition

• Relations

Aggregation Dependency
Overview of UML notations 4/4
• Relations
Inheritance

Realization
Package Diagrams

 Package diagrams are used to reflect the organisation of packages and their elements.

 When used to represent class elements, package diagrams provide a visualization of the
namespaces.

 The most common use for package diagrams is to organise use case diagrams and class
diagrams, although the use of package diagrams is not limited to these UML elements.

InputOutpout Graphics

Print Buffer Console Window


Component Diagrams
 Component diagrams illustrate the pieces of software, embedded controllers, etc., that will
make up a system.

 A component diagram has a higher level of abstraction than a Class Diagram - usually a
component is implemented by one or more classes (or objects) at runtime. They are building
blocks so a component can eventually encompass a large portion of a system.

UserAuthorisation ProfileCreation

ProfileCreation
ProfileCreation
UserAuthorisation
Deployment Diagrams

 A deployment diagram models the run-time architecture of a


system.

 It shows the configuration of the hardware elements (nodes) and


shows how software elements and artifacts are mapped onto
those nodes.
Activity Diagrams

 In UML, an activity diagram is used to display the sequence of activities.

 Activity diagrams show the workflow from a start point to the finish point
detailing the many decision paths that exist in the progression of events
contained in the activity.
State Machine Diagrams
 A state machine diagram models the behaviour of a single object,
specifying the sequence of events that an object goes through during its
lifetime in response to events.

 As an example, the following state machine diagram shows the states that
a door goes through during its lifetime.
Key points
 UML 2.0 as a defacto standard for software modelling allows Structural and
Behavioral Modeling of Software

 Class Diagrams
 Use case Diagrams
 Sequence Diagrams

 Package Diagram
 Deployment Diagrams
 Component Diagrams
 Activity Diagram
 State Machine Diagram

You might also like