CH 02 Lect 1

UsingUML,Patterns,andJava
ObjectOrientedSoftwareEngineering
Chapter2,
ModelingwithUML
Overview:modelingwithUML
Whatismodeling?
WhatisUML?
Usecasediagrams
Classdiagrams
Nextlecture
Sequencediagrams
Activitydiagrams
BerndBruegge&AllenH.Dutoit
ObjectOrientedSoftwareEngineering:UsingUML,Patterns,andJava
Whatismodeling?
Modelingconsistsofbuildinganabstractionofreality.
Abstractionsaresimplificationsbecause:
Theyignoreirrelevantdetailsand
Theyonlyrepresenttherelevantdetails.
Whatisrelevantorirrelevantdependsonthepurposeofthe
model.
Example:streetmap
Whymodelsoftware?
Whymodelsoftware?
Softwareisgettingincreasinglymorecomplex
WindowsXP>40miolinesofcode
Asingleprogrammercannotmanagethisamountofcodeinits
entirety.
Codeisnoteasilyunderstandablebydeveloperswhodidnot
writeit
Weneedsimplerrepresentationsforcomplexsystems
Modelingisameanfordealingwithcomplexity
Systems,ModelsandViews
Amodelisanabstractiondescribingasubsetofasystem
Aviewdepictsselectedaspectsofamodel
Anotationisasetofgraphicalortextualrulesfordepictingviews
Viewsandmodelsofasinglesystemmayoverlapeachother
Examples:
System:Aircraft
Models:Flightsimulator,scalemodel
Views:Allblueprints,electricalwiring,fuelsystem
Systems,ModelsandViews
Blueprints
Flightsimulator
Aircraft
Model2
System
View2
View1
View3
Model1
Scale Model
Electrical
Wiring
Models,ViewsandSystems(UML)
System
Model
Describedby
View
Depictedby
Airplane:System
ScaleModel:Model
Blueprints:View
FlightSimulator:Model
FuelSystem:View
ElectricalWiring:View
ConceptsandPhenomena
Phenomenon
Anobjectintheworldofadomainasyouperceiveit
Example:Thelectureyouareattending
Example:Myblackwatch
Concept
Describesthepropertiesofphenomenathatarecommon.
Example:Lecturesonsoftwareengineering
Example:Blackwatches
Conceptisa3tuple:
Name(Todistinguishitfromotherconcepts)
Purpose(Propertiesthatdetermineifaphenomenonisamember
ofaconcept)
Members(Thesetofphenomenawhicharepartoftheconcept)
Conceptsandphenomena
Name
Clock
Purpose
Members
Adevicethat
measurestime.
Abstraction
Classificationofphenomenaintoconcepts
Modeling
Developmentofabstractionstoanswerspecificquestionsaboutasetof
phenomenawhileignoringirrelevantdetails.
10
Conceptsinsoftware:TypeandInstance
Type:
Anabstractioninthecontextofprogramminglanguages
Name:int,Purpose:integralnumber,Members:0,1,1,2,
2,...
Instance:
Memberofaspecifictype
Thetypeofavariablerepresentsallpossibleinstancesthe
variablecantake
Thefollowingrelationshipsaresimilar:
type<>instance
concept<>phenomenon
11
AbstractDataTypes&Classes
Abstractdatatype
Specialtypewhoseimplementationishidden
fromtherestofthesystem.
Class:
Anabstractioninthecontextofobject
orientedlanguages
Likeanabstractdatatype,aclass
encapsulatesbothstate(variables)and
behavior(methods)
ClassVector
Unlikeabstractdatatypes,classescanbe
definedintermsofotherclassesusing
inheritance
Watch
time
date
SetDate(d)
CalculatorWatch
calculatorState
EnterCalcMode()
InputNumber(n)
12
ApplicationandSolutionDomain
ApplicationDomain(RequirementsAnalysis):
Theenvironmentinwhichthesystemisoperating
SolutionDomain(SystemDesign,ObjectDesign):
Theavailabletechnologiestobuildthesystem
13
Objectorientedmodeling
Application Domain
Application Domain Model
UML Package
TrafficControl
Aircraft
SummaryDisplay
TrafficController
FlightPlan
Solution Domain
System Model
Airport
MapDisplay
FlightPlanDatabase
TrafficControl
14
WhatisUML?
UML(UnifiedModelingLanguage)
Anemergingstandardformodelingobjectorientedsoftware.
Resultedfromtheconvergenceofnotationsfromthreeleading
objectorientedmethods:
OMT(JamesRumbaugh)
OOSE(IvarJacobson)
Booch(GradyBooch)
Reference:TheUnifiedModelingLanguageUserGuide,
AddisonWesley,1999.
SupportedbyseveralCASEtools
RationalROSE
TogetherJ
15
UML:FirstPass
Youcanmodel80%ofmostproblemsbyusingabout20%
UML
Weteachyouthose20%
16
UMLFirstPass
UsecaseDiagrams
Describethefunctionalbehaviorofthesystemasseenbytheuser.
Classdiagrams
Describethestaticstructureofthesystem:Objects,Attributes,
Associations
Sequencediagrams
Describethedynamicbehaviorbetweenactorsandthesystemand
betweenobjectsofthesystem
Statechartdiagrams
Describethedynamicbehaviorofanindividualobject(essentiallya
finitestateautomaton)
ActivityDiagrams
Modelthedynamicbehaviorofasystem,inparticulartheworkflow
(essentiallyaflowchart)
17
UMLfirstpass:Usecasediagrams
Use case
Package
Watch
Actor
ReadTime
WatchUser
SetTime
WatchRepairPerson
ChangeBattery
Use case diagrams represent the functionality of the system

