Transcript Lecture for Chapter 2, Modeling with UML - ICAR-CNR

Using UML, Patterns, and Java
Object-Oriented Software Engineering
Chapter 2,
Modeling with UML
Overview: modeling with UML






What is modeling?
What is UML?
Use case diagrams
Class diagrams
Sequence diagrams
Activity diagrams
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
2
What is modeling?


Modeling consists of building an abstraction of reality.
Abstractions are simplifications because:
 They ignore irrelevant details and
 They only represent the relevant details.

What is relevant or irrelevant depends on the purpose of the
model.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
3
Example: street map
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
4
Why model software?
Why model software?

Software is getting increasingly more complex
 Windows XP > 40 millions of lines of code
 A single programmer cannot manage this amount of code in its
entirety.


Code is not easily understandable by developers who did not
write it
We need simpler representations for complex systems
 Modeling is a mean for dealing with complexity
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
5
Systems, Models and Views




A model is an abstraction describing a subset of a system
A view depicts selected aspects of a model
A notation is a set of graphical or textual rules for depicting views
Views and models of a single system may overlap each other
Examples:
 System: Aircraft
 Models: Flight simulator, scale model
 Views: All blueprints, electrical wiring, fuel system
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
6
Systems, Models and Views
Flightsimulator
Blueprints
Aircraft
System
Model 2
View 2
View 1
View 3
Model 1
Scale Model
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
Electrical
Wiring
7
Models, Views and Systems (UML)
*
System
*
Model
Described by
View
Depicted by
Airplane: System
Scale Model: Model
Blueprints: View
Bernd Bruegge & Allen H. Dutoit
Flight Simulator: Model
Fuel System: View
Electrical Wiring: View
Object-Oriented Software Engineering: Using UML, Patterns, and Java
8
Application and Solution Domain

Application Domain (Requirements Analysis):
 The environment in which the system is operating

Solution Domain (System Design, Object Design):
 The available technologies to build the system
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
13
Object-oriented modeling
Application Domain
Application Domain Model
UML Package
TrafficControl
Aircraft
SummaryDisplay
TrafficController
FlightPlan
Bernd Bruegge & Allen H. Dutoit
Solution Domain
System Model
Airport
MapDisplay
FlightPlanDatabase
TrafficControl
Object-Oriented Software Engineering: Using UML, Patterns, and Java
14
What is UML?

UML (Unified Modeling Language)
 An emerging standard for modeling object-oriented software.
 Resulted from the convergence of notations from three leading
object-oriented methods:





OMT (James Rumbaugh)
OOSE (Ivar Jacobson)
Booch (Grady Booch)
Reference: “The Unified Modeling Language User Guide”,
Addison Wesley, 1999.
Supported by several CASE tools




Rational ROSE
Eclipse/UML (by Omondo)
Gentleware Poseidon
TogetherJ
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
15
UML


You can model 80% of most problems by using about 20 %
UML
We teach you those 20%
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
16
UML First Pass

Use case Diagrams
 Describe the functional behavior of the system as seen by the user.

Class diagrams
 Describe the static structure of the system: Objects, Attributes,
Associations

Sequence diagrams
 Describe the dynamic behavior between actors and the system and
between objects of the system

Statechart diagrams
 Describe the dynamic behavior of an individual object (essentially a
finite state automaton)

Activity Diagrams
 Model the dynamic behavior of a system, in particular the workflow
(essentially a flowchart)
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
17
UML Core Conventions



Rectangles are classes, instances (objects) or states
Ovals are functions or use cases
Instances are denoted with an underlined names
 myWatch:SimpleWatch
 Joe:Firefighter

Types are denoted with non underlined names
 SimpleWatch
 Firefighter

Diagrams are graphs
 Nodes are entities
 Arcs are relationships between entities
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
18
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
Use Case diagrams
UML first pass: Use case diagrams
Use case
Package
Watch
Actor
ReadTime
WatchUser
SetTime
ChangeBattery
WatchRepairPerson
(behavior)
Use case diagrams represent the functionality of the system
from user’s point of view
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
20
Use Case Diagrams

