the unified modeling language (uml) instructor: jerry gao ph.d. san jose state university email:...

The Unified Modeling Language (UML)

Instructor: Jerry Gao Ph.D.

San Jose State Universityemail: [email protected]

URL: http://www.engr.sjsu.edu/gaojerry

Sept., 2001


- Introduction to UML

- An Overview of UML

- UML Notation

- Use-Case Modeling

- Modeling Classes, Objects, and Their Relationships - Dynamic Modeling

- Advanced Dynamic Modeling: Real-Time Systems

- Physical Architectures

Jerry Gao Ph.D. 9/2001

Presentation Outline

All Rights Reserved


Introduction To UML


What is UML?

The UML is a modeling tool (or methodology) for software engineers and system analysts.

It is designed to support all phases of software development, including

- Requirements analysis and specification- Software design specification- Software code generation- Testing systems and modules in a black box view

Why UML?- Software developments need consistent and standard modelingtool (or methods) to all phases of software development

>- understandable, consistent, simple, and powerful- Too many methods


Introduction To UML


The goals of UML (stated by the designers):

- To model systems using Object-Oriented Concepts- To establish an explicit coupling to conceptual as well as executable

artifacts- To address the issue of scale inherent in complex, mission-critical systems - To create a modeling language usable by both humans and machines.

Use of UML: (The UML has a broad spectrum of usage)

- business modeling- software modeling in all phases of development for various systems


Introduction To UML


History of UML:

- Grady Booch and James Rumbaugh at Rational Software Corp.Started the work on UML in 1994. In the initial work, theyunite the Booch method and the MOT-2 method.

- In 1995 systems, Ivar Jacobson (OOSE and Objectory methods) joined them.

- Rational bought Objective System (the Swedish company)They started to work on UML to create a unified modeling method and tool


Introduction To UML


The Acceptance of UML:

- During 1996, a number of companies and organizations joinedRational to form the UML Partners consortium.

- 1997, many companies joined them:IBM, OCON, HP, DEC, Microsoft, Oracle, TI,….

- 1997 OMG has decide to use UML as their standard and is working on the final details of the specification.


The View of UML


Component View

Local View

Use-CaseView

Deployment View Concurrency

View


An Overview of UML


Software Application

System

Use-Case View:- Describe the functionality of the system from an external view- Focus on system function usage from the user point of view- Described in use-case diagrams- Used to support users, operators, designers, developers, and testers

External viewUse-CaseDiagrams

What are thesystem functions?


Use-Case Diagram for An Insurance Business


Signing aninsurance policy

Sale statistics

Customer statistics

CustomerInsurance Salesperson


An Overview of UML


Logical View:

- Describe how the system functionality is provided- Focus on internal logic structures and elements of the system- Provide diagrams to represent static structure & dynamic behaviors of the system - Used to support designers and developers

internal viewStatic modeling diagramsDynamic modeling diagrams

How do they work?

Software Application System


A Class Diagram for Financial Trading


Customer Portfolio Trader

Instrument

Bond Stock Stock Option

1 Owns 1..* 1..* Handles 1

0..*

0..*

Con

tain

sC

onta

ins


A Class Diagram and An Object Diagram


1..*

Author

Name:Stringage: integer

Computer

Name:Stringmemory: integer

Uses0..1Class diagram

Bob:Author

Name:”Bob J.”age: 32

Bob’s Job PCComputer

Name:”Dell 466”memory: 64

Object diagram


A State Diagram for An Elevator


On first floor

Movingup

MovingDown Idle

Moving tofirst floor

Go up(floor)

Active at floor

Go up(floor)

Arrive at floor

Go down(floor)

Arrive at first floor

Time out


A Sequence Diagram For A Printer Server


:Computer :PrinterServer :Printer :QueuePrint(file)

Print(file) [printer free]Print(file)

[printer busy]Store(file)


A Collaboration Diagram For A Printer Server


:Computer

:PrinterServer :Printer

:Queue

1:Print(file)

[printer busy]1.2:Store(file)

[printer free]1.1:Print(file)


Component View of UML


Component View:

- Describe the implementation modules and their dependencies.- Focus on system structure at the component integration level- Provide component diagrams with component structures and dependencies- Used to support developers

