Ch02lect1 UD

UsingUML,Patterns,andJava
ObjectOrientedSoftwareEngineering
Chapter2,
ModelingwithUML
Overview:modelingwithUML
Whatismodeling?
WhatisUML?
Usecasediagrams
Classdiagrams
Sequencediagrams
Activitydiagrams
BerndBruegge&AllenH.Dutoit
ObjectOrientedSoftwareEngineering:UsingUML,Patterns,andJava
Whatismodeling?
Modelingconsistsofbuildinganabstractionofreality.
Abstractionsaresimplificationsbecause:
Theyignoreirrelevantdetailsand
Theyonlyrepresenttherelevantdetails.
Whatisrelevantorirrelevantdependsonthepurposeofthe
model.
Example:streetmap
Whymodelsoftware?
Whymodelsoftware?
Softwareisgettingincreasinglymorecomplex
WindowsXP>40millionlinesofcode
Asingleprogrammercannotmanagethisamountofcodeinits
entirety.
Codeisnoteasilyunderstandablebydeveloperswhodidnot
writeit
Weneedsimplerrepresentationsforcomplexsystems
Modelingisameansfordealingwithcomplexity
ApplicationandSolutionDomain
ApplicationDomain(RequirementsAnalysis):
Theenvironmentinwhichthesystemisoperating
SolutionDomain(SystemDesign,ObjectDesign):
Theavailabletechnologiestobuildthesystem
ObjectorientedModeling
Application Domain
(Phenomena)
Solution Domain
(Phenomena)
System Model (Concepts)(Analysis)
System Model (Concepts)(Design)
TrafficControl
UML
Package
Aircraft TrafficController
Airport
FlightPlan
MapDisplay
Summary
Display
FlightPlanDatabase
TrafficControl
WhatisUML?
UML(UnifiedModelingLanguage)
Nonproprietarystandardformodelingsoftwaresystems,OMG
Convergenceofnotationsusedinobjectorientedmethods
OMT(JamesRumbaughandcollegues)
Booch(GradyBooch)
OOSE(IvarJacobson)
CurrentVersion:UML2.2
InformationattheOMGportalhttp://www.uml.org/
Commercialtools:Rational(IBM),Together(Borland),VisualArchitect
(businessprocesses,BCD)
OpenSourcetools:ArgoUML,StarUML,Umbrello
CommercialandOpensource:PoseidonUML(Gentleware)
UML:FirstPass
Youcanmodel80%ofmostproblemsbyusingabout20%
UML
Weteachyouthose20%
8020rule:Paretoprinciple
(http://en.wikipedia.org/wiki/Pareto_principle)
80%ofyourprofitscomefrom20%ofyourcustomers
80%ofyourcomplaintscomefrom20%ofyourcustomers
80%ofyourprofitscomefrom20%ofthetimeyouspend
80%ofyoursalescomefrom20%ofyourproducts
UMLFirstPass
Usecasediagrams
Describethefunctionalbehaviorofthesystemasseenbythe
user
Classdiagrams
Describethestaticstructureofthesystem:Objects,attributes,
associations
Sequencediagrams
Describethedynamicbehaviorbetweenobjectsofthesystem
Statediagrams
Describethedynamicbehaviorofanindividualobject
10
UMLCoreConventions
AllUMLDiagramsdenotegraphsofnodesandedges
Nodesareentitiesanddrawnasrectanglesorovals
Rectanglesdenoteclassesorinstances
Ovalsdenotefunctions
Names of Classes are not underlined

SimpleWatch
Firefighter
Names of Instances are underlined

myWatch:SimpleWatch
Joe:Firefighter
An edge between two nodes denotes a

relationship between the corresponding entities
11
UMLfirstpass:Usecasediagrams
Classifier
Use Case
Actor
System boundary
Use case diagrams represent the functionality of the system

from users point of view
12
UMLfirstpass:Classdiagrams
Association
Multiplicity
2
PushButton
Class
SimpleWatch
1
1
Display
1
2
Battery
1
Time
Class diagrams represent the structure of the system

13
UMLfirstpass:Classdiagrams
Class diagrams represent the structure of the system
Association
Class
Multiplicity
1
2
PushButton
state
push()
release()
Attribute
Watch
1 1 1
2
1
LCDDisplay
blinkIdx
blinkSeconds()
blinkMinutes()
blinkHours()
stopBlinking()
referesh()
Battery
Load
1
Time
Now
Operations
14
UMLfirstpass:Sequencediagram
Actor
Message
:WatchUser
Object
:Watch
pressButton1()
pressButton1()
pressButton2()
Lifeline
:LCDDisplay
:Time
blinkHours()
blinkMinutes()
incrementMinutes()
refresh()
pressButton1and2()
commitNewTime()
Activation
stopBlinking()
Sequence diagrams represent the behavior of a system

as messages (interactions) between different objects
15
UMLfirstpass:Statechartdiagrams
Initial state
Event
button1&2Pressed
Blink
Hours
Transition
button1&2Pressed
State
button2Pressed
Increment
Hours
button1Pressed
Blink
Minutes
button2Pressed
Increment
Minutes
button1Pressed
Stop
Blinking
Blink
Seconds
button2Pressed
Increment
Seconds
Final state
Represent behavior of a single object with interesting
dynamic behavior.
16
OtherUMLNotations
UMLprovidesmanyothernotations,forexample
Deploymentdiagramsformodelingconfigurations
Usefulfortestingandforreleasemanagement
Weintroducetheseandothernotationsaswegoalonginthe
lectures
OCL:AlanguageforconstrainingUMLmodels
17
Whatshouldbedonefirst?CodingorModeling?
Italldepends.
ForwardEngineering
Creationofcodefromamodel
Startwithmodeling
Greenfieldprojects
ReverseEngineering
Creationofamodelfromexistingcode
Interfaceorreengineeringprojects
RoundtripEngineering
Moveconstantlybetweenforwardandreverseengineering
Reengineeringprojects
Usefulwhenrequirements,technologyandschedulearechanging
frequently.
18
UMLSecondPass
Usecasediagrams
Describethefunctionalbehaviorofthesystemasseenbytheuser
Classdiagrams
Describethestaticstructureofthesystem:Objects,attributes,
associations
Sequencediagrams
Describethedynamicbehaviorbetweenobjectsofthesystem
Statediagrams
Describethedynamicbehaviorofanindividualobject
Activitydiagrams
Describethedynamicbehaviorofasystem,inparticularthe
workflow.
19
UMLUseCaseDiagrams
Used during requirements elicitation
and analysis to represent external
behavior (visible from the outside of
the system)
AnActorrepresentsarole,thatis,atype
ofuserofthesystem
Passenger
A use case represents a class of

functionality provided by the system
PurchaseTicket
Use case model:

The set of all use cases that
completely describe the
functionality of the system.
20
Actors
Anactorisamodelforanexternalentity
whichinteracts(communicates)withthe
system:
User
Externalsystem(Anothersystem)
Physicalenvironment(e.g.Weather)
Passenger
Name
Anactorhasauniquenameandanoptional
description
Optional
Examples:
Description
Passenger:Apersoninthetrain
GPSsatellite:Anexternalsystemthatprovides
thesystemwithGPScoordinates.
21
UseCase
PurchaseTicket
Ausecaserepresentsaclassof
functionalityprovidedbythesystem
Usecasescanbedescribedtextually,witha
focusontheeventflowbetweenactorand
system
Thetextualusecasedescriptionconsistsof
6parts:
1.
2.
3.
4.
5.
6.
Uniquename
Participatingactors
Entryconditions
Exitconditions
Flowofevents
Specialrequirements.
22
TextualUseCase
DescriptionExample
Passenger
1.Name:Purchaseticket
2.Participatingactor:Passenger
3.Entrycondition:
Passengerstandsinfrontof
ticketdistributor
Passengerhassufficient
moneytopurchaseticket
PurchaseTicket
5.Flowofevents:
1.Passengerselectsthe
numberofzonestobetraveled
2.Ticket Distributordisplays
theamountdue
3.Passengerinsertsmoney,at
leasttheamountdue
4.TicketDistributorreturns
change
5.TicketDistributorissuesticket
6.Specialrequirements:None.
4.Exitcondition:
Passengerhasticket
23
UsesCasescanberelated
ExtendsRelationship
Torepresentseldominvokedusecasesorexceptionalfunctionality
IncludesRelationship
Torepresentfunctionalbehaviorcommontomorethanoneuse
case.
24
The<<extends>>Relationship
Passenger
PurchaseTicket
<<extends>>relationshipsmodel
exceptionalorseldominvokedcases
Theexceptionaleventflowsare
factoredoutofthemaineventflowfor
clarity
Thedirectionofan<<extends>>
relationshipistotheextendedusecase
Usecasesrepresentingexceptional
flowscanextendmorethanoneuse
case.
<<extends>>
<<extends>>
<<extends>>
OutOfOrder
<<extends>>
Cancel
TimeOut
NoChange
25
The<<includes>>Relationship
Passenger
PurchaseMultiCard
PurchaseSingleTicket
<<includes>>
<<includes>>
<<extends>>
NoChange
CollectMoney
<<extends>>
Cancel
<<includes>>relationship
representscommonfunctionality
neededinmorethanoneusecase
<<includes>>behavioris
factoredoutforreuse,notbecauseit
isanexception
Thedirectionofa<<includes>>
relationshipistotheusingusecase
(unlikethedirectionofthe
<<extends>>relationship).
<<extends>>
Cancel
26
ClassDiagrams
Classdiagramsrepresentthestructureofthesystem
Used
duringrequirementsanalysistomodelapplicationdomain
concepts
duringsystemdesigntomodelsubsystems
duringobjectdesigntospecifythedetailedbehaviorand
attributesofclasses.
TarifSchedule
Tablezone2price
EnumerationgetZones()
PricegetPrice(Zone)
Trip
zone:Zone
Price:Price
27
Classes
Type
Name
TarifSchedule
zone2price
getZones()
getPrice()
TarifSchedule
Tablezone2price
PricegetPrice(Zone)
Attributes
Operations
Signature
TarifSchedule
Aclassrepresentsaconcept
Aclassencapsulatesstate(attributes)andbehavior(operations)
Each attribute has a type

Each operation has a signature
The class name is the only mandatory information
28
ActorvsClassvsObject
Actor
Anentityoutsidethesystemtobemodeled,interactingwiththe
system(Passenger)
Class
Anabstractionmodelinganentityintheapplicationorsolution
domain
Theclassispartofthesystemmodel(User,Ticketdistributor,
Server)
Object
Aspecificinstanceofaclass(Joe,thepassengerwhoispurchasing
aticketfromtheticketdistributor).
30
Associations
TarifSchedule
TripLeg
PricegetPrice(Zone)
Price
Zone
Associationsdenoterelationshipsbetweenclasses
The multiplicity of an association end denotes how many
objects the instance of a class can legitimately reference.
31
1to1and1tomanyAssociations
Country
name:String
City
name:String
1to1association
Polygon
Point
x: Integer
y: Integer
draw()
1tomanyassociation
32
ManytoManyAssociations
StockExchange
Company
tickerSymbol
33
FromProblemStatementToObjectModel
ProblemStatement:Astockexchangelistsmanycompanies.
Eachcompanyisuniquelyidentifiedbyatickersymbol
Class Diagram:
StockExchange *
Lists
Company
tickerSymbol
34
FromProblemStatementtoCode
ProblemStatement :Astockexchangelistsmanycompanies.
Eachcompanyisidentifiedbyatickersymbol
Class Diagram:
StockExchange
Java Code
Lists
Company
tickerSymbol
publicclassStockExchange
{
privateVectorm_Company=newVector();
};
Associations
are mapped to
Attributes!
publicclassCompany
{
publicintm_tickerSymbol;
privateVectorm_StockExchange=newVector();
};
35
Aggregation
Anaggregationisaspecialcaseofassociationdenotingaconsistsof
hierarchy
Exhaust system
Theaggregateistheparentclass,
thecomponentsarethechildrenclasses
1
Muffler
diameter
0..2
Tailpipe
diameter
A solid diamond denotes composition: A strong form of

aggregation where the life time of the component
instances is controlled by the aggregate. That is, the parts
dont exist on their won (the whole controls/destroys the
parts)
TicketMachine
3
ZoneButton
36
Inheritance
Button
CancelButton
ZoneButton
Inheritanceisanotherspecialcaseofanassociationdenotinga
kindofhierarchy
Inheritancesimplifiestheanalysismodelbyintroducinga
taxonomy
Thechildrenclassesinherittheattributesandoperationsofthe
parentclass.
39
Packages
PackageshelpyoutoorganizeUMLmodelstoincreasetheir
readability
WecanusetheUMLpackagemechanismtoorganizeclassesinto
subsystems
Account
Bank
Customer
Anycomplexsystemcanbedecomposedintosubsystems,where
eachsubsystemismodeledasapackage.
40
ObjectModelinginPractice
Foo
Amount
CustomerId
Deposit()
Withdraw()
GetBalance()
Class Identification: Name of Class, Attributes and Methods

Is Foo the right name?
41
ObjectModelinginPractice:Brainstorming
Foo
Dada
Amount
Amount
CustomerId
CustomerId
Deposit()
Withdraw()
GetBalance()
Deposit()
Withdraw()
GetBalance()
Account
Amount
CustomerId
Is Foo the right name?
Deposit()
Withdraw()
GetBalance()
42
ObjectModelinginPractice:Moreclasses
Account
Amount
AccountId
CustomerId
Bank
Deposit()
Withdraw()
GetBalance()
Name
Customer
Name
CustomerId
1) Find New Classes