Used during requirements
elicitation to represent external
behavior
Actors represent roles, that is, a
type of user of the system
Passenger
 Use cases represent a sequence of
interaction for a type of
functionality
 The use case model is the set of
all use cases. It is a complete
description of the functionality of
PurchaseTicket the system and its environment

Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
21
Actors

An actor models an external entity which
communicates with the system:
 User
 External system
 Physical environment
Passenger


An actor has a unique name and an optional
description.
Examples:
 Passenger: A person in the train
 GPS satellite: Provides the system with GPS
coordinates
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
22
Use Case
A use case represents a class of
functionality provided by the system as
an event flow.
A use case consists of:
PurchaseTicket  Unique name
 Participating actors
 Entry conditions
 Flow of events
 Exit conditions
 Special requirements
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
23
Use Case Diagram: Example
Name: Purchase ticket
Participating actor: Passenger
Entry condition:
 Passenger standing in front of
ticket distributor.
 Passenger has sufficient money
to purchase ticket.
Exit condition:
 Passenger has ticket.
Event flow:
1. Passenger selects the number of
zones to be traveled.
2. Distributor displays the amount
due.
3. Passenger inserts money, of at
least the amount due.
4. Distributor returns change.
5. Distributor issues ticket.
Anything missing?
Exceptional cases!
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
24
The <<extends>> Relationship


Passenger

PurchaseTicket

<<extends>>
<<extends>> relationships
represent exceptional or seldom
invoked cases.
The exceptional event flows are
factored out of the main event flow
for clarity.
Use cases representing exceptional
flows can extend more than one
use case.
The direction of a <<extends>>
relationship is to the extended use
case
<<extends>>
<<extends>>
OutOfOrder
<<extends>>
Cancel
Bernd Bruegge & Allen H. Dutoit
TimeOut
NoChange
Object-Oriented Software Engineering: Using UML, Patterns, and Java
25
The <<includes>> Relationship

Passenger

PurchaseMultiCard

PurchaseSingleTicket
<<includes>>
<<includes>>
<<extends>>
CollectMoney
NoChange
Bernd Bruegge & Allen H. Dutoit
<<includes>> relationship
represents behavior that is factored
out of the use case.
<<includes>> behavior is
factored out for reuse, not because
it is an exception.
The direction of a <<includes>>
relationship is to the using use case
(unlike <<extends>>
relationships).
<<extends>>
Cancel
Object-Oriented Software Engineering: Using UML, Patterns, and Java
26
Other examples
<<include>>
<<extend>>
OpenIncident
OpenIncident
<<include>>
HelpDispatcher
<<extend>>
AllocateResources
Connection
Down
Allocate
Resources
Authenticate
WithPassword
Authenticate
Authenticate
WithCard
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
27
Use Case Diagrams: Summary




Use case diagrams represent external behavior
Use case diagrams are useful as an index into the use cases
Use case descriptions provide meat of model, not the use case
diagrams.
All use cases need to be described for the model to be useful.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
28
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
Class diagrams
UML first pass: Class diagrams
Class diagrams represent the structure of the system
Association
Class
Multiplicity
Watch
1
2
PushButton
state
push()
release()
Attribute
1
1
1
2
1
LCDDisplay
blinkIdx
blinkSeconds()
blinkMinutes()
blinkHours()
stopBlinking()
referesh()
Battery
load
1
Time
now
Operations
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
30
Class Diagrams
TarifSchedule
Enumeration getZones()
Price getPrice(Zone)


*
*
Trip
zone:Zone
Price: Price
Class diagrams represent the structure of the system.
Used
 during requirements analysis to model problem domain concepts
 during system design to model subsystems and interfaces
 during object design to model classes.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
31
Classes
Name
TarifSchedule
zone2price
getZones()
getPrice()
Attributes
TarifSchedule
Table zone2price
Enumeration getZones()
Price getPrice(Zone)
Signature
Operations





TarifSchedule
A class represent a concept
A class encapsulates state (attributes) and behavior (operations).
Each attribute has a type.
Each operation has a signature.
The class name is the only mandatory information.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
32
Attributes and operations visibility
Attributes visibility
 They should always be private ( information hiding)
 Other classes can access an attribute value using get and set