Component viewComponent diagrams

What is the system structureand component interactions?

Component



An Activity Diagram Example


PrintFile()

RemoveMessageBox Create

postscript file

Show MessageBox

“Print” onScreen

ShowMessageBox“Disk full”on Screen

[Disk full]

[free disk space]

^Printer.Print(file)


A Component Diagram Example


WindowHandler

(whnd.cpp)

CommHandler

(comhnd.cpp)

WindowHandler

(whnd.obj)

Graphic lib(graphic.dll)

MainClass

(main.cpp)

CommHandler

(comhnd.obj)

ClientProgram

(client.exe)

MainClass

(main.obj)


An Overview of UML


Concurrency View:

- View the system as processes and processors. - Focus on parallel execution, concurrent threads, their communications

and synchronization- Provide dynamic diagrams and implementation diagrams - Designed for developers and integrators of the system

Concurrency viewImplementation modeling diagramsDynamic modeling diagrams

What are processes?How do they interact?


P1

P3

P2

process


An Overview of UML


Deployment View:

- Describe show the physical deployment of the system (or physical architecture)in terms of devices and computers

- Focus on physical parts of the system and their connections- Provide deployment diagrams- Used to support developers, integrators, and testers

physical viewDeployment diagrams

What is the physical architecture?


A Deployment Diagram (physical architecture)


Client A:Compaq Pro PC

Client B:Compaq Pro PC

DatabaseServerVAX

ApplicationServer:

Silicon Graphics O2

<<TCI/IP>>

<<TCI/IP>>

<<DecNet>>


UML Notation - Model Elements


Class

Attributes

Operations

Object

Attributes

Operations

State

Node

Use caseInterface

Package ComponentNote


UML Notation - Model Elements


Aggregation

Dependency Association

Generalization

ClassanObject:

Class


The Results of the UML Modeling


Use-case Diagrams

Activity Diagrams

Sequence Diagrams

State Diagrams

Class Diagrams

Collaboration Diagrams

Component Diagrams

Deployment Diagrams

CommonRepository


The UML: Use-Case Modeling





Sept., 2001


Use-Case Modeling


Use-Case Modeling:- use the use-case diagrams to describe a system- represent the functionality of the system- present a use-case view of the system- an iterative process

The major components of a use-case model:- use cases, actors, and the system and relationships.

- The functionality is represented by a number of use cases. - Each of them specifies a complete functional feature.

Purpose of use cases:- to describe the functional requirements of the system- to provide a clear and consistent description of what the system do- to provide a basis for system tests- to make functional requirements traceable


Use-Case Diagram for An Insurance Business


Signing aninsurance policy

Sale statistics

Customer statistics

CustomerInsurance Salesperson


Use-Case Modeling


How to perform use-case modeling?

- Step #1: Finding actors.- An actor is someone interacting with the system.such as users, operators, or another system…- Actor is a type, not instance.

- Step #2: Find the relationships between actors- Generalization relationship between actors (inheritance)

- Step #3: Define use cases.- A use case represents a complete functionality of the systemfrom an actor point’s of view

- Step #4: Identify the relationships between use cases


Use-Case Modeling


Finding actors by asking the following questions:

- Who will use the system?

- Who will support and maintain the system?

- Who will perform administration work for the system?

- What other systems or (hardware) are interested the results from the system?

- What other systems or (hardware) may generate input information or signals to the system?


Generalization between customer actors


Customer

Telephone CustomerPersonal Visitor Customer


Use-Case Modeling


Characteristics of use cases:

- A use case is always initiated by an actor.- A use case provides value to an actor. - A use case is complete.- Use cases are connected to actors through associations.

Relationships between use cases:

- Extends relationship: one use case extends another use case by adding actions to a general use case.

- Use relationship: one use case uses another use case.

- Grouping:a number of use cases handle similar functionality.


Notations for Use Cases in UML


Actor Name

Use-casename

CommunicationAssociation

Use-caseA

Use-caseB

Use-caseC

System Name


Relationships Between Use Cases in UML


Signing insurance policy

Signing Car Purchase Insurance

<<Extends>>

Signing insurance policy

