UML Basics

UML Basics

Process Model

Deployment Model

Design Model

1
 UML Basics

Contents -
 Models
 Use-case model
 Design model (Class diagram)

 Diagrams
 Use-case diagram and activity diagram
 Sequence diagram and communication diagram
 Component diagram and deployment diagram
 Topic diagram and browse diagram

 How many diagrams need to be created?

2
 UML Basics

What Is a Model?
 A model is “a complete description of a system from a
particular perspective.” A model is a simplification of reality.

3
 UML Basics

Why Model?
 Modeling achieves four aims:
Helps you to visualize a system as you want it to be.
Permits you to specify the structure or behavior of a
system.
Gives you a template that guides you in constructing a
system.
Documents the decisions you have made.
 You build models of complex systems because you
cannot comprehend such a system in its entirety.
 You build models to better understand the system
you are developing.
4
 UML Basics

Importance of Modeling
Applications approaching like building paper airplanes
Start coding from project requirements
Work longer hours and create more code
Lacks any planned architecture
Doomed to failure
Modeling is a common thread to successful projects
Less Important More Important

5
 UML Basics

Four Principles of Modeling

 The model you choose influences how the problem is
attacked.

Process Model Deployment Model Design Model

 Every model may be expressed at different levels of

precision.

 The best models are connected to reality.

 No single model is sufficient.

6
 UML Basics

What Is the UML?

 The UML is a language for
 Visualizing
 Specifying
 Constructing
 Documenting

the artifacts of a software-intensive system.

 The Unified Modelling Language (UML) is an

industry standard for object oriented design
notation, supported by the Object Management
Group (OMG).

7
 UML Basics

The UML Is a Language for Visualizing

 Communicating conceptual models

to others is prone to error unless
everyone involved speaks the
same language.
 There are things about a software
system you can’t understand
unless you build models.
 An explicit model facilitates
communication.

8
 UML Basics

The UML Is a Language for Specifying

 The UML builds models that are precise,
unambiguous, and complete.

9
 UML Basics

The UML Is a Language for Constructing

 UML models can be directly connected to a

variety of programming languages.
Maps to Java, C++, Visual Basic, and so on
Tables in a RDBMS or persistent store in an
OODBMS
Permits forward engineering
Permits reverse engineering

10
 UML Basics

The UML Is a Language for Documenting

 The UML addresses documentation of system architecture,
requirements, tests, project planning, and release
management.
Use Case Diagram Deployment Diagram
ºÐ»ê ȯ°æÀÇ Çϵå¿þ¾î¹× ³×Æ®¿÷À¸·ÎÀÇ Á¤º¸ ½Ã½ºÅÛ ¿¬°á ¸ðµ¨
- À©µµ¿ì 95 : Ŭ¶óÀ̾ðÆ®
- À©µµ¿ì NT: ÀÀ¿ë¼-¹ö
- À¯´Ð½º ¸Ó½Å: ÀÀ¿ë ¼-¹ö ¹× µ¥ÀÌŸ ¼-¹ö, Åë½Å ¼-¹ö
- IBM ¸ÞÀÎÇÁ·¹ÀÓ: µ¥ÀÌŸ ¼-¹ö, Åë½Å ¼-¹ö

Windows95
Window95

Use Case 1
Windows95

¹®¼-°ü¸®
Ŭ¶óÀ̾ðÆ®.EXE
¹®¼-°ü¸® ¾ÖÇø´

Windows
NT

Actor A Actor B
Use Case 2 Solaris

¹®¼-°ü¸® ¿£Áø.EXE

Alpha
UNIX
ÀÀ¿ë¼-¹ö.EXE

Windows
NT

IBM

Use Case 3 Mainframe

µ¥ÀÌŸº£À̽º¼-¹ö

DocumentList

mainWnd fileMgr : document : gFile repository

Document
FileMgr
FileMgr Document
user
add( )
name : int
fetchDoc( ) delete( )
docid : int
sortByName( )
numField : int