methods
Operation visibility
 + : public (the operation is part of the class interface)
 - : private (the operation can only be accessed by the class
itself)
 #: protected (in abstract classes, operations that can be used by
subclasses only).
 This visibility constraint, in abstract classes, can also be used for
attributes
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
33
Instances
tarif_1974:TarifSchedule
zone2price = {
{‘1’, .20},
{‘2’, .40},
{‘3’, .60}}



An instance represents a phenomenon.
The name of an instance is underlined and can contain the class of the
instance.
The attributes are represented with their values.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
34
Actor vs Instances


What is the difference between an actor , a class and an
instance?
Actor:
 A coherent set of roles that users of use cases play when interacting
with these use cases. An actor has one role for each use case with
which it communicates. (UML 1.5 definition)
 An entity outside the system to be modeled, interacting with the system
(“Passenger”) (book definition)

Class:
 An abstraction modeling an entity in the problem domain, must be
modeled inside the system (“User”)

Object:
 A specific instance of a class (“Joe, the passenger who is purchasing
a ticket from the ticket distributor”).
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
35
Associations


TarifSchedule
TripLeg
Enumeration getZones()
Price getPrice(Zone)
Price
Zone
*
*
Associations denote relationships between classes.
The multiplicity of an association end denotes how many objects the source
object can legitimately reference.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
36
1-to-1 and 1-to-many Associations
Has-capital
Country
City
*
name:String
name:String
One-to-one association
Point
Polygon
*
x: Integer
y: Integer
draw()
One-to-many association
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
37
Many-to-Many Associations
StockExchange
*
Lists
*
Company
tickerSymbol
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
38
From Problem Statement To Object Model
Problem Statement: A stock exchange lists many companies. Each
company is uniquely identified by a ticker symbol
Class Diagram:
StockExchange *
Bernd Bruegge & Allen H. Dutoit
*
Lists
Company
tickerSymbol
Object-Oriented Software Engineering: Using UML, Patterns, and Java
39
From Problem Statement to Code
Problem Statement : A stock exchange lists many companies.
Each company is identified by a ticker Symbol
Class Diagram:
StockExchange
*
Lists
*
Company
tickerSymbol
Java Code
public class StockExchange
{
private Vector m_Company = new Vector();
};
public class Company
{
public int m_tickerSymbol;
private Vector m_StockExchange = new Vector();
};
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
40
Aggregation


An aggregation is a special case of association denoting a “consists of”
hierarchy.
The aggregate is the parent class, the components are the children class.
Exhaust system
Exhaust system
1
0..2
0..2
1
Muffler
Tailpipe
Muffler
Tailpipe
diameter
diameter
diameter
diameter

A solid diamond denotes composition, a strong form of aggregation where
components cannot exist without the aggregate. (Bill of Material)
TicketMachine
3
ZoneButton
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
41
Inheritance (Generalization)
Button
CancelButton



ZoneButton
Generalization relationships denote inheritance between
classes.
The children classes inherit the attributes and operations of the
parent class.
Inheritance simplifies the model by eliminating redundancy.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
43
Object Modeling in Practice: Class Identification
Foo
Betrag
CustomerId
Deposit()
Withdraw()
GetBalance()
Class Identification: Name of Class, Attributes and Methods
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
44
Object Modeling in Practice:
Encourage Brainstorming
“Dada”
Foo
Betrag
Betrag
CustomerId
CustomerId
Deposit()
Withdraw()
GetBalance()
Deposit()
Withdraw()
GetBalance()
Account
Betrag
CustomerId
Naming is important!
Is Foo the right name?
Bernd Bruegge & Allen H. Dutoit
Deposit()
Withdraw()
GetBalance()
Object-Oriented Software Engineering: Using UML, Patterns, and Java
45
Object Modeling in Practice ctd
Account
Bank
Name
Betrag
AccountId
CustomerId
Deposit()
Withdraw()
GetBalance()
Customer
Name
CustomerId
1) Find New Objects
2) Iterate on Names, Attributes and Methods
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
46
Object Modeling in Practice: A Banking System
Account
Betrag
AccountId
CustomerId
AccountI
d
Deposit()
Withdraw()
GetBalance()
Bank
Name
*
Customer
Has
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
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
47
Practice Object Modeling: Iterate, Categorize!
Account
Bank
*
Name
Savings
Account
Withdraw()
Bernd Bruegge & Allen H. Dutoit
Customer
Amount
AccountId
CustomerId
AccountI
d
Deposit()
Withdraw()
GetBalance()
Checking
Account
Withdraw()
*
Has
Name
CustomerId()
Mortgage
Account
Withdraw()
Object-Oriented Software Engineering: Using UML, Patterns, and Java
48
Packages