from users point of view
18
UMLfirstpass:Classdiagrams
Class diagrams represent the structure of the system
Association
Class
Multiplicity
Watch
1
2
PushButton
state
push()
release()
Attribute
1
2
1
LCDDisplay
blinkIdx
blinkSeconds(
)
blinkMinutes(
)
blinkHours()
stopBlinking(
)
referesh()
Battery
load
1
Time
now
Operations
19
UMLfirstpass:Sequencediagram
Actor
:WatchUser
Message
Object
:Watch
:LCDDisplay
pressButton1()
blinkHours()
pressButton1()
blinkMinutes()
pressButton2()
:Time
incrementMinutes()
refresh()
pressButtons1And2()
commitNewTime()
stopBlinking()
Activation
Lifeline
Sequence diagrams represent the behavior as interactions

20
UMLfirstpass:Statechartdiagramsforobjects
withinterestingdynamicbehavior
Event
Initial state
State
[button2Pressed]
[button1&2Pressed]
BlinkHours
Transition
IncrementHrs
[button1Pressed]
[button2Pressed]
[button1&2Pressed]
BlinkMinutes
IncrementMin.
[button1Pressed]
[button2Pressed]
[button1&2Pressed]
BlinkSeconds
IncrementSec.
Final state
StopBlinking
Represent behavior as states and transitions
21
OtherUMLNotations
UMLprovideothernotationsthatwewillbeintroducedin
subsequentlectures,asneeded.
Implementationdiagrams
Componentdiagrams
Deploymentdiagrams
IntroducedinlectureonSystemDesign
Objectconstraintlanguage
IntroducedinlectureonObjectDesign
22
UMLCoreConventions
Rectanglesareclassesorinstances
Ovalsarefunctionsorusecases
Instancesaredenotedwithanunderlinednames
myWatch:SimpleWatch
Joe:Firefighter
Typesaredenotedwithnonunderlinednames
SimpleWatch
Firefighter
Diagramsaregraphs
Nodesareentities
Arcsarerelationshipsbetweenentities
23
UseCaseDiagrams
Usedduringrequirements
elicitationtorepresentexternal
behavior
Actorsrepresentroles,thatis,a
typeofuserofthesystem
Passenger
Usecasesrepresentasequenceof
interactionforatypeof
functionality
Theusecasemodelisthesetof
allusecases.Itisacomplete
descriptionofthefunctionalityof
PurchaseTicket thesystemanditsenvironment
24
Actors
Anactormodelsanexternalentitywhich
communicateswiththesystem:
User
Externalsystem
Physicalenvironment
Passenger
Anactorhasauniquenameandanoptional
description.
Examples:
Passenger:Apersoninthetrain
GPSsatellite:ProvidesthesystemwithGPS
coordinates
25
UseCase
Ausecaserepresentsaclassof
functionalityprovidedbythesystemas
aneventflow.
Ausecaseconsistsof:
PurchaseTicket Uniquename
Participatingactors
Entryconditions
Flowofevents
Exitconditions
Specialrequirements
26
UseCaseDiagram:Example
Name:Purchaseticket
Participatingactor:Passenger
Entrycondition:
Passengerstandinginfrontof
ticketdistributor.
Passengerhassufficientmoney
topurchaseticket.
Exitcondition:
Passengerhasticket.
Eventflow:
1.Passengerselectsthenumberof
zonestobetraveled.
2.Distributordisplaystheamount
due.
3.Passengerinsertsmoney,ofat
leasttheamountdue.
4.Distributorreturnschange.
5.Distributorissuesticket.
Anything missing?
Exceptional cases!
27
The<<extends>>Relationship
Passenger
PurchaseTicket
<<extends>>
<<extends>>relationships
representexceptionalorseldom
invokedcases.
Theexceptionaleventflowsare
factoredoutofthemainevent
flowforclarity.
Usecasesrepresentingexceptional
flowscanextendmorethanone
usecase.
Thedirectionofa<<extends>>
relationshipistotheextendeduse
case
<<extends>>
<<extends>>
OutOfOrder
<<extends>>
Cancel
TimeOut
NoChange
28
The<<includes>>Relationship
Passenger
PurchaseMultiCard
PurchaseSingleTicket
<<includes>>
<<includes>>
<<extends>>
CollectMoney
NoChange
<<includes>>relationship
representsbehaviorthatisfactored
outoftheusecase.
<<includes>>behavioris
factoredoutforreuse,notbecause
itisanexception.
Thedirectionofa<<includes>>
relationshipistotheusinguse
case(unlike<<extends>>
relationships).
<<extends>>
Cancel
29
UseCaseDiagrams:Summary
Usecasediagramsrepresentexternalbehavior
Usecasediagramsareusefulasanindexintotheusecases
Usecasedescriptionsprovidemeatofmodel,nottheusecase
diagrams.
Allusecasesneedtobedescribedforthemodeltobeuseful.
30
ClassDiagrams
TarifSchedule
EnumerationgetZones()
PricegetPrice(Zone)
Trip
zone:Zone
Price:Price
Classdiagramsrepresentthestructureofthesystem.
Used
duringrequirementsanalysistomodelproblemdomainconcepts
duringsystemdesigntomodelsubsystemsandinterfaces
duringobjectdesigntomodelclasses.
31
Classes
Name
TarifSchedule
zone2price
getZones()
getPrice()
Attributes
Operations
TarifSchedule
Tablezone2price
PricegetPrice(Zone)
Signature
TarifSchedule
Aclassrepresentaconcept
Aclassencapsulatesstate(attributes)andbehavior(operations).
Eachattributehasatype.
Eachoperationhasasignature.
Theclassnameistheonlymandatoryinformation.
32
Instances
tarif_1974:TarifSchedule
zone2price={
{1,.20},
{2,.40},
{3,.60}}
Aninstancerepresentsaphenomenon.
Thenameofaninstanceisunderlinedandcancontaintheclassofthe
instance.
Theattributesarerepresentedwiththeirvalues.
33
ActorvsInstances
Whatisthedifferencebetweenanactor,aclassandan
instance?
Actor:
Anentityoutsidethesystemtobemodeled,interactingwiththe
system(Passenger)
Class:
Anabstractionmodelinganentityintheproblemdomain,mustbe
modeledinsidethesystem(User)
Object:
Aspecificinstanceofaclass(Joe,thepassengerwhoispurchasing
aticketfromtheticketdistributor).
34
Associations
TarifSchedule
TripLeg
PricegetPrice(Zone)
Price
Zone
Associationsdenoterelationshipsbetweenclasses.
Themultiplicityofanassociationenddenoteshowmanyobjectsthesource
objectcanlegitimatelyreference.
35
1to1and1tomanyAssociations
Has-capital
Country
name:String
City
name:String
Onetooneassociation
Polygon
Point
x: Integer
y: Integer
draw()
Onetomanyassociation
36
ManytoManyAssociations
StockExchange
Lists
Company
tickerSymbol
StockExchange
Lists
tickerSymbol
SX_ID
Company
37
FromProblemStatementToObjectModel
ProblemStatement:Astockexchangelistsmanycompanies.Each
companyisuniquelyidentifiedbyatickersymbol
Class Diagram:
StockExchange *
Lists
Company
tickerSymbol
38
FromProblemStatementtoCode
ProblemStatement :Astockexchangelistsmanycompanies.
EachcompanyisidentifiedbyatickerSymbol
Class Diagram:
StockExchange
Java Code
Lists
Company
tickerSymbol
publicclassStockExchange
{
privateVectorm_Company=newVector();
};
publicclassCompany
{
publicintm_tickerSymbol;
privateVectorm_StockExchange=newVector();
};
39
Aggregation
Anaggregationisaspecialcaseofassociationdenotingaconsistsof
hierarchy.
Theaggregateistheparentclass,thecomponentsarethechildrenclass.
Exhaust system
Exhaust system
0..2
1
Muffler
Tailpipe
diameter
diameter
0..2
1
Muffler
Tailpipe
diameter
diameter
Asoliddiamonddenotescomposition,astrongformofaggregationwhere
componentscannotexistwithouttheaggregate.(BillofMaterial)
TicketMachine
3
ZoneButton
40
Qualifiers
Without qualification
Directory
File
filename
With qualification
Directory
filename
01
File
Qualifierscanbeusedtoreducethemultiplicityofan
association.
41
Inheritance
Button
CancelButton
ZoneButton
Thechildrenclassesinherittheattributesandoperationsofthe
parentclass.
Inheritancesimplifiesthemodelbyeliminatingredundancy.
42
ObjectModelinginPractice:ClassIdentification
Foo
Betrag
CustomerId
Deposit()
Withdraw()
GetBalance()
Class Identification: Name of Class, Attributes and Methods
43
ObjectModelinginPractice:
EncourageBrainstorming
Foo
Dada
Betrag
Betrag
CustomerId
CustomerId
Deposit()
Withdraw()
GetBalance()
Deposit()
Withdraw()
GetBalance()
Account
Betrag
CustomerId
Naming is important!
Is Foo the right name?
Deposit()
Withdraw()
GetBalance()
44
ObjectModelinginPracticectd
Account
Betrag
Bank
Name
AccountId
CustomerId
Deposit()
Withdraw()
GetBalance()
Customer
Name
CustomerId
1) Find New Objects

