using uml, patterns, and java object-oriented software engineering chapter 2, uml ile modelleme,...
TRANSCRIPT
Usi
ng U
ML
, Pat
tern
s, a
nd J
ava
Ob
ject
-Ori
ente
d S
oftw
are
En
gin
eeri
ng Chapter 2,
UML ile Modelleme, Bölüm 2
UML nedir ? Unified Modeling Language
• Nesne-Tabanlı methodların ifadesinde kullanılan birçok notasyonun biraraya gelmiş hali
• OMT (James Rumbaugh and collegues), OOSE (Ivar Jacobson), Booch (Grady Booch)
• Rational Unified Process’i de geliştirdiler, 1999’da Unified Process oldu
25 year at GE Research, where he developed OMT, joined (IBM) Rational in 1994, CASE tool OMTool
At Ericsson until 1994, developed use cases and the CASE tool Objectory, at IBM Rational since 1995, http://www.ivarjacobson.com
Developed the Booch method (“clouds”), ACM Fellow 1995, and IBM Fellow 2003http://www.booch.com/
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3
UML
• Nonproprietary standard for modeling systems• Current Version: UML 2.2
• Information at the OMG portal http://www.uml.org/
• Commercial tools:• Rational (IBM),Together (Borland), Visual Architect (Visual
Paradigm), Enterprise Architect (Sparx Systems)
• Open Source tools http://www.sourceforge.net/• ArgoUML, StarUML, Umbrello (for KDE), PoseidonUML
• Example of research tools: Unicase, Sysiphus• Based on a unified project model for modeling,
collaboration and project organization• http://unicase.org• http://sysiphus.in.tum.de/
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4
UML: İlk Bakış
• Senaryo diyagramları(Use case)• Sistemin fonksiyonel davranışını kullanıcının gördüğü
gibi tarif eder
• Sınıf Diyagramları (Class diagrams)• Sistemin statik yapısını tarif eder: Objeler, attributes,
bağlantılar
• Sıralı Diyagramlar (Sequence diagrams)• Sistemin objeler arasındaki dinamik davranışını tarif
eder
• Durum Diyagramları (Statechart diagrams)• Tek bir objenin dinamik davranışını tarif eder
• Aktivite Diyagramları (Activity diagrams)• Sistemin dinamik davranışını tarif eder, özelde iş
akışını tarif eder.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5
UML Use Case Diyagramları
Aktör sistemde bir kullanıcı tipini temsil eden rolu temsil eder.
Passenger
PurchaseTicket
Gereksinim belirlemede ve analiz aşamasında sistemin dışarıdan görünen davranışlarını göstermek için kullanılır.
Use case modeli:Sistemin tüm fonksiyonalitesini tarif eden use case’lerin oluşturduğu model.
Use case sistemin sağladığı bir fonksiyonalite sınıfını temsil eder.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6
Aktörler
• An actor is a model for an external entity which interacts (communicates) with the system:
• User• External system (Another system)• Physical environment (e.g. Weather)
• An actor has a unique name and an optional description
• Examples:• Passenger: A person in the train• GPS satellite: An external system that
provides the system with GPS coordinates.
Passenger
Name
Optional Description
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7
Use Case• Use case sistemin sağladığı bir
fonksiyonalite sınıfını temsil eder.
• Use case bir sistem ile aktör arasındaki olay akışını text formatında ifade eder.
• Use case yazımında altı kısım vardır:1. İsim2. Aktörler (Participating actors)3. Giriş koşulları (Entry conditions)4. Çıkış koşulları (Exit conditions)5. Olay akışı (Flow of events)6. Özel Gereksinimler (Special
requirements.)
PurchaseTicket
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 8
Text Formatında Use Case Tarifi
1. İsim: Bilet Satınal
2. Aktör: Yolcu
3. Giriş Koşulu: • Yolcu bilet satış makinasının
önünde durur
• Yolcunun bilet satın alacak yeterli parası vardır
4. Çıkış Koşulu:• Yolcu bileti satın alır
5. Olay Akışı:1. Yolcu gezilecek bölgeleri
seçer
2. Bilet satş makinası toplam üçreti gösterir
3. Yolcu yeterli miktarda parayı makinaya verir
4. Bilet satış makinası para üstü verir
5. Bilet satış makinası bileti oluşturur
6. Özel Gereksinimler: Yok.
PassengerPurchaseTicket
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 9
Uses Cases can be related
• Extends Relationship• To represent seldom invoked use cases or exceptional
functionality
• Includes Relationship• To represent functional behavior common to more than
one use case.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 10
The <<extends>> Relationship• <<extends>> relationships
model exceptional or seldom invoked cases
• The exceptional event flows are factored out of the main event flow for clarity
• The direction of an <<extends>> relationship is to the extended use case
• Use cases representing exceptional flows can extend more than one use case.
Passenger
PurchaseTicket
TimeOut
<<extends>>
NoChange
<<extends>>OutOfOrder
<<extends>>
Cancel
<<extends>>
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11
The <<includes>> Relationship
• <<includes>> relationship represents common functionality needed in more than one 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 the direction of the <<extends>> relationship).
Passenger
PurchaseSingleTicket
PurchaseMultiCard
<<includes>>
CollectMoney
<<includes>>
NoChange
<<extends>>
Cancel
<<extends>>
Cancel
<<extends>>
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12
Use Case Models can be packaged
Actor.
Use Case
System boundary
Classifier
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 13
Historical Remark: UML 1 used packages
Instructor
Package Course
GiveLecture
HoldExercise
DoHomework
Student
Teaching Assistent
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 14
Class Diagrams
• Class diagrams represent the structure of the system
• Used• during requirements analysis to model application
domain concepts• during system design to model subsystems• during object design to specify the detailed behavior
and attributes of classes.
Table zone2priceEnumeration getZones()Price getPrice(Zone)
TarifSchedule
* *
Tripzone:Zone
Price: Price
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 15
Classes
• A class represents a concept• A class encapsulates state (attributes) and behavior (operations)
Table zone2priceEnumeration getZones()Price getPrice(Zone)
TarifSchedule
zone2pricegetZones()getPrice()
TarifSchedule
Name
Attributes
Operations
Signature
TarifSchedule
The class name is the only mandatory information
Each attribute has a typeEach operation has a signature
Type
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 16
Actor vs Class vs Object
• Actor • An entity outside the system to be modeled,
interacting with the system (“Passenger”)
• Class• An abstraction modeling an entity in the application or
solution domain• The class is part of the system model (“User”, “Ticket
distributor”, “Server”)
• 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 17
Instances
• An instance represents a phenomenon• The attributes are represented with their values• The name of an instance is underlined • The name can contain only the class name of the instance (anonymous instance)
zone2price = {{‘1’, 0.20},{‘2’, 0.40},{‘3’, 0.60}}
tarif2006:TarifSchedulezone2price = {{‘1’, 0.20},{‘2’, 0.40},{‘3’, 0.60}}
:TarifSchedule
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 18
Associations
Associations denote relationships between classes
PriceZone
Enumeration getZones()Price getPrice(Zone)
TarifSchedule TripLeg
* *
The multiplicity of an association end denotes how many objects the instance of a class can legitimately reference.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 19
1-to-1 and 1-to-many Associations
1-to-1 association
1-to-many association
Polygon
draw()
Point
x: Integer
y: Integer
*
Country
name:String
City
name:String
11
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 20
Many-to-many Associations
StockExchange Company
tickerSymbolLists **
• A stock exchange lists many companies.• Each company is identified by a ticker symbol
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 21
From Problem Statement To Object Model
Class Diagram:
StockExchange Company
tickerSymbolLists
**
Problem Statement: A stock exchange lists many companies. Each company is uniquely identified by a ticker symbol
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 22
From Problem Statement to Code
Problem Statement : A stock exchange lists many companies. Each company is identified by a ticker symbol
Class Diagram:
private Vector m_Company = new Vector();
public int m_tickerSymbol; private Vector m_StockExchange = new Vector();
public class StockExchange{
};
public class Company{
};
Java Code
StockExchange Company
tickerSymbolLists **
Associationsare mapped to
Attributes!
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 23
Qualifiers
• Qualifiers can be used to reduce the multiplicity of an association
DirectoryFile
filename
Without qualification
1 *
With qualification
0..1Directory File
1filename
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 24
Qualification: Another Example
*StockExchangeCompanyLists *tickerSymbol
1
StockExchange
Company
tickerSymbolLists **
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 25
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 classes
Exhaust system
Muffler
diameter
Tailpipe
diameter
1 0..2
TicketMachine
ZoneButton3
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 don’t exist on their won (“the whole controls/destroys the parts”)
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 26
Inheritance
• Inheritance is another special case of an association denoting a “kind-of” hierarchy
• Inheritance simplifies the analysis model by introducing a taxonomy
• The children classes inherit the attributes and operations of the parent class.
Button
ZoneButtonCancelButton
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 27
Packages
• Packages help you to organize UML models to increase their readability
• We can use the UML package mechanism to organize classes into subsystems
• Any complex system can be decomposed into subsystems, where each subsystem is modeled as a package.
Account
CustomerBank
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 28
Object Modeling in Practice
Class Identification: Name of Class, Attributes and Methods
Is Foo the right name?
Foo
Amount
CustomerId
Deposit()Withdraw()GetBalance()
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 29
Object Modeling in Practice: Brainstorming
Foo
Amount
CustomerId
Deposit()Withdraw()GetBalance()
Account
Amount
CustomerId
Deposit()Withdraw()GetBalance()Is Foo the right name?
“Dada”
Amount
CustomerId
Deposit()Withdraw()GetBalance()
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 30
Object Modeling in Practice: More classes
Account
Amount
Deposit()Withdraw()GetBalance()
Customer
NameCustomerId
CustomerIdAccountIdBank
Name
1) Find New Classes
2) Review Names, Attributes and Methods
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 31
Object Modeling in Practice: Associations
Account
Amount
Deposit()Withdraw()GetBalance()
Customer
NameCustomerId
CustomerIdAccountId
AccountIdBank
Name
1) Find New Classes
2) Review Names, Attributes and Methods
3) Find Associations between Classes
owns
4) Label the generic assocations
6) Review associations
*2
*?has
5) Determine the multiplicity of the assocations
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 32
Practice Object Modeling: Find Taxonomies
SavingsAccount
Withdraw()
CheckingAccount
Withdraw()
MortgageAccount
Withdraw()
Account
Amount
Deposit()Withdraw()GetBalance()
CustomerIdAccountId
AccountId
Customer
Name
CustomerId()
Has*Bank
Name*
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 33
Practice Object Modeling: Simplify, Organize
SavingsAccount
Withdraw()
CheckingAccount
Withdraw()
MortgageAccount
Withdraw()
Account
Amount
Deposit()Withdraw()GetBalance()
CustomerIdAccountId
AccountIdShow Taxonomies
separately
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 34
Practice Object Modeling: Simplify, Organize
Customer
Name
CustomerId()
Account
Amount
Deposit()Withdraw()GetBalance()
CustomerIdAccountId
AccountId
Bank
Name Has**
Use the 7+-2 heuristics
or better 5+-2!
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 35
Sequence Diagrams
• Used during analysis• To refine use case descriptions• to find additional objects
(“participating objects”)
• Used during system design • to refine subsystem interfaces
• Instances are represented by rectangles. Actors by sticky figures
• Lifelines are represented by dashed lines
• Messages are represented by arrows
• Activations are represented by narrow rectangles.
selectZone()
pickupChange()
pickUpTicket()
insertCoins()
TicketMachinePassenger
Focus on Controlflow
Messages ->Operations on
participating Object
zone2priceselectZone()insertCoins()pickupChange()pickUpTicket()
TicketMachine
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 36
Sequence Diagrams can also model the Flow of Data
• The source of an arrow indicates the activation which sent the message
• Horizontal dashed arrows indicate data flow, for example return results from a message
Passenger
selectZone()
ZoneButton TarifSchedule Display
lookupPrice(selection)
displayPrice(price)
price
Dataflow
…continued on next slide...
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 37
Sequence Diagrams: Iteration & Condition
• Iteration is denoted by a * preceding the message name• Condition is denoted by boolean expression in [ ] before
the message name
Passenger ChangeProcessor
insertChange(coin)
CoinIdentifier Display CoinDrop
displayPrice(owedAmount)
lookupCoin(coin)
price
[owedAmount<0] returnChange(-owedAmount)
Iteration
Condition
…continued on next slide...
…continued from previous slide...
*
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 38
Creation and 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.
Passenger ChangeProcessor
…continued from previous slide...
Ticket
createTicket(selection)
free()
Creation of Ticket
Destruction of Ticket
print()
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 39
Sequence Diagram Properties
• UML sequence diagram represent behavior in terms of interactions
• Useful to identify or 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 40
UML Activity Diagrams
An activity diagram consists of nodes and edges• Nodes describe activities and objects
• Control nodes• Executable nodes
• Most prominent: Action• Object nodes
• E.g. a document
• Edge is a directed connection between nodes• There are two types of edges
• Control flow edges• Object flow edges
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 41
Activity Diagrams: Grouping of Activities
• Activities may be grouped into swimlanes to denote the object or subsystem that implements the activities.
OpenIncident
AllocateResources
CoordinateResources
DocumentIncident
ArchiveIncident
Dispatcher
FieldOfficer
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 42
State Chart Diagrams vs Activity Diagrams• An activity diagram that contains only activities
can be seen as a special case of a state chart diagram
• Such an activity diagram is useful to describe the overall workflow of a system
HandleIncident
DocumentIncident
ArchiveIncident
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 43
Statechart Diagram vs Activity Diagram
HandleIncident
DocumentIncident
ArchiveIncident
Active Inactive Closed ArchivedIncident-Handled
Incident-Documented
Incident-Archived
Statechart Diagram for IncidentFocus on the set of attributes of a single abstraction (object, system)
Activity Diagram for Incident
(Focus on dataflow in a system)
TriggerlesstransitionCompletion of activity
causes state transition
Event causesstate transition
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 44
UML Summary
• UML provides a wide variety of notations for representing many aspects of software development
• Powerful, but complex
• UML is a programming language• Can be misused to generate unreadable models• Can be misunderstood when using too many exotic
features
• We concentrated on a few notations:• Functional model: Use case diagram• Object model: class diagram• Dynamic model: sequence diagrams, statechart and
activity diagrams.