A package is a UML mechanism for organizing elements into
groups (usually not an application domain concept)
Packages are the basic grouping construct with which you may
organize UML models to increase their readability.
DispatcherInterface
Notification

IncidentManagement
A complex system can be decomposed into subsystems, where
each subsystem is modeled as a package
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
49
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
Sequence diagrams
UML first pass: Sequence diagram
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
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
51
UML sequence diagrams

Passenger
Used during requirements analysis
 To refine use case descriptions
 to find additional objects
(“participating objects”)
TicketMachine
selectZone()

Used during system design
 to refine subsystem interfaces
insertCoins()


pickupChange()


pickUpTicket()
Bernd Bruegge & Allen H. Dutoit
Classes are represented by
columns
Messages are represented by
arrows
Activations are represented by
narrow rectangles
Lifelines are represented by
dashed lines
Object-Oriented Software Engineering: Using UML, Patterns, and Java
52
Nested messages
Passenger
ZoneButton
selectZone()
TarifSchedule
Display
lookupPrice(selection)
price
Dataflow
displayPrice(price)
…to be continued...




The source of an arrow indicates the activation which sent the message
An activation is as long as all nested activations
Horizontal dashed arrows indicate data flow
Vertical dashed lines indicate lifelines
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
53
Iteration & condition
…continued from previous slide...
Passenger
ChangeProcessor
*insertChange(coin)
Iteration
CoinIdentifier
Display
CoinDrop
lookupCoin(coin)
price
displayPrice(owedAmount)
[owedAmount<0] returnChange(-owedAmount)
Condition
…to be continued...


Iteration is denoted by a * preceding the message name
Condition is denoted by boolean expression in [ ] before the message
name
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
54
Creation and destruction
…continued from previous slide...
Passenger
ChangeProcessor
Creation
createTicket(selection)
Ticket
print()
free()



Destruction
Creation is denoted by a message arrow pointing to the object.
Destruction is denoted by an X mark at the end of the destruction activation.
In garbage collection environments, destruction can be used to denote the
end of the useful life of an object.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
55
Condizioni e iterazioni
a
b
c
[i>0] op1()
[i<=0] op2()
*op3()
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
56
Sequence Diagram Summary




UML sequence diagram represent behavior in terms of
interactions.
Useful to find missing objects.
Time consuming to build but worth the investment.
Complement the class diagrams (which represent structure).
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
57
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
State diagrams
UML First Pass: Statechart Diagrams
Initial state
Event
IncidentHandled
Active
incidentDocumented
Inactive
IncidentHandled
Closed
Archived
State
Transition
Final state
Statechart diagram for class Incident
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
59
UML First Pass: Statechart Diagrams
pressButtonsLandR
MeasureTime
SetTime
After 2 min.
After 20 years
After 20 years
pressButtonsLandR / beep
DeadBattery
Statechart of the 2BWatch set time functions
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
60
State Diagrams

A state is a condition that an object satisfies
A state can be thought of as an abstraction of the attribute
values of a class

A state diagram can be used to describe:

 The life of a class
 The life of a system/subsystem referred to as a whole
 The navigational paths among the different windows of an
application GUI
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
61
State Diagram (from UML 1.5 pag. 537)
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
62
State internal actions/activities (from UML 1.5 pag. 538)
Reserved action labels:
Internal actions syntax:
event-name ‘(’ comma-separated-parameter-list ‘)’
‘[’ guard-condition‘]’
‘/’action-expression
Example: click on button X [var_y=1]/ do_something
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
63
Composite state
Guard Condition
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
64
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
Activity diagrams
Activity Diagram: Modeling Decisions
Open
Incident
[lowPriority]
Allocate
Resources
[fire & highPriority]
[not fire & highPriority]
Notify
Fire Chief
Notify
Police Chief
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
66
Activity diagrams: concurrency
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
67
Activity Diagrams