Signing Life Insurance

<<uses>>

Signing Car Insurance

<<uses>>


Describing Use Cases


The description of the use case is normally done through a text description. It also can be described through an activity diagram.

It is about how the actors and the use cases interact.The description of a use case should include:

- Objective for the use case

- How the use case is initiated

- The flow of messages between actors and the use case

- Alternative flow in the use case

- How the use case finishes with a value to the actor


A Use Case Example



An Activity Diagram Example


Inserts coinsinto machine

Check that enoughcoins have been inserted?

Show that drinknow can be chosen

Chose drink

Show that drinkis not available

Deliver drink

[drink available]

[drink not available]


The UML: Object-Oriented Modeling





Sept., 2001


Object-Oriented Modeling


Object-Oriented Modeling:- Focus on classes, objects and their relationships in the system- Represent the system using class diagrams and object diagrams- Is an iterative process

The major elements of the object-oriented modeling:- classes, objects and their relationships.

Purpose of object-oriented modeling:- to describe the system in terms of classes and objects- to provide a complete object-oriented view of the system - to help the understanding of the system through object-oriented analysis and modeling


A Class Diagram and An Object Diagram


1..*

Author

Name:Stringage: integer

Computer

Name:Stringmemory: integer

Uses0..1Class diagram

Bob:Author

Name:”Bob J.”age: 32

Bob’s Job PCComputer

Name:”Dell 466”memory: 64

Object diagram


Object-Oriented Modeling


How to perform object-oriented modeling?

- Step #1: Identify classes and objects in the system.- Find classes in the system- Identify their names and attributes- Identify their operations or functions

- Step #2: Find the relationships between classes- Find association relationships between classes- Find aggregation relationships between classes- Find inheritance (generalization) relationship between classes- Define the roles and cardinality of each class in the relationships.

- Step #3: Generate object diagrams based class diagrams


Finding Classes


Finding classes by asking the following questions:

- Do we have information that should be stored or analyzed?If so, check information-oriented classes. such as input/output

- Do we have external systems? If so, check the interface classes.

- Do we use any components, libraries? If so, check component-orientedclasses and library-oriented classes.

- Do we have any customers or users? If so, check user-oriented classes.

- Do we handle any devices? If so, check hardware-oriented interface classes.

- Do we have any business structure or organization involved in the system? If so, find organization-oriented classes.


Class Examples


Student

Name:Stringage: integerSS#: StringGPA: float

ReadStudent();UpdateStudent();CreateStudent();PrintStudent();

Figure

Size: Sizeposition: PositionType: FigureType

draw();setFiguer();scaleFigure();returnPosition();

operations

attributes


Association Relationship Between Classes


Student ComputerOwns

Student ComputerOwns

1..* 0..*

Multiplicity:

default one-to-one0..1 zero-to-one0..* or * zero-to-many1..* one-to-many


Roles in Association Relationship Between Classes


Person

married to

wife

husband

A husband is married to a wife. Both husband and wife are people.If a person is not married, then he or she cannot play the role of husband or wife, which means the married to association is not applicable.

Car Persondrives* *

company car driver

role

A person plays the role of a driver, and a car plays the role of a company car the relationship.


Aggregation Relationship Between Classes


Navy WarshipContains

Team Personmembers

* *

** Normal Aggregation

Shared Aggregation

A team is composed of team members. One person could be a member of many teams.


Aggregation Relationship Between Classes


Composition Aggregation

window

listbox

text

button

menu

*

*

*

*

contains


Generalization Relationship Between Classes


Normal Generalization -> Inheritance

Part-timeStudent

Student

Full-timeStudent

Part-timeStudent

Student

Full-timeStudent


A Class Diagram for Financial Trading


Customer Portfolio Trader

Instrument

Bond Stock Stock Option

1 Owns 1..* 1..* Handles 1

0..*

0..*

Con

tain

sC

onta

ins


Packages


Subsystem B

Subsystem A

Subsystem E

Subsystem C

Subsystem D

dependency


Packages


Subsystem B

Subsystem A

Subsystem D

Subsystem C

Subsystem E


The UML: Dynamic Modeling





Sept., 2001


Dynamic Modeling