2) Review Names, Attributes and Methods
43
ObjectModelinginPractice:Associations
Account
Bank
?
has
Amount
AccountId
CustomerId
AccountId
owns
Deposit()
Withdraw()
GetBalance()
Name
Customer
2
Name
CustomerId
1) Find New Classes

2) Review Names, Attributes and Methods
3) Find Associations between Classes
4) Label the generic assocations
5) Determine the multiplicity of the assocations
6) Review associations
44
PracticeObjectModeling:FindTaxonomies
Account
Bank
Name
Amount
AccountId
CustomerId
AccountId
Customer
Has
Deposit()
Withdraw()
GetBalance()
Savings
Account
Withdraw()
Name
CustomerId()
Checking
Account
Mortgage
Account
Withdraw()
Withdraw()
45
PracticeObjectModeling:Simplify,Organize
Account
Amount
AccountId
CustomerId
AccountId
Deposit()
Withdraw()
GetBalance()
Savings
Account
Withdraw()
Show Taxonomies
separately
Checking
Account
Mortgage
Account
Withdraw()
Withdraw()
46
PracticeObjectModeling:Simplify,Organize
Bank
Name
Account
Amount
AccountId
CustomerId
AccountId
Customer
Has
Deposit()
Withdraw()
GetBalance()
Name
CustomerId()
Use the 7+-2 heuristics