1: Doc view request ( ) get( )

ƯÁ¤¹®¼-¿¡ ´ëÇÑ º¸±â¸¦
»ç¿ëÀÚ°¡ ¿äûÇÑ´Ù. read() fill the
open( )

code..
close( )

2: fetchDoc( ) read( )
FileList

sortFileList( )
fList
create( )
3: create ( )
fillDocument( )
add( )

delete( )

4: create ( ) 1

5: readDoc ( )

È-ÀÏ°ü¸®ÀÚ´Â Àоî¿Â 6: fillDocument ( )

¹®¼-ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼-
°´Ã¼¿¡ ¼³Á¤À» ¿äûÇÑ´Ù.

rep

7: readFile ( )

File
Repository

8: fillFile ( )
(from Persistence)
read( ) GrpFile

È-¸é °´Ã¼´Â ÀоîµéÀÎ 9: sortByName ( ) name : char * = 0

°´Ã¼µé¿¡ ´ëÇØ À̸§º°·Î
Á¤·ÄÀ» ½ÃÄÑ È-¸é¿¡
read( )
º¸¿©ÁØ´Ù. readDoc( )
open( )
readFile( )
create( )

fillFile( )

Sequence Diagram Class Diagram

11
 UML Basics

History of the UML

UML 2.0
(2004)

UML 1.5
(March, ‘03)

UML 1.1
(Sept. ‘97)

UML 1.0
(Jan. ‘97)

UML 0.9 and UML 0.91

(June ‘96) (Oct. ‘96)
Public
Unified Method 0.8 Feedback
(OOPSLA ’95)

Booch ’93 OMT - 2

OOSE Other Booch ‘91 OMT - 1

Methods

12
 UML Basics

Diagrams
 Diagrams graphically depict a view of a part of your
model.
 Different diagrams represent different views of the
system that you are developing.
 A model element will appear on one or more diagrams.

13
 UML Basics

UML Diagrams in Software Architecture

Structural
Diagrams

Use-Case Class
Diagrams Diagrams
Composite
Sequence Structure
Diagrams Diagrams

Communication Component
Diagrams Model Diagrams

State Machine Deployment

Diagrams Diagrams
Activity
Behavioral Diagrams
Diagrams

14
 UML Basics

Key Diagrams in UML

Use Case Diagrams

Requirements

Class Diagrams
System Structure
Collaboration Diagrams

Interaction Diagrams
Activity Diagrams
System Behaviour State Charts

15
 UML Basics

Different diagrams of system for different people

Logical View Implementation View

Analysts/Designers Programmers

Structure Software management

Use-Case View

End-user
Functionality

Process View Deployment View

System engineering
System integrators System topology, delivery,
installation, communication
Performance, scalability, throughput

16
 UML Basics

What is a Use-Case Model?

A use-case model:
Is a model of a system’s intended functions and
its environment
Serves as a contract between the customer and
the developers
Contains the following diagrams:
 Use case: Shows a set of use cases and actors and their
relationships
 Activity: Shows the flow of events within a use case
 Sequence: Shows how a use case will be implemented in
terms of collaborating objects

17
 UML Basics

Use-Case Diagram (Example)

View Report Card

Course Catalog
Maintain Professor
Register for Courses Information

Student

Login Maintain Student

Information

Registrar

Select Courses to
Teach Close Registration

Professor

Submit Grades

Billing System

18
 UML Basics

Activity Diagram
Action
A step in the flow of events

Decision
Flows split based on a guard
condition

Fork
Beginning of concurrent flows

Join
End of concurrent flow

Flow
Show the sequence of
activities

19
 UML Basics

Activity Diagram (Example)

Decision Activity/Action
Select Course
Concurrent
Threads [ delete course ]
Delete Course
[ add course ]