Dynamic Modeling:- Focus on dynamic behaviors in the system- Use state, sequence, collaboration, and activity diagramsto present the behaviors of the system- Demonstrate how the objects interact dynamically

The results of dynamic modeling:

- State diagrams: -> describing object states and their changes in terms of events.

- Sequence diagrams:-> describing how objects interact and communicate with each other.

- Collaboration diagrams:-> describing how objects collaborate together by interactions

- Activity diagrams: -> another shows the object interactions for functionality and actors.


The Notation of State Diagram


State 1 State 2Event

State

starting point

State

end point

State Name

State Vars

Activities




On first floor

Movingup

MovingDown Idle


Go up(floor)

Active at floor

Go up(floor)

Arrive at floor

Go down(floor)


Time out




On first floor

Moving up

do/moving to floor

Moving down

do/moving to floor

Idletimer = 0

do/increase timer


Go up(floor)Active at floor

Go up(floor)

Arrive at floor

Go down(floor)


[Timer = time out] Guard-condition

Dynamic Modeling




Sept., 2001

Topic: The Unified Modeling Language


Sending Messages between State Diagrams

All Rights Reserved

Off On

On()

Off()

Play()Stop()

Off On/Stop

On()

Off()

Off()/Stop()

On/Play

Play()

Stop()

CD PlayerStop()Play()On() Off()

Remote control

Sequence Diagram




Sept., 2001

Sequence Diagram

Sequence diagrams:- illustrate how objects interact with each other.- focus on interacting message sequences between objects

:ObjectNameSimple message

Synchronous message

[Guard-condition]

Return

Activation

lifeline

Sequence Diagram Example

:Computer

Print(ps-file)

Activation

lifeline


Print(ps-file)

Object[no queue]Print(ps-file)

Guard-condition

Synchronousmessage

Return

simplemessage


:Computer

Print(file)


Print(file)

[printer free]Print(file)

:Queue

[printer busy]Store(file)

Collaboration Diagram




Sept., 2001


Collaboration diagrams:- illustrate the interactions of objects.- focus on space instead of time.

Applications:- may be used to show the execution of an operation- may be used to show a use-case execution- simply an interaction scenario in the system


Object name: classOper()

Oper()The Oper( ) operation call itself.


:Computer


Print(ps-file)

1:Print(ps-file)

[printer free] 1.1:Print(ps-file)

Collaboration Diagram Example

:MainWindow :Customer{new}

:CustomerWindow{transient}

NewCustomer()

2:Create()

[free memory] 1:Create()

3:Show(Customer)

3:Update(data)

{parameter}

Collaboration Diagram Example

:Queue :Elevator

:Order{new}

{parameter}job

2: nextjob=GetJob()

{local}nextjob:Elevator control

1.1 *[all queues]:len = Length(){broadcast}1.3:invoke(job)

:Button

1.2: Create( )Push( )

1:GetElevator(floorid)job

Activity Diagram




Sept., 2001

Activity Diagram

Activity diagrams:- focus on work performed in the implementation of an operation and activities in a use-case instance or in an object- capture actions and results in terms of object state changes.

Activity diagrams are used for different purposes:- to capture the work that will be performed when an operation is executing.- to capture the internal work in an object.- to show how a set of related actions may be performed, and how they will affect objects around them.- to show an instance of a use-case may be performed in termsof actions and object state changes.- to show how a business works in terms of workers, workflows,organization, and objects.

Activity Diagram Example - Show a sequence of interactions

Show MessageBox“Printing” on screen

Create postscript file

Remove MessageBox Send postscriptfile to printer

CustomerWindow.PrinterAllCustomers()




Remove MessageBox

^Printer.Printer(file)


Send-clause



Show MessageBox“Disk full” on thescreen

Remove MessageBox



[disk full]

[free disk space]

^Printer.Printer(file)

Send-clause


initiate

MeasuringUpdatingdisplayer

Sampler.Run(channel, frequency)

Performing concurrent actions

the unified modeling language (uml) instructor: jerry gao ph.d. san jose state university email:...

Documents

overview of uml

goals of uml

acceptance of uml

uml notation use

unified modeling method

uml partners consortium

modeling language usable

standard modeling tool