or better 5+-2!
47
Focus on
control flow
SequenceDiagrams
Passenger
TicketMachine
Torefineusecasedescriptions
tofindadditionalobjects
(participatingobjects)
selectZone()
insertCoins()
pickupChange()
Usedduringsystemdesign
TicketMachine
torefinesubsysteminterfaces
zone2price
Messages ->
Instancesarerepresentedby
selectZone()
Operations on
rectangles.Actorsbystickyfigures
insertCoins()
participating Object
Lifelinesarerepresentedbydashed
pickupChange()
lines
pickUpTicket()
pickUpTicket()
Usedduringanalysis
Messagesarerepresentedbyarrows
Activationsarerepresentedbynarrow
rectangles.
48
SequenceDiagramscanalsomodeltheFlowofData
Passenger
ZoneButton
selectZone()
TarifSchedule
Display
lookupPrice(selection)
price
Dataflow
displayPrice(price)
continued on next slide...
Thesourceofanarrowindicatestheactivationwhichsentthemessage
Horizontaldashedarrowsindicatedataflow,forexamplereturnresults
fromamessage
49
SequenceDiagrams:Iteration&Condition
continued from previous slide...
Passenger
ChangeProcessor
*insertChange(coin)
Iteration
Condition
CoinIdentifier
Display
CoinDrop
lookupCoin(coin)
price
displayPrice(owedAmount)
[owedAmount<0]returnChange(owedAmount)
continued on next slide...
Iterationisdenotedbya*precedingthemessagename
Conditionisdenotedbybooleanexpressionin[]beforethemessage
name
50
Creationanddestruction
continued from previous slide...
Passenger
Creation of Ticket
ChangeProcessor
createTicket(selection)
Ticket
print()
free()
Destruction of Ticket
Creationisdenotedbyamessagearrowpointingtotheobject
DestructionisdenotedbyanXmarkattheendofthedestructionactivation
Ingarbagecollectionenvironments,destructioncanbeusedtodenotetheend
oftheusefullifeofanobject.
51
SequenceDiagramProperties
UMLsequencediagramrepresentbehaviorintermsof
interactions
Usefultoidentifyorfindmissingobjects
Timeconsumingtobuild,butworththeinvestment
Complementtheclassdiagrams(whichrepresentstructure).
52
ActivityDiagrams
Anactivitydiagramisaspecialcaseofastatechartdiagram
Thestatesareactivities(functions)
Anactivitydiagramisusefultodepicttheworkflowina
system
Handle
Incident
Document
Incident
Archive
Incident
53
ActivityDiagramsallowtomodelDecisions
Decision
[lowPriority]
Open
Incident
Allocate
Resources
[fire&highPriority]
[notfire&highPriority]
Notify
FireChief
Notify
PoliceChief
54
ActivityDiagramscanmodelConcurrency
Synchronizationofmultipleactivities
Splittingtheflowofcontrolintomultiplethreads
Splitting
Open
Incident
Allocate
Resources
Coordinate
Resources
Synchronization
Archive
Incident
Document
Incident
55
ActivityDiagrams:GroupingofActivities
Activitiesmaybegroupedintoswimlanestodenotetheobject
orsubsystemthatimplementstheactivities.
Allocate
Resources
Open
Incident
Coordinate
Resources
Dispatcher
Archive
Incident
FieldOfficer
Document
Incident
56
ActivityDiagramvs.StatechartDiagram
Statechart Diagram for Incident
Focus on the set of attributes of a single abstraction (object, system)
Event causes
state transition
Active
Inactive
Incident
Handled
Closed
Incident
Documented
Archived
Incident
Archived
Activity Diagram for Incident