Synchronization
Bar (Fork)
Check Check
Guard Schedule Pre-requisites
Condition
Synchronization
[ checks completed ] [ checks failed ] Bar (Join)

Assign to Resolve
Course Conflicts
Transition

Update
Schedule

20
 UML Basics

What is a Design Model?

A design model:
Describes the realization of use cases in terms of design elements
Describes the design of the application
Contains the following diagrams:
 Class: Shows UML classes and relationships
 Component: Shows the structure of elements in the implementation model
 Communication and Sequence: Show how objects and classes interact
 State Machine: Shows event-driven behavior

21
 UML Basics

Class Diagram (Design Model)

Class diagrams show the static structure of the model, in
particular, its classes, their internal structure, and their
relationships to other classes. Class diagrams do not
show temporal information.

Class
A description of a set
of objects
Aggregation
Represents a part-whole
relationship
Attribute
Named property of
a class
Operation
Class behavior

Generalization
Shows an inheritance
relationship

22
 UML Basics

Sequence Diagram
used to show how objects interact to perform the
behavior of all or part of a use case as part of a use-case
realization.
Object/Class
Shows the object/class
involved in the
interaction

Messages
Show data exchanged
between objects

Execution Occurrence
Shows object executing Lifeline
Shows the life of the object
23
 UML Basics

Sequence Diagram (Example)

:RegisterForCoursesForm :RegistrationController SWTSU Catalog :
CourseCatalogSystem Activity/Action
: Student : Course Catalog

1: create schedule( )

2: get course offerings( )

3: get course offerings(for Semester)

4: get course offerings( )

5: display course offerings( )

6: display blank schedule( )

ref
Select Offerings

24
 UML Basics

Sequence Diagram: Combined Fragments

Interaction Use (ref)

References another interaction

Optional Fragment (opt)

Executed if guard condition
evaluates to true

Loop (loop)
Executed as long as the first
guard condition
evaluates to true

25
 UML Basics

Communication (Collaboration) Diagram

provide another way to show how objects interact to perform the
behavior of a particular use case or a part of a use case. Where
sequence diagrams emphasize the interactions of objects over time,
communication diagrams are designed to emphasize the
relationships between objects.

Object/Class
Shows the
object/class involved
in the interaction

Message
Shows data
exchanged
between objects

26
 UML Basics

Communication Diagram (Example)

Messages 5: display course offerings( )

6: display blank schedule( )

1: create schedule( ) Links : Course Catalog

: RegisterForCoursesForm

: Student
2: get course offerings( )
4: get course offerings( )

3: get course offerings(forSemester)

: RegistrationController : CourseCatalogSystem

27
 UML Basics

Component Diagram
It shows the runtime structure of the system at the level of software
components. Components are the modular parts of the system and
are made up of groups of related objects that are hidden behind an
external interface.

Component Class
Modular parts of the system Included to show implementation
relationships.
28
 UML Basics

Deployment Diagram
Deployment diagrams show the deployment architecture of the
system, that is, which of the system’s software artifacts reside
on which pieces of hardware.

Artifact
Represents a physical file

Owned Element
Relationship
Shows another way of
showing nested elements

Node
Represents a
physical machine

29
 UML Basics

How Many Diagrams Need to be Created?

 Depends:
You use diagrams to visualize the system from different perspectives.
No complex system can be understood in its entirety from one perspective.
Diagrams are used for communication
 Model elements will appear on one or more diagrams.
For example, a class may appear on one or more class diagrams, be represented in a state machine diagram, and have instances
appear on a sequence diagram.
Each diagram will provide a different perspective.

30
 UML Basics

References
 Rational Unified Process® course
 Essentials of Rational Unified Process®
Essentials of Rational® RequisitePro®
 Web-based or Instructor-led training
Mastering Business Modeling with the UML
 Web sites
Rational’s corporate site: www.rational.com
Rational Developer NetworkSM: www.rational.net
 Books and articles about requirements management

31
 UML Basics

THANK YOU

32