2) Iterate on Names, Attributes and Methods
45
ObjectModelinginPractice:ABankingSystem
Account
Betrag
AccountId
CustomerId
AccountId
Bank
Has
Deposit()
Withdraw()
GetBalance()
Name
Customer
Name
CustomerId
1) Find New Objects

2) Iterate on Names, Attributes and Methods
3) Find Associations between Objects
4) Label the assocations
5) Determine the multiplicity of the assocations
46
PracticeObjectModeling:Iterate,Categorize!
Account
Bank
Name
Amount
AccountId
CustomerId
AccountId
Customer
Has
Deposit()
Withdraw()
GetBalance()
Savings
Account
Withdraw()
Name
CustomerId()
Checking
Account
Mortgage
Account
Withdraw()
Withdraw()
47
Packages
ApackageisaUMLmechanismfororganizingelementsinto
groups(usuallynotanapplicationdomainconcept)
Packagesarethebasicgroupingconstructwithwhichyoumay
organizeUMLmodelstoincreasetheirreadability.
DispatcherInterface
Notification
IncidentManagement
Acomplexsystemcanbedecomposedintosubsystems,where
eachsubsystemismodeledasapackage
48
UMLsequencediagrams
Passenger
Usedduringrequirementsanalysis
Torefineusecasedescriptions
tofindadditionalobjects
(participatingobjects)
TicketMachine
selectZone()
Usedduringsystemdesign
torefinesubsysteminterfaces
insertCoins()
pickupChange()
pickUpTicket()
Classesarerepresentedby
columns
Messagesarerepresentedby
arrows
Activationsarerepresentedby
narrowrectangles
Lifelinesarerepresentedby
dashedlines
49
Nestedmessages
Passenger
ZoneButton
selectZone()
TarifSchedule
Display
lookupPrice(selection)
price
Dataflow
displayPrice(price)
to be continued...
Thesourceofanarrowindicatestheactivationwhichsentthemessage
Anactivationisaslongasallnestedactivations
Horizontaldashedarrowsindicatedataflow
Verticaldashedlinesindicatelifelines
50
Iteration&condition
continued from previous slide...
Passenger
ChangeProcessor
*insertChange(coin)
Iteration
Condition
CoinIdentifier
Display
CoinDrop
lookupCoin(coin)
price
displayPrice(owedAmount)
[owedAmount<0]returnChange(owedAmount)
to be continued...
Iterationisdenotedbya*precedingthemessagename
Conditionisdenotedbybooleanexpressionin[]beforethemessage
name
51
Creationanddestruction
continued from previous slide...
Passenger
ChangeProcessor
Creation
createTicket(selection)
Ticket
print()
free()
Destruction
Creationisdenotedbyamessagearrowpointingtotheobject.
DestructionisdenotedbyanXmarkattheendofthedestructionactivation.
Ingarbagecollectionenvironments,destructioncanbeusedtodenotethe
endoftheusefullifeofanobject.
52
SequenceDiagramSummary
UMLsequencediagramrepresentbehaviorintermsof
interactions.
Usefultofindmissingobjects.
Timeconsumingtobuildbutworththeinvestment.
Complementtheclassdiagrams(whichrepresentstructure).
53
StateChartDiagrams
State
Initial state
Event
[button2Pressed]
[button1&2Pressed]
BlinkHours
Transition
IncrementHrs
[button1Pressed]
[button2Pressed]
[button1&2Pressed]
BlinkMinutes
IncrementMin.
[button1Pressed]
[button2Pressed]
[button1&2Pressed]
BlinkSeconds
IncrementSec.
Final state
StopBlinking
Represent behavior as states and transitions
54
ActivityDiagrams
Anactivitydiagramshowsflowcontrolwithinasystem
Handle
Incident
Document
Incident
Archive
Incident
Anactivitydiagramisaspecialcaseofastatechartdiagramin
whichstatesareactivities(functions)
Twotypesofstates:
Actionstate:
Cannotbedecomposedanyfurther
Happensinstantaneouslywithrespecttothelevelofabstractionused
inthemodel
Activitystate:
Canbedecomposedfurther
Theactivityismodeledbyanotheractivitydiagram
55
StatechartDiagramvs.ActivityDiagram
Statechart Diagram for Incident (similar to Mealy Automaton)
(State: Attribute or Collection of Attributes of object of type Incident)
Event causes
State transition
Active
Inactive
Incident
Handled
Closed
Incident
Documented
Archived
Incident
Archived
Activity Diagram for Incident (similar to Moore

(State: Operation or Collection of Operations)
Handle
Incident
Document
Incident
Completion of activity
causes state transition
Archive
Incident
Triggerless
Transition
56
ActivityDiagram:ModelingDecisions
[lowPriority]
Open
Incident
Allocate
Resources
[fire&highPriority]
[notfire&highPriority]
Notify
FireChief
Notify
PoliceChief
57
ActivityDiagrams:ModelingConcurrency
Synchronizationofmultipleactivities
Splittingtheflowofcontrolintomultiplethreads
Splitting
Open
Incident
Allocate
Resources
Coordinate
Resources
Synchronization
Archive
Incident
Document
Incident
58
ActivityDiagrams:Swimlanes
Actionsmaybegroupedintoswimlanestodenotetheobjector
subsystemthatimplementstheactions.
Allocate
Resources
Open
Incident
Coordinate
Resources
Dispatcher
Archive
Incident
FieldOfficer
Document
Incident
59
Whatshouldbedonefirst?CodingorModeling?
Italldepends.
ForwardEngineering:
Creationofcodefromamodel
Greenfieldprojects
ReverseEngineering:
Creationofamodelfromcode
Interfaceorreengineeringprojects
RoundtripEngineering:
Moveconstantlybetweenforwardandreverseengineering
Usefulwhenrequirements,technologyandschedulearechanging
frequently
60
UMLSummary
UMLprovidesawidevarietyofnotationsforrepresenting
manyaspectsofsoftwaredevelopment
Powerful,butcomplexlanguage
Canbemisusedtogenerateunreadablemodels
Canbemisunderstoodwhenusingtoomanyexoticfeatures
Fornowweconcentrateonafewnotations:
Functionalmodel:Usecasediagram
Objectmodel:classdiagram
Dynamicmodel:sequencediagrams,statechartandactivity
diagrams
61
AdditionalSlides
62
ModelsforPlatosandAristotlesViewsofReality
Plato
Aristotle
Materialrealityisasecondclass
subordinatetypeofreality.
Thefirstclasstypeisaform
Formsliebehindeverythingorin
theworld.Formscanbeabstract
nounslikebeautyormammal
orconcretenounsliketreeor
horse.
Thereisanimportantdifference
betweentheworldofformsand
particulars.Formsarenonmaterial,
particularsarematerial.Formsare
permanentandchangeless.
Particularsarechanging.
Formscanbeacquired
intellectuallythroughadialectic
processthatmovestowardthe
highestunderstandingofreality
throughtheinteractionofquestions
andanswers.
AristotleacceptedtherealityofFormsas
nonmaterialentities.
However,hecouldnotacceptPlatosidea,that
theseFormswerenotreal.
Insteadoftwoseparateworlds,oneforForms
andoneforParticulars,Aristotlehadonlyone
world,aworldofparticularthings.
ParticularthingsaccordingtoAristotlehavea
certainpermanceaboutthem,evenwhilethey
aresubjecttochange:Atreechangescolors
withoutceasingtobeatree.Ahorsegrowsin
sizewithoutceasingtobeahorse.
Whatistherootofthispermancence?Itisthe
thingsinternalform,whichmindsdetect,when
theypenetratebeyondthethingschanging
attributes.SoforAristotle,realityisthusmade
upofparticularthingsthatareeachcomposedof
formantdnmatter..
UsingUML,wecanillustratePlatonsandAristotlesviewpointsveryeasily
andseetheirdifferencesaswell
63
ModelforPlatosViewofReality
Plato
Materialrealityisasecondclass
subordinatetypeofreality.
Thefirstclasstypeisaform
Formsliebehindeverythingorin
theworld.Formscanbeabstract
nounslikebeautyormammal
orconcretenounsliketreeor
horse.
Thereisanimportantdifference
betweentheworldofformsand
particulars.Formsarenonmaterial,
particularsarematerial.Formsare
permanentandchangeless.
Particularsarechanging.
Formscanbeacquired
intellectuallythroughadialectic
processthatmovestowardthe
highestunderstandingofreality
throughtheinteractionof
questionsandanswers.
Reality
Thing
Particular
Form
64
ModelAristotlesViewsofReality
Aristotle
AristotleacceptedtherealityofForms
asnonmaterialentities.
However,hecouldnotacceptPlatos
idea,thattheseFormswerenotreal.
Insteadoftwoseparateworlds,onefor
FormsandoneforParticulars,
Aristotlehadonlyoneworld,aworld
ofparticularthings.
ParticularthingsaccordingtoAristotle
haveacertainpermanceaboutthem,
evenwhiletheyaresubjecttochange:
Atreechangescolorswithoutceasing
tobeatree.Ahorsegrowsinsize
withoutceasingtobeahorse.
Whatistherootofthispermancence?
Itisthethingsinternalform,which
mindsdetect,whentheypenetrate
beyondthethingschangingattributes.
SoforAristotle,realityisthusmadeup
ofparticularthingsthatareeach
composedofformantdnmatter. .
Reality
*
Substance
Form
Matter
65
ComparisonofPlatosandAristotlesViews
Aristotle
Plato
Reality
Reality
Substance
Thing
Form
Particular
Matter
Form
66

CH 02 Lect 1

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

CH 02 Lect 1

Uploaded by

Copyright:

Available Formats

UsingUML,Patterns,andJava

Use case diagrams represent the functionality of the system

Sequence diagrams represent the behavior as interactions

Represent behavior as states and transitions

Class Identification: Name of Class, Attributes and Methods

1) Find New Objects

1) Find New Objects

Represent behavior as states and transitions

Activity Diagram for Incident (similar to Moore

You might also like