(Focus on dataflow in a system)
Handle
Incident
Document
Incident
Completion of activity
causes state transition
Archive
Incident
Triggerless
transition
57
UMLSummary
UMLprovidesawidevarietyofnotationsforrepresenting
manyaspectsofsoftwaredevelopment
Powerful,butcomplex
UMLisaprogramminglanguage
Canbemisusedtogenerateunreadablemodels
Canbemisunderstoodwhenusingtoomanyexoticfeatures
Weconcentratedonafewnotations:
Functionalmodel:Usecasediagram
Objectmodel:classdiagram
Dynamicmodel:sequencediagrams,statechartandactivity
diagrams
58
AdditionalReferences
MartinFowler
UMLDistilled:ABriefGuidetotheStandardObjectModeling
Language,3rded.,AddisonWesley,2003
Grady Booch,James Rumbaugh,Ivar Jacobson

TheUnifiedModelingLanguageUserGuide,AddisonWesley,2 nd
edition,2005
CommercialUMLtools
RationalRoseXDEforJava
http://www306.ibm.com/software/awdtools/developer/java/
Together(Eclipse,MSVisualStudio,JBuilder)
http://www.borland.com/us/products/together/index.html
OpenSourceUMLtools
http://javasource.net/opensource/umlmodeling
ArgoUML,UMLet,Violet,
59

Ch02lect1 UD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ch02lect1 UD

Uploaded by

Copyright:

Available Formats

UsingUML,Patterns,andJava

System Model (Concepts)(Analysis)

System Model (Concepts)(Design)

Names of Classes are not underlined

Names of Instances are underlined

An edge between two nodes denotes a

Use case diagrams represent the functionality of the system

Class diagrams represent the structure of the system

Sequence diagrams represent the behavior of a system

A use case represents a class of

Use case model:

Each attribute has a type

A solid diamond denotes composition: A strong form of

Class Identification: Name of Class, Attributes and Methods

Is Foo the right name?

1) Find New Classes

1) Find New Classes

Use the 7+-2 heuristics

continued on next slide...

continued on next slide...

Activity Diagram for Incident

Grady Booch,James Rumbaugh,Ivar Jacobson

You might also like