Fundamentals: Software Engineeringrzb/FSE -UML2.pdf · Fundamentals of Software Engineering, R....
Transcript of Fundamentals: Software Engineeringrzb/FSE -UML2.pdf · Fundamentals of Software Engineering, R....
Fundamentals of Software Engineering, R. Bahsoon
1Unit 2. Modeling Objects and
Components with UML
Fundamentals: Software Engineering
Dr. Rami BahsoonSchool of Computer Science
The University Of [email protected]/~rzb
Office 112 Y9- Computer Science
Fundamentals of Software Engineering, R. Bahsoon
2
Objectives
• To describe the activities in the object-oriented analysis and design process
• To introduce various models that can be used to describe an object-oriented analysis and design
• To show how the Unified Modelling Language (UML) may be used to represent these models
• To introduce models suitable for specifying Components-Based Software
Fundamentals of Software Engineering, R. Bahsoon
3
Roughly …
Requirements Elicitation Requirements Specification Go ahead
Analysis and Design
They could be usingUML ;-)
Fundamentals of Software Engineering, R. Bahsoon
4
You are here!
Fundamentals of Software Engineering, R. Bahsoon
5
The Unified Modelling Language
• Several different notations for describing object-oriented designs were proposed in the 1980s and 1990s.
• The Unified Modeling Language is an integration of these notations.
• It describes notations for a number of different models that may be produced during OO analysis and design.
• It is now a de facto standard for OO modelling.
Fundamentals of Software Engineering, R. Bahsoon
6
UML Contributors
• http://www.uml.org/
RumbaughOMT
JacobsonOOSE
Shlaer-Mellor
Meyer
Booch
Gamma et alFramework and pattern
Harel
And many others…….
Major three (submission to OMG Jan 97, Acceptance Nov 97…)http://www.omg.org/
Fundamentals of Software Engineering, R. Bahsoon
7
Fundamentals of Software Engineering, R. Bahsoon
8
UML Diagrams
Fundamentals of Software Engineering, R. Bahsoon
9
Models?
• The language of the designer• Representations of the system to-be-built or as-built
• A complete description of a system from a particular perspective
• Vehicles for communication with various stakeholders
• Allow reasoning about some characteristics of a system
• Often captures both structural and behavioural(e.g., interaction) information
Fundamentals of Software Engineering, R. Bahsoon
10
UML Diagrams
• Diagram: a view into the model
• In UML, there are nine standard diagrams– Static view: use case, class, object, component, deployment
– Dynamic view: sequence, collaboration, state chart, activity
Fundamentals of Software Engineering, R. Bahsoon
11
Some UML diagrams
Deployment
Use cases
Sequence
activity Class diagram
Collaboration
Fundamentals of Software Engineering, R. Bahsoon
12
UML DiagramsYou are Here!
Fundamentals of Software Engineering, R. Bahsoon
13
Use Cases
• What is use case modelling?
• What are actors?
• How to find actors?
• What are use cases?
• How to find use cases?
• How to construct a use case diagram?
• Detailing a use case…
Fundamentals of Software Engineering, R. Bahsoon
14
What is a use case modelling• Basis for a user-oriented approach to system development– Identify the users of the system (actors)
– Identify the tasks they must undertake with the system (use cases)
– Relate users & tasks (relationship)… help identify boundary
Capture system functionality as seen by users
Fundamentals of Software Engineering, R. Bahsoon
15
Use cases
Built in early stages of development– Specify the context of a system– Plan iterations of development
– Validate a system’s architecture– Drive implementation & generate test cases– Developed by analysts & domain experts during requirements analysis
Fundamentals of Software Engineering, R. Bahsoon
16
How to find actors?• Observe direct users of the system- could be users or systems– What role do they play?– Who provides information to the system?– Who receives information from the system?
• Actors could be:– Principal – Secondary (External hardware, other systems, …)
• Describe each actor clearly and precisely (semantics)– Short name– Description BookBorrower
This actor represents some one that make use of the library for borrowing books
Fundamentals of Software Engineering, R. Bahsoon
17
Exercise
• Assume you have a requirements documents for a library system: identify all actors that interact with a system
• For each actor, write down the name and provide a brief textual description (i.e., describing the semantics of the actor)
Actor Semantics
Name 1 Description
Fundamentals of Software Engineering, R. Bahsoon
18
What are use cases?
• Things actors do with the system– A task which an actor needs to perform with the help of a system (e.g., Borrow a book)
– A specific kind of a system
• Describe the behaviour of the system from a user’s standpoint
• Represented by ellipses Borrow a copy of book
Fundamentals of Software Engineering, R. Bahsoon
19
How to find use cases?
• Start with the list of actors and consider– What they need from the system (i.e. what use cases there are which have value for them)
– Any other interactions they expect to interact with the system (i.e. which use cases they might take part in for someone’s else benefit)
• How do you know what is a use case?– Estimate frequency of use, examine differences between use cases, distinguish between “basic” and “alternative” course of events & create new uses when necessary
Fundamentals of Software Engineering, R. Bahsoon
20
Describing use cases
Semantics detailed in text
Example:Borrow copy of book
A book borrower presents a book. The system checks that the potential borrower is a member of the library & she does not have the maximum number of books
Borrow a copy of book
Use case name
----------------
Text describing the use case… blabla……….
Should be described �
Fundamentals of Software Engineering, R. Bahsoon
21
Exercise
• Draft use case diagrams of a library system
Fundamentals of Software Engineering, R. Bahsoon
22
Possible use cases…
Fundamentals of Software Engineering, R. Bahsoon
23
Use case diagram of a library
Fundamentals of Software Engineering, R. Bahsoon
24
Requirements example
Multi-purpose recycling machine must:
�receive & check items for customers,�print out receipt for items received,�print total received items for operator,�change system information,�signal alarm when problems arise.
Reference: Anthony Finkelstein, UCL
Fundamentals of Software Engineering, R. Bahsoon
25
ExampleReturning items is started by Customer when she wants toreturn cans, bottles or crates. With each item that theCustomer places in the recycling machine, the system willincrease the received number of items from Customer aswell as the daily total of this particular type.
When Customer has deposited all her items, she will press areceipt button to get a receipt on which returned items havebeen printed, as well as the total return sum.
Particular instances of use would be different…Themorning after the party Sarah goes to the recycling centre
with three crates containing ....
Fundamentals of Software Engineering, R. Bahsoon
26
Use case diagram
Fundamentals of Software Engineering, R. Bahsoon
27
Extensions
• Extensions provide opportunities for :– optional parts– alternative complex cases– separate sub-cases– insertion of use cases
Fundamentals of Software Engineering, R. Bahsoon
28
Refinement - <<extend>>
Borrow copy of a book
Refuse loan
<<extend>>
Note: the direction of the arrow from the less central case to the central one!Refuse loan and borrow copy of a book two different scenarios
Fundamentals of Software Engineering, R. Bahsoon
29
Refinement - <<extend>>
Fundamentals of Software Engineering, R. Bahsoon
30
Refinement
Extend Loan
Borrow copy of a book
Check for reservation
<<include>>
Fundamentals of Software Engineering, R. Bahsoon
31
Use <<include>>
• Use <<include>>– How the system can reuse pre-existing component
– To show common functionality between use cases
– To develop the fact that project from existing components!
Note: <<include>> and <<extend>>:are UML stereotypes used to attach additional classification
Fundamentals of Software Engineering, R. Bahsoon
32
Fundamentals of Software Engineering, R. Bahsoon
33
Refinement
Fundamentals of Software Engineering, R. Bahsoon
34
Generalization
Journal borrower is a book borrower
Fundamentals of Software Engineering, R. Bahsoon
35
Detailing a use case
• Writing a specification for the use case
• Good Practice– Preconditions: the system state before the case begin (i.e., facts, things that must be true)
– Flow of events; the steps in the use case (i.e. actions…)
– Postconditions: the system state after the case has been completed
Fundamentals of Software Engineering, R. Bahsoon
36
Detailing a use case
Borrow a copy of book• Precondition
1. the BookBorrower is a member of the library2. the BookBorrower has not got more than the permitted number of books on loan
• Flow of events1. the use case starts when the BookBorrower attempts to borrow a book
2. the librarian checks it is ok to borrow a book3. If …… (indicate an alternative path of action)
• Post-conditions1. the system has updated the number of books the BookBorrower has on loan
Borrow a copy of book
Fundamentals of Software Engineering, R. Bahsoon
37
Exercise
• Select one of the use cases identified for the library system and create complete specification of each
• Use Structured English to show at least one alternative flow of events and at least one repeated action
Borrow copy of book
Preconditions
1.
Flow of events
1.
2.
Post conditions
1.
Fundamentals of Software Engineering, R. Bahsoon
38
Scenarios
• Each time an actor interacts with a system, the triggered use cases instantiate a scenario
• Each case corresponds to a specific path through a use case with no branching
• Scenarios are typically documented as text along side the use case and activity diagrams
Fundamentals of Software Engineering, R. Bahsoon
39
Write the scenarios for this diagram
Fundamentals of Software Engineering, R. Bahsoon
40
Example- borrow copy of book
• Scenario 1BookBorrower Joe B Borrows the library’s only copy of using UML, when he has no other book on loan. The system is updated accordingly.
• Scenario 2BookBorrower Ann tries to borrow the library’s second copy of Software Engineering, but is refused because she has six books out on loan, which is her maximum allowance.
Fundamentals of Software Engineering, R. Bahsoon
41
UML Diagrams
You are Here!
Covered
Fundamentals of Software Engineering, R. Bahsoon
42
Activity Diagrams
• Activity diagrams show the dependencies and coordination between activities within a system– The activity flow should not get “stuck”
– They can be used during the requirements elicitation process …
– help in identifying use cases of a system and operations involved in the realization of a use case
• Workflows and business processes
• Can be attached to any model element to model its dynamic behavior
Fundamentals of Software Engineering, R. Bahsoon
43
Activity Diagrams
Reference: David Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
44
Fundamentals of Software Engineering, R. Bahsoon
45
Swimlanes(i.e., main actors swimming on each lane)
Fundamentals of Software Engineering, R. Bahsoon
46
UML Diagrams
You are Here!Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
47
Class: Simple Example
Fundamentals of Software Engineering, R. Bahsoon
48
UML Class Icons
Reference: D. Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
49
+, #, -
• + means public: public members can be accessed by any client of the class
• # means protected: protected members can be accessed by members of the class or any subclass
• - means private: private members can only be accessed by members of the same class
Fundamentals of Software Engineering, R. Bahsoon
50
Analysis class
An analysis class abstracts one or more classes and/or
subsystems in the system’s design– Focuses on handling functional requirements
– Defines responsibilities (cohesive subsets of behaviour defined by the class)
– Defines attributes
– Expresses relationships the class is involved in
Fundamentals of Software Engineering, R. Bahsoon
51
Approach 1: Data-Driven Design
Identify all the data in the system• Divide into classes before considering responsibilities• Common approach: noun identification
– Identify candidate classes by selecting all the nounsand noun phrases in the requirements document
– Discard inappropriate candidates» Redundant or omnipotent entities» Vague entities» Events or operations» Meta-language» Entities outside system scope» Attributes
– Verbs and verb phrases highlight candidate operations!
Fundamentals of Software Engineering, R. Bahsoon
52
Approach 1: Data-Driven Design
Some heuristics of what kind of things are classes [Shlaer and Mellor; Booch]…– Tangible or “real-world” things – book, copy, course;
– Roles- library member, student, director of studies,
– Events- arrival, leaving, request;
– Interactions- meeting, intersection
Fundamentals of Software Engineering, R. Bahsoon
53
Exercise
• Perform noun-verb analysis of your requirements document;
• Underline all the noun and noun phrases,
• Create a list of candidate classes (in examining the discard criteria, you may also identify some candidate attributes)
• Identify all verb and verb phrases
• Create a list of candidate operations and assign them to classes
Fundamentals of Software Engineering, R. Bahsoon
54
Noun/Verb Analysis
Fundamentals of Software Engineering, R. Bahsoon
55
Approach 2: Responsibility-Driven Design
• Identify all the responsibilities in the system• Divide into classes before considering the classes’ data
• Common approach: CRC cards– Class, Responsibilities, Collaborations
Fundamentals of Software Engineering, R. Bahsoon
56
Example CRC Cards for a Library
Fundamentals of Software Engineering, R. Bahsoon
57
Exercise
• Perform responsibility-driven analysis for the system to identify potential classes:– Look at the requirements document and use cases
– Identify the candidate classes
• Derive your CRC (i.e., Class, Responsibility, and collaborators)
Fundamentals of Software Engineering, R. Bahsoon
58
First-Cut Class Diagram
Fundamentals of Software Engineering, R. Bahsoon
59
Relationships
• Relationships are connections between modeling elements• Improve understanding of the domain, describing how objectswork together• Act as a sanity check for good modeling• Associations are relationships between classes
Examples» Object of class A sends a message to object of class B» Object of class A creates an object of class B» Object of class A has attribute whose values are objects of class B» Object of class A receives a message with argument of class B
• Links are relationships between objects– Links can be instances of associations (as in UML 1.4)– Allow one object to invoke operations on another object
Fundamentals of Software Engineering, R. Bahsoon
60
UML Relationship Notation
Reference: D. Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
61
Links Instantiate Associations
Reference: D. Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
62
Multiplicity of an Association
Reference: D. Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
63
Generalisation and Inheritance
Fundamentals of Software Engineering, R. Bahsoon
64
Another Inheritance Example
Fundamentals of Software Engineering, R. Bahsoon
65
Part/Whole Associations
A module is part of a course
In fact,
5 or more modules are part of one or more courses
Fundamentals of Software Engineering, R. Bahsoon
66
Part/Whole Associations
Composed of 64 squares
Fundamentals of Software Engineering, R. Bahsoon
67
Association Classes
• Used to attach attributes to an association itself rather than the classes it associates
• Class association line must have the same name!
Fundamentals of Software Engineering, R. Bahsoon
68
Example: Class Model
Fundamentals of Software Engineering, R. Bahsoon
69
Another Example: Class Model
Fundamentals of Software Engineering, R. Bahsoon
70
Example: Example Class Diagram
Fundamentals of Software Engineering, R. Bahsoon
71
More Examples
Fundamentals of Software Engineering, R. Bahsoon
72
More Examples
Fundamentals of Software Engineering, R. Bahsoon
73
More Examples
Classes Corporate Customerand Personal Customer have some similarities such as name and address, but each class has some of its own attributes and operations.
The class Customer is a general form of both the Corporate Customer and Personal Customer classes.
Fundamentals of Software Engineering, R. Bahsoon
74
What Makes a ‘Good’ Analysis Class..
� Its name reflects its intent
� It is a crisp abstraction that models one specific element of the problem domain
� It has a small but defined set of responsibilities
�It has high cohesion
�It has low coupling with other classes�homework: important!
�What is cohesion?�What is coupling?
Fundamentals of Software Engineering, R. Bahsoon
75
Note…
• Noun/verb analysis and Responsibility-Driven analysis – Noun/Verb and responsibility complement each others
– Often goes hand in hand with use cases
• First-cut class diagram (also referred to Class model)
• Refine the first-cut diagram into a detailed class diagram
Fundamentals of Software Engineering, R. Bahsoon
76
Hint…
Fundamentals of Software Engineering, R. Bahsoon
77
Environment: Demo
• Examples– Rational Rose sample
– http://www.developers.net/external/249
Fundamentals of Software Engineering, R. Bahsoon
78
UML Diagrams
You are Here!Covered
Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
79
UML Object Icons
Reference: D. Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
80
Object Diagram
Fundamentals of Software Engineering, R. Bahsoon
81
Object Diagram
• Built during analysis & design– Illustrate data/object structures– Specify snapshots
• Developed by analysts, designers and implementers
Fundamentals of Software Engineering, R. Bahsoon
82
Object Diagram
Fundamentals of Software Engineering, R. Bahsoon
83
More Examples…
Fundamentals of Software Engineering, R. Bahsoon
84
UML DiagramsYou are Here!
Covered
Covered
CoveredCovered Covered
Fundamentals of Software Engineering, R. Bahsoon
85
Sequence diagrams
• Sequence diagrams demonstrate the behavior of objects in a use case by describing the objects and the messages they pass. the diagrams are read left to right and descending.
• Object interactions arranged in a time sequence (i.e. time-oriented)
objects
Activation:i.e., object in activeL
ife-time
Fundamentals of Software Engineering, R. Bahsoon
86
Sequence diagrams
objects
Activation:i.e., object in active
Life-line
destroy
message
Fundamentals of Software Engineering, R. Bahsoon
87
Sequence diagrams
• The example shows an object of class 1 start the behavior by sending a message to an object of class 2. Messages pass between the different objects until the object of
class 1 receives the final message
Fundamentals of Software Engineering, R. Bahsoon
88
Sequence diagrams
• The example shows an object of class 1 start the behavior by sending a message to an object of class 2. Messages pass between the different objects until the object of
class 1 receives the final message
Fundamentals of Software Engineering, R. Bahsoon
89
Sequence diagrams
• The example shows an object of class 1 start the behavior by sending a message to an object of class 2. Messages pass between the different objects until the object of
class 1 receives the final message
Fundamentals of Software Engineering, R. Bahsoon
90
Sequence diagrams
• The example shows an object of class 1 start the behavior by sending a message to an object of class 2. Messages pass between the different objects until the object of
class 1 receives the final message
Fundamentals of Software Engineering, R. Bahsoon
91
Example• Self-service machine, three objects do the work we're concerned with – the front: the interface the self-service machine presents to the customer
– the money register: part of the machine where moneys are collected
– the dispenser: which delivers the selected product to the customer
Fundamentals of Software Engineering, R. Bahsoon
92
Example
• The instance sequence diagram may be sketched by using this sequences:– 1.The customer inserts money in the money slot
– 2.The customer makes a selection
– 3.The money travels to the register
– 4.The register checks to see whether the selected product is in the dispenser
– 5. The register updates its cash reserve
– 6. The register has a dispenser deliver the product to the front of the machine
Fundamentals of Software Engineering, R. Bahsoon
93
Example
The "Buy a product" scenario. Because this is the best-case scenario, it's an instance sequence diagram
Notify()
Fundamentals of Software Engineering, R. Bahsoon
94
… But
• We have seen an instance of an interaction diagram- one possible sequence of messages
• Since a use case can include may scenarios– There is a need to show conditional behaviour
– There is a need to show possible iterations
• A generic interaction diagram shows all possible sequences of messages that can occur
Fundamentals of Software Engineering, R. Bahsoon
95
Showing conditional behavior • A message may be guarded by a condition • Messages are only sent if the guard evaluates to true at the time when the system reaches that point in the interaction
Obj:class Obj:class
If i=0 then foo()Else bar()
If i=0 then foo()If i= 1 then bar()
Fundamentals of Software Engineering, R. Bahsoon
96
alt: Operators in interactions frames – UML 2.0
Operator
Guard
Alternative multiple fragment: only the one whose condition is true will execute
Fundamentals of Software Engineering, R. Bahsoon
97
Iterations (i.e., loop) – UML 1.0 • * Indicates looping or iterations• i:=1..2 means 2 iterations….
Result: ab abIf you have seen it?Earlier UML versions: UML 1.0
Fundamentals of Software Engineering, R. Bahsoon
98
Loop in UML 2.0
Loop:the fragment may execute multiple times, and the guard indicates basisfor iterations
Guard
Fundamentals of Software Engineering, R. Bahsoon
99
Opt in UML 2.0
Opt:Optional; the fragment executes only if the supplied condition is true. This is equivalent to an alt with one trace
Fundamentals of Software Engineering, R. Bahsoon
100
Sequence diagram of library
Fundamentals of Software Engineering, R. Bahsoon
101
Showing timing constraints on a sequencediagram
time
Fundamentals of Software Engineering, R. Bahsoon
102
Interaction types in sequence diagrams
Some UML versions use for both
Fundamentals of Software Engineering, R. Bahsoon
103
Example
AsynchronousreturnStudent submitting a choice to the web
An e-mail sent to the system
synchronous
Fundamentals of Software Engineering, R. Bahsoon
104
Other notions: Branching
The life time of any object which could be affected by a conditional message is split into branches
Fundamentals of Software Engineering, R. Bahsoon
105
Opt in UML 2.0
Opt:Optional; the fragment executes only if the supplied condition is true. This is equivalent to an alt with one trace
Fundamentals of Software Engineering, R. Bahsoon
106
Examples
• Refer to examples and printouts on sequence diagrams for optional extra features
Fundamentals of Software Engineering, R. Bahsoon
107
Exercise
• Draft use case diagram for an ATM machine
• Use a Scenario of Interest
• Draw a simplified object diagram corresponding to the use cases
• Draft the corresponding sequence diagram
Fundamentals of Software Engineering, R. Bahsoon
108
UML Diagrams
You are Here!
Covered
Covered
CoveredCovered Covered
Fundamentals of Software Engineering, R. Bahsoon
109
Collaboration diagrams• Describe a specific scenario by showing the movement of messages between the objects
• Show a spatial organization of objects and their interactions, rather than the sequence of the interactions
Unlike a Sequence diagram, a collaboration diagram shows the relationships among the objects. A collaboration diagram does not show time (i.e., sequence)
• Keep in mind:- Both are referred to as interaction diagrams but with different focus!
• Sequence diagrams – message flows between objects based on time (i.e., sequence)
• Collaboration diagrams– message flows between objects with no timing
Fundamentals of Software Engineering, R. Bahsoon
110
ATM: Assume you have these objects
Fundamentals of Software Engineering, R. Bahsoon
111
First step to build a collaboration diagram
• Connect the objects
Fundamentals of Software Engineering, R. Bahsoon
112
Second step to build a collaboration diagram
1. Connect the objects
2. Draw the flow of messages
Fundamentals of Software Engineering, R. Bahsoon
113
A simple collaboration, showing nointeraction
Fundamentals of Software Engineering, R. Bahsoon
114
Interaction shown on a collaborationdiagram
Fundamentals of Software Engineering, R. Bahsoon
115
• Sketch a collaboration diagram for self-service machine, three objects do the work we're concerned with
– the front: the interface the self-service machine presents to the customer
– the money register: part of the machine where moneys are collected
– the dispenser: which delivers the selected product to the customer
• Compare your collaboration diagram with that of a sequence diagram
Exercise
Fundamentals of Software Engineering, R. Bahsoon
116
UML Diagrams
You are Here!
Covered
Covered
CoveredCovered Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
117
State Diagrams• Also known as statecharts (invented by David Harel)• Used primarily to model state of an object
• A class has at most one state machine diagram– Models how an object’s reaction to a message depends on its
state
» Objects of the same class may therefore receive the same message, but respond differently
Fundamentals of Software Engineering, R. Bahsoon
118
Note: use of State diagrams
• Often used for modelling the behaviour of components (subsystems) of real time and critical systems….
Fundamentals of Software Engineering, R. Bahsoon
119
Modelling states and events
Copy of aBook
The Book states could be
On shelf
On loan
maybe lost
Borrow
return
The related events could be
Fundamentals of Software Engineering, R. Bahsoon
120
Realising state diagrams
On shelf
On loan
Return()
borrow()Copy of book
Fundamentals of Software Engineering, R. Bahsoon
121
Conditional notions
Conditional notation is used if the value of an object’sattributes determines the change of state ( i.e., change the state under this condition….)
Important hint: For some guards use keywords like
After followed by expressionWhen followed by expression
Fundamentals of Software Engineering, R. Bahsoon
122
Conditional notions
When(balance<overdraft limit)
/notify manager
In credit overdrawnUpdating the account [balance<0]
[balance>=0]
Important hint: For expressing some events use keywords likeAfter followed by expressionWhen followed by expression
Means……If balance<0, then change the state to overdrawn If balance>=0, then change the state to Incredit
Fundamentals of Software Engineering, R. Bahsoon
123
Conditional notions
overdrawn
After (3months)
Important hint: For expressing some events use keywords likeAfter followed by expressionWhen followed by expression
When(balance<overdraft limit)/notify manager
frozen
Fundamentals of Software Engineering, R. Bahsoon
124
Modelling states and substates
States of ATM machine itself…
Idle busy
Serving customer
Customer served
Out of order
Fundamentals of Software Engineering, R. Bahsoon
125
Modelling substates
Idle busyServing customer
Customer served
Out of order
States of ATM machine itself… is rather trivial….Let us see how we can model the sub state busy
Fundamentals of Software Engineering, R. Bahsoon
126
Modelling substates for ATM machine
Reading card
Correct
After
Three wrong
Trials
Wrong pin
Retain card
Fundamentals of Software Engineering, R. Bahsoon
127
State diagram for ATM machine
Busy
Idle
Serving customer
Customer served
Out of order
Reading card
Correct
After
Three wrong
Trials
Wrong pin
Retain card
Fundamentals of Software Engineering, R. Bahsoon
128
Modelling concurrent states
States that occur in parallel
Fundamentals of Software Engineering, R. Bahsoon
129
Exercise
Reference: David Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
130
Exercise
Fundamentals of Software Engineering, R. Bahsoon
131
UML Diagrams
We are here
Covered
Covered
CoveredCovered Covered
Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
132
Component Diagram
• The component diagram's main purpose is to show the structural relationships between the components of a system
• Component diagrams offer architects a natural format to begin modeling a solution
• Component diagrams allow an architect to verify that a system's required functionality is being implemented by components
• Helps to reason about non-functionalties
• Developers find the component diagram useful because it provides them with a high-level, architectural view of the system that they will be building
Architecture of the System
Fundamentals of Software Engineering, R. Bahsoon
133
three-tier style Client-server style
Fundamentals of Software Engineering, R. Bahsoon
134
N-tier architecture & components
Reference: Ivica Crnkovic
Fundamentals of Software Engineering, R. Bahsoon
135
N-tier architecture & components
Reference: Ivica Crnkovic
Fundamentals of Software Engineering, R. Bahsoon
136
Component Diagramshows a relationship between two components: an Order System component that uses the Inventory System component
UML version 1.4
Fundamentals of Software Engineering, R. Bahsoon
137
Component Diagram
All they mean the same: a component Order
UML version 2.0
Fundamentals of Software Engineering, R. Bahsoon
138
Required/Provide Interface
Fundamentals of Software Engineering, R. Bahsoon
139
Component Diagram
showing a component's relationship with other components, the lollipop and socket notation must also include a dependency arrow (as used in the class diagram). On a component diagram with lollipops and sockets, note that the dependency arrow comes out of the consuming (requiring) socket and its arrow head connects with the provider's lollipop
Fundamentals of Software Engineering, R. Bahsoon
140
Components Diagrams
• Architectural connection in UML 2.0 is expressed primarily in terms of interfaces
• Interfaces are classifiers with operations but no attributes
• Components have provided and required interfaces– Component implementations are said to realize their provided
interfaces– A provided and required interface can be connected if the
operations in the latter are a subset of those in the former, and the signatures of the associated operations are ‘compatible’
• Ports provide access between external interfaces and internal structure of components
• UML components can be used to model complex architectural connectors (like a CORBA ORB)
Fundamentals of Software Engineering, R. Bahsoon
141
Component Diagrams
Ref: David Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon142
Exercise 1
Flight Booking service
Hotel Promotional Service
Car Hire Promotional Service
Sketch the components and interfaces corresponding to the given services
Fundamentals of Software Engineering, R. Bahsoon143
Exercise 1
• Assume that Bob wants to book a holiday– Bob will book his holiday, where
• He provides the following data: His origin airport, his destination, his dates of departure/return, and any other preference information (e.g., budget, luxury, etc)
– Bob is interested in promotional offers for the period of his holiday• He wants to rent a car at his destination.
• He wants to get good hotel deals during his stay.
Fundamentals of Software Engineering, R. Bahsoon144
Software Requirements
• After you book a holiday, the company shall provide the holidaymaker with promotional services, which include hotel deals and car rent promotional service at the destination and for the duration of her/his stay
Fundamentals of Software Engineering, R. Bahsoon145
Flight Booking
ProvidesRequires
Flight Booking
Flight Information
Customer Preference Information
Customer data
Fundamentals of Software Engineering, R. Bahsoon146
Promotional Hotel Booking Service..
ProvidesRequires
PromotionalHotel BookingService
List of available Hotels
Flight Information
Customer Preference Information
Fundamentals of Software Engineering, R. Bahsoon147
You can even provide more services..
ProvidesRequires
PromotionalHotel BookingService
List of available HotelsList of BudgetHotel
List of Five stars
List of B&B
List of 3 stars
Flight Information
Customer Preference Information
Fundamentals of Software Engineering, R. Bahsoon148
Car Hire Promotional Service
ProvidesRequires
Car Hire Promotional Service
List of available Car agents
Flight Information
Customer Preference Information
List of cars deals
Fundamentals of Software Engineering, R. Bahsoon149
Gluing the components
ProvidesRequires
Flight Booking
Flight InformationCustomer Preference InformationCustomer
data
ProvidesRequires
Car Hire Promotional
Service
List of available Car agentsFlight
Information
Customer Preference Information
List of cars deals
ProvidesRequires
PromotionalHotel BookingService
List of available HotelsList of Budget
Hotel
List of Five star
List of B&B
List of 3 stars
Flight Information
Customer Preference Information
Fundamentals of Software Engineering, R. Bahsoon
150
Composite Structure in Component Diagrams
A composite structure depicts the internal realisation ofcomponent functionality
Ref: David Rosenblum, UCL
Fundamentals of Software Engineering, R. Bahsoon
151
Ports
The ports and connectors specify how component interfaces aremapped to internal functionality
Note that these ‘connectors’ are rather limited, special cases of the oneswe’ve been considering in software architectures
Ref: David Rosenblum, UCL
classes
Ports
ports provide a way to model how component's provided/required interfaces relate to its internal parts
Fundamentals of Software Engineering, R. Bahsoon
152
Fundamentals of Software Engineering, R. Bahsoon
153
Ports
Connectors and ports also can be used to specify structure of component instantiations
Fundamentals of Software Engineering, R. Bahsoon
154
ExampleStereotype
Fundamentals of Software Engineering, R. Bahsoon
155
Guidelines to Componentization• Keep components cohesive. A component should implement a
single, related set of functionality.– This may be the user interface logic for a single user application,
business classes comprising a large-scale domain concept, or technical classes representing a common infrastructure concept.
• Assign user interface classes to application components.– User interface classes, those that implement screens, pages, or
reports, as well as those that implement “glue logic”.• Assign technical classes to infrastructure components.
– Technical classes, such as those that implement system-level services such as security, persistence, or middleware should be assigned to components which have the infrastructurestereotype.
Fundamentals of Software Engineering, R. Bahsoon
156
ExampleInfrastructure components
User interfaces assigned to application components
Fundamentals of Software Engineering, R. Bahsoon
157
Guidelines to Componentization• Assign hierarchies to the same component.
– 99.9% of the time it makes sense to assign all of the classes of a hierarchy, either an inheritance hierarchy or a composition hierarchy, to the same component.
• Identify business domain components.– Because you want to minimize network traffic to reduce the
response time of your application, you want to design your business domain components in such a way that most of the information flow occurs within the components and not between them.
– Business domain components = services
• Identify the “collaboration type” of business classes.– Once you have identified the distribution type of each class, you
are in a position to start identifying potential business domain components.
Fundamentals of Software Engineering, R. Bahsoon
158
ExampleInfrastructure components
Students, Facilities, Seminar, Schedule are Business Domain Components
Fundamentals of Software Engineering, R. Bahsoon
159
Guidelines to Componentization• Highly coupled classes belong in the same component.
– When two classes collaborate frequently, this is an indication they should be in the same domain business component to reduce the network traffic between the two classes.
• Minimize the size of the message flow between components.– Merge a component into its only client. If you have a domain
component that is a server to only one other domain component, you may decide to combine the two components.
• Define component contracts.– Each component will offer services to its clients, each such service is
a component contract.
Fundamentals of Software Engineering, R. Bahsoon
160
Guidelines to Componentization
Highly coupled classes belong in the same component
Ref: David Rosenblum, UCL
Highly coupled classes
Defining contacts
Fundamentals of Software Engineering, R. Bahsoon
161
UML Diagrams
We are here
Covered
Covered
CoveredCovered Covered
Covered
Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
162
Deployment Diagram
• Models the run-time configuration in a static view and visualizes the distribution of components in an application
• A component is deployed in which part of the software system architecture
• In most cases, it involves modeling the hardware configurations together with the software components that lived on
Fundamentals of Software Engineering, R. Bahsoon
163
Deployment Diagram• Deployment diagram depicts a static view of the run-time
configuration of processing nodes and the components that run on those nodes
– Node: server, client etc.• Deployment diagrams show the hardware for your system, the
software that is installed on that hardware, and the middleware used to connect the disparate machines to one another!
• Models the run-time configuration in a static view and visualizes the distribution of components in an application
• Deployment DiagramsA deployment diagram models the run-time architecture of a system. – It shows the configuration of the hardware elements (nodes) and
shows how software elements and artifacts are mapped onto those nodes.
Fundamentals of Software Engineering, R. Bahsoon
164
Node
• A Node is either a hardware or software element. It is shown as a three-dimensional box shape, as shown below.
Fundamentals of Software Engineering, R. Bahsoon
165
Node Instance
• A node instance can be shown on a diagram. – An instance can be distinguished from a node by the fact that its
name is underlined and has a colon before its base node type. An instance may or may not have a name before the colon.
– The following diagram shows a named instance of a computer
Fundamentals of Software Engineering, R. Bahsoon
166
Node Stereotypes
• A number of standard stereotypes are provided for nodes, namely «cdrom», «cd-rom», «computer», «disk array», «pc», «pc client», «pc server», «secure», «server», «storage», «unix server», «user pc». These will display an appropriate icon in the top right corner of the
node symbol
Fundamentals of Software Engineering, R. Bahsoon
167
Artifact• An artifact is a product of the software development process. That
may include process models (e.g. use case models, design models etc), source files, executables, design documents, test reports, prototypes, user manuals, etc.
• An artifact is denoted by a rectangle showing the artifact name, the «artifact» keyword and a document icon, as shown below.
Fundamentals of Software Engineering, R. Bahsoon
168
Association
• In deployment diagram, an association represents a communication path between nodes. The following diagram shows a deployment diagram for a network, depicting network protocols as stereotypes, and multiplicities at the association
ends.
Fundamentals of Software Engineering, R. Bahsoon
169
Node as container
A node can contain other elements, such as components or artifacts. The following diagram shows a deployment diagram for part of an embedded system, depicting an executable artifact as being contained
by the motherboard node.
Fundamentals of Software Engineering, R. Bahsoon
170
Example of three-tiers architectures
Many of real life web applications have three tier architectures
Fundamentals of Software Engineering, R. Bahsoon
171
Deployment diagrams for three tiers
UML 1.4
Components deployed in an architecture
Fundamentals of Software Engineering, R. Bahsoon
172
Example: Client server architectures
Fundamentals of Software Engineering, R. Bahsoon
173
Example: Deployment diagram for a client server architecture
UML 2.0
Fundamentals of Software Engineering, R. Bahsoon
174
UML – End or the beginning?
Covered
Covered
CoveredCovered Covered
Covered
Covered
Fundamentals of Software Engineering, R. Bahsoon
175
References to tools
• http://www.sparxsystems.com.au/resources/links.html