An activity diagram shows flow control within a system
Handle
Incident


Document
Incident
Archive
Incident
An activity diagram is a special case of a state chart diagram in
which states are activities (“functions”)
Two types of states:
 Action state:


Cannot be decomposed any further
Happens “instantaneously” with respect to the level of abstraction
used in the model
 Activity state:


Can be decomposed further
The activity is modeled by another activity diagram
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
68
Activity diagrams key concepts

In an activity diagram:
 states represent the performance of actions or subactivities
 transitions are triggered by the completion of the actions or
subactivities.
 A subactivity state invokes an activity graph. When a subactivity
state is entered, the activity graph “nested” in it is executed as any
activity graph would be.

Action definition (from UML 1.5):
 The specification of an executable statement that is part of a
computational procedure.
 An action typically results in a change in the state of the system, and
can be realized by sending a message to an object or modifying a
link or a value of an attribute.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
69
Statechart Diagram vs. Activity Diagram
Statechart Diagram for Incident
(State: Attribute or Collection of Attributes of object of type Incident)
Event causes
State transition
Active
Inactive
IncidentHandled
Closed
IncidentDocumented
Archived
IncidentArchived
Activity Diagram for Incident (similar to Moore
(State: Operation or Collection of Operations)
Handle
Incident
Document
Incident
Completion of activity
causes state transition
Bernd Bruegge & Allen H. Dutoit
Archive
Incident
Triggerless
Transition
Object-Oriented Software Engineering: Using UML, Patterns, and Java
70
Activity Diagram: Modeling Decisions
Open
Incident
[lowPriority]
Allocate
Resources
[fire & highPriority]
[not fire & highPriority]
Notify
Fire Chief
Notify
Police Chief
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
71
Activity Diagrams: Modeling Concurrency


Synchronization of multiple activities
Splitting the flow of control into multiple threads
Splitting
Open
Incident
Allocate
Resources
Coordinate
Resources
Synchronization
Archive
Incident
Document
Incident
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
72
Activity Diagrams: Swimlanes

Actions may be grouped into swimlanes to denote the object or
subsystem that implements the actions.
Allocate
Resources
Open
Incident
Coordinate
Resources
Dispatcher
Archive
Incident
FieldOfficer
Document
Incident
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
73
Activity diagram
(from UML 1.5
pag.557)
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
74
Activity diagram (from UML 1.5 pag.562)
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
75
Activity diagram (from UML 1.5 pag.562)
Data flows (objects)
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
76
What should be done first? Coding or Modeling?

It all depends….

Forward Engineering:
 Creation of code from a model
 Greenfield projects

Reverse Engineering:
 Creation of a model from code
 Interface or reengineering projects

Roundtrip Engineering:
 Move constantly between forward and reverse engineering
 Useful when requirements, technology and schedule are changing
frequently
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
77
Using UML, Patterns, and Java
Object-Oriented Software Engineering
UML second pass
Component and Deployment diagrams
Other UML Notations
UML provide other notations that we will be introduced in
subsequent lectures, as needed.

Implementation diagrams
 Component diagrams
 Deployment diagrams

Object Constraint Language (OCL)
 Introduced in lecture on Object Design
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
79
Component diagrams key concepts




A component represents a modular, deployable, and replaceable
part of a system that encapsulates implementation and exposes
a set of interfaces.
A component conforms to the interfaces that it exposes, where
the interfaces represent services provided by elements that
reside on the component.
A component may be implemented by one or more artifacts,
such as binary, executable, or script files.
A component may be deployed on a node.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
80
Component diagrams
Component
Interface
Components typically expose a set of interfaces,
which represent the services provided
by the elements that reside on the component.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
81
Component and Deployment diagrams key concepts



A node is a physical object that represents a processing resource,
generally, having at least a memory and often processing capability
as well.
Nodes include computing devices but also human resources or
mechanical processing resources.
Run time computational instances, both objects and component
instances, may reside on node instances.
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
82
Deployment Diagrams
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
83
UML Core Conventions



Rectangles are classes or instances
Ovals are functions or use cases
Instances are denoted with an underlined names
 myWatch:SimpleWatch
 Joe:Firefighter

Types are denoted with nonunderlined names
 SimpleWatch
 Firefighter

Diagrams are graphs
 Nodes are entities
 Arcs are relationships between entities
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
84
UML Summary

UML provides a wide variety of notations for representing
many aspects of software development
 Powerful, but complex language
 Can be misused to generate unreadable models
 Can be misunderstood when using too many exotic features

For now we concentrate on a few notations:
 Functional model: Use case diagram
 Object model: class diagram
 Dynamic model: sequence diagrams, statechart and activity
diagrams
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
85
Additional Slides
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
86
Models for Plato’s and Aristotle’s Views of Reality
Plato




Aristotle
Material reality is a second-class
subordinate type of reality.
The first-class type is a “form”
Forms lie behind every thing or in
the world. Forms can be abstract
nouns like “beauty” or “mammal”
or concrete nouns like “tree” or
“horse”.
There is an important difference
between the world of forms and
particulars. Forms are nonmaterial,
particulars are material. Forms are
permanent and changeless.
Particulars are changing.
Forms can be acquired
intellectually through a “dialectic”
process that moves toward the
highest understanding of reality
through the interaction of questions
and answers.
Aristotle accepted the reality of Forms as
nonmaterial entities.
 However, he could not accept Plato’s idea,
that these Forms were not real.
 Instead of two separate worlds, one for
Forms and one for Particulars, Aristotle
had only one world, a world of particular
things.
 Particular things according to Aristotle
have a certain permance about them, even
while they are subject to change: A tree
changes colors without ceasing to be a
tree. A horse grows in size without ceasing
to be a horse.
 What is the root of this permancence? It is
the thing’s internal form, which minds
detect, when they penetrate beyond the
thing’s changing attributes. So for
Aristotle, reality is thus made up of
particularviewpoints
things that are
each
composed of
Using UML, we can illustrate Platon’s and Aristotle’s
very
easily
form antdn matter..

and see their differences as well
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
87
Model for Plato’s View of Reality




Plato
Material reality is a secondclass subordinate type of
reality.
Reality
The first-class type is a “form”
Forms lie behind every thing or
in the world. Forms can be
abstract nouns like “beauty” or
“mammal” or concrete nouns
like “tree” or “horse”.
There is an important difference
Thing
between the world of forms and
particulars. Forms are
nonmaterial, particulars are
material. Forms are permanent
and changeless. Particulars are
changing.
Forms can be acquired
Particular
intellectually through a
“dialectic” process that moves
toward the highest
Bernd Bruegge & Allen H. Dutoit
Object-Oriented Software Engineering: Using UML, Patterns, and Java
understanding
of reality
*
Form
88
Model Aristotle’s Views of Reality
Aristotle





Aristotle accepted the reality of
Forms as nonmaterial entities.
However, he could not accept
Plato’s idea, that these Forms were
Reality
not real.
Instead of two separate worlds, one
for Forms and one for Particulars,
Aristotle had only one world, a
world of particular things.
*
Particular things according to
Aristotle have a certain permance
Substance
about them, even while they are
subject to change: A tree changes
colors without ceasing to be a tree.
A horse grows in size without
ceasing to be a horse.
What is the root of this
Form
Matter
permancence? It is the thing’s
internal form, which minds detect,
when they penetrate beyond the
thing’s changing attributes. So for
Aristotle, reality is thus made up of
particular
that are each Object-Oriented Software Engineering: Using UML, Patterns, and Java
Bernd Bruegge & things
Allen H. Dutoit
composed of form antdn matter..
89
Comparison of Plato’s and Aristotle’s Views
Plato
Aristotle
Reality
Reality
*
*
Substance
Thing
Form
Particular
Bernd Bruegge & Allen H. Dutoit
Matter
Form
Object-Oriented Software Engineering: Using UML, Patterns, and Java
90