CS8592 Object Oriented Analysis & Design - UNIT III

CS8592 Object Oriented Analysis and Design Unit III
III IT Prepared by Kaviya.P, AP/IT Page 1
CS8592 – Object Oriented Analysis and Design
UNIT III – Dynamic and Implementation UML Diagrams
Dynamic Diagrams – UML interaction diagrams – System sequence diagram – Collaboration diagram
– When to use Communication Diagrams – State machine diagram and Modelling –When to use State
Diagrams – Activity diagram – When to use activity diagrams. Implementation Diagrams – UML
package diagram – When to use package diagrams – Component and Deployment Diagrams – When to
use Component and Deployment diagrams
3.1 DYNAMIC DIAGRAMS
 The dynamic modeling is used to represent the behavior of the static constituents of software.
 The dynamic diagram or the dynamic model represents the time–dependent aspects of a system.
 The static constituents are class, objects, their relationships and interfaces.
 The dynamic modeling represents behavior, workflow, states and so on.
 Dynamic modeling is done using
o Use case modeling
o Interaction modeling
 Sequence diagram
 Communication diagram
o State modeling
 State chart diagram
 Activity diagram
3.2 UML INTERACTION DIAGRAMS
 To illustrate how objects interact via messages.
 It is used for dynamic object modeling.
 UML defines two types of interaction diagrams
o Sequence diagram
o Communication or collaboration diagram
3.2.1 Sequence Vs. Collaboration Diagram
Sequence Diagram Collaboration Diagram
It illustrates interacting in fence format in
which new object added to the right.
It illustrates object interaction in
graph/network format.
It clearly shows the sequence/time modeling
of messages
It is difficult to see the sequence of messages
It consumes vertical space of the diagram
It consumes both vertical and horizontal
space of the diagram
It has large set of detailed notation options It has fewer notation options

Example:
public class A
{
private B myB = new B();
public void doOne()
{
myB.doTwo();
myB.doThree();
}
}
Class A has a method named doOne and an attribute of type B. Also, that class B has methods named
doTwo and doThree.
Sequence Diagram Communication Diagrm
3.2.2 When to use Interaction Diagram? / Purpose of Interaction Diagram
 To capture the dynamic behavior of a system.
 To describe the message flow in the system.
 To describe the structural organization of the objects.
 To describe the interaction among objects.
3.2.3 How to draw an Interaction Diagram?
Following things are to be identified clearly before drawing the interaction diagram:
 Objects taking part in the interaction.
 Message flows among the objects.
 The sequence in which the messages are flowing.
 Object organization.
3.2.4 Interaction Diagram Notation
Lifeline boxes to show participants in interactions.

Basic Message Expression Syntax
The UML has a standard syntax for these message expressions:
return = message(parameter : parameterType) : returnType
Parentheses are usually excluded if there are no parameters.
Example:
initialize(code)
initialize
d = getProductDescription(id)
d = getProductDescription(id:ItemID)
d = getProductDescription(id:ItemID) : ProductDescription
Signleton Object
 There is only one instance of a class instantiated never two.
 In a UML interaction diagram (sequence or communication), such an object is marked with a '1'
in the upper right corner of the lifeline box.
Basic Sequence Diagram Notation
Name Symbol Description
Lifeline Boxesand
Lifelines,
Messages
Lifeline Box: Represents the
participants in the interaction.
Lifeline: Vertical dashed line
extending below.
Found Message: The sender
will not be specified, is not
known, or that the message is
coming from a random source.

Reply or Return
Messages
There are two ways to show
the return result from a
message:
1. Using the message syntax
returnVar =
message(parameter).
2. Using a reply (or return)
message line at the end of
an activation bar.
Messages to"self"
or "this"
Message being sent from an
object to itself by using a
nested activation bar
Creation of
Instances and
Object
Destruction
Creation of Instance: Objects
are placed at their creation
heights.
Object Destruction: If an
object is no longer usable, it is
destroyed.
Frames
 To support conditional and looping constructs (among many other things).
 Frames are regions or fragments of the diagrams
 They have an operator or label (such as loop) and a guard (conditional clause).
Frame
Operator
Meaning
Alt Alternative fragment for mutual exclusion conditional logic expressed in the guards.
Loop Loop fragment while guard is true. Can also write loop(n) to indicatelooping n times.
Opt Optional fragment that executes if guard is true.
Par Parallel fragments that execute in parallel.
Region Critical region within which only one thread can run.

Alt Frame Alternative fragment for
mutual exclusion
conditional logic expressed
in the guards.
Loop
Frame
Loop fragment while guard
is true. Can also write
loop(n) to indicate looping
n times. The specification
will be enhanced to define
a FOR loop, such as loop(i,
1, 10)
Opt
Frame
Optional fragment that
executes if guard is true.
Nesting of
frames
Frames can be nested.
Frame within a frame

Relating
Interaction
Diagrams
An interaction occurrence
(also called an interaction
use) is a reference to an
interaction within another
interaction.
It is useful, for example,
when you want to simplify
a diagram and factor out a
portion into another
diagram, or there is a
reusable interaction
occurrence.
to Invoke
Static (or
Class)
Methods
The classes Class and Type
are metaclasses, which
means their instances are
themselves classes.
A specific class, such as
class Calendar, is itself an
instance of class Class.
Thus, class Calendar is an
instance of a metaclass.
Asynchronous
&
Synchronous
Calls
An asynchronous message
call does not wait for a
response.
They are used in multi-
threaded environments
such as .NET and Java.
The UML notation for
asynchronous calls is a
stick arrow message;
regular synchronous
(blocking) calls are shown
with a filled arrow.

3.2.5 Basic Communication Diagram Notation
Links,
Messages
A link is a connection path between two objects;
it indicates some form of navigation and visibility
between the objects
Each message between objectsis represented with a
message expression, direction of the message,
message number.
Messages to
"self" or
"this"
A message can be sent from an object to itself.
This is illustrated by a link to itself, with messages
flowing along the link.
Creation of
Instances
The message may be annotated with a UML
stereotype, like «create».
The create message may include parameters,
indicating thepassing of initial values.
Message
Number
Sequencing
The first message is not numbered. Thus, msg1 is
unnumbered.
The order and nesting of subsequent messages is
shown with a legal numbering scheme in which
nested messages have a number appended to them.
Conditional
Messages
A conditional message by following a sequence
number with a conditional clause in square
brackets, similar to an iteration clause.
The message is only sent if the clause evaluates to
true.

Mutually
Exclusive
Conditional
Paths
Modify the sequence expressions with aconditional
path letter.
The first letter used is a by convention.
Either 1a or 1b could execute after msg1.
Both are sequence number 1 since either could be
the first internal message.
Iteration or
Looping
A simple * can be used.
Messages to a
Classes to
Invoke Static
(Class)
Methods
Meta class stereotype is used to
represent static method call.
Asynchronous
&
Synchronous
Calls
Asynchronous calls are shown with astick arrow.
Synchronous calls with a filled arrow.

3.2.6 Sequence Diagram Vs. Communication Diagram Example
3.3 SYSTEM SEQUENCE DIAGRAM
It is a picture that shows for one particular scenario of a use case, events that the external actors
generate, their order, and inter-system events.
3.3.1 Guidelines
 Draw an SSD for a main success scenario of each use case and frequent or complex, alternate
scenario.
 System behavior is a description of what a system does without explaining how it does.
(Black-box)
Types of Events in SSD
 External Event
 Fault Event
 Timer Event
SSD in UP Phases
Inception Elaboration
SSD are not motivated in inception, involves
only cost estimation of identifying system
operations such as LOC, FP using COCOMO-II
Model
Most SSD are created during elaboration.
Identifying major operations and detailed
system events.

3.4 UML STATE MACHINE DIAGRAM
 A UML state machine diagram illustrates the interesting events and states of an object,
and the behavior of an object in reaction to an event.
 Transitions are shown as arrows, labeled with their event.
 States are shown in rounded rectangles.
 It is common to include an initial pseudo-state, which automatically transitions to
another state when the instance is created.
3.4.1 Definitions: Events, States, and Transitions
 An event is a significant or noteworthy occurrence. Eg: A telephone receiver is taken off the
hook.
 A state is the condition of an object at a moment in time the time between events. Eg: A
telephone is in the state of being "idle" after the receiver is placed on thehook and until it is taken
off the hook.
 A transition is a relationship between two states that indicates that when an event occurs, the
object moves from the prior state to the subsequent state. Eg: When the event "off hook" occurs,
transition the telephone from the "idle" to"active" state.
3.4.2 Guidelines: To Apply State Machine Diagrams
Object can be classified into
1) State-Independent Object: If an object always responds the same way to an event, then it is
considered state-independent.
2) State-Dependent Objects: State-dependent objects react differently to events depending on their
state or mode.
Guidelines: Consider state machines for state-dependent objects with complex behavior, not for
state-independent objects.
Example: A telephone is very state-dependent. The phone's reaction to pushing a particular button
(generatingan event) depends on the current mode of the phone-off hook, engaged, in a configuration
subsystem, and so forth.
Modeling State-Dependent Objects:
State machines are applied in two ways:
1. To model the behavior of a complex reactive object in response to events.

2. To model legal sequences of operations protocol or language specifications.
1. Complex Reactive Objects
a) Physical Devices controlled by software
 Phone, car, microwave oven: They have complex and rich reactions to events, and the
reaction depends upon their current mode.
b) Transactions and related Business Objects
 How does a business object (a sale, order, payment) react to an event?
 Example: What should happen to an Order if a cancel event occurs?And understanding
all the events and states that a Package can go through in the shipping business can help
with design, validation, andprocess improvement.
c) Role Mutators: These are objects that change their role.
 A Person changing roles from being a civilian to a veteran. Each role isrepresented by a
state.
Example: Physical Devices / Nested States – Telephone Object
 A state allows nesting to contain substates
 A substate inherits the transitions of its superstate (the enclosing state).
 It may be graphically shown by nesting them in a superstate box
 Example: When a transition to the Active state occurs, creation and transition into the
PlayingDialTone substate occurs. No matter what substate the object is in, if the on hook
event related to the Active superstate occurs, a transition to the Idle state occurs.
Example: Transactions and related Business Objects

Order Processing System – Order Object
2. Protocols and Legal Sequences
a) Communication Protocols: TCP, and new protocols, can be easily and clearly understood
with a state machine diagram. Example: A TCP "close" request should be ignored if the protocol
handler is already in the "closed" state.
b) UI Page/Window Flow or Navigation: When doing UI modeling, it can be useful to understand
the legal sequence between Web pages or windows;
State Machine Diagram - Web Page Navigation Modeling
c) UI Flow Controllers or Sessions: These are usually server-side objects representing an
ongoing session or conversations with a client. Example: A Web application that remembers
the state of the session with a Web client and controls the transitions to new Web pages,
or the modified display of thecurrent Web page, based upon the state of the session and the
next operation that is received.

d) Use Case System Operations: The system operations for Process Sale: makeNewSale,
enterItem etc. These should arrive in a legal order. Example: endSale should only come after
one or more enterItem operations.
STATE DIAGRAM: COFFEE VENDING MACHINE
3.4.3 When to Use State Diagram
 To model the object states of a system.

 To model lifetime of an object from creation to termination.
 To model the reactive system.
 To identify the events responsible for state changes.
 Forward and reverse engineering.

3.5 ACTIVITY DIAGRAM
 It shows sequential and parallel activities in a process.
 Theyare useful for modeling business processes, workflows, data flows, and complex algorithms.
PURPOSE: To understand & communicate the structure & dynamics of the organization in which a
system is to be deployed.
ELEMENTS: Start, end, activity, action, object, fork, join, decision, merge, time signal, rake,accept
signal, swim lane
Symbol Name Use
Start/ Initial Node
Used to represent the starting point or the
initial state of an activity
Activity /
ActionState
Used to represent the activities of the
process
Action
Used to represent the executable sub-areas of
an activity
Object Used to represent the object
Control Flow /
Edge
Used to represent the flow of control from one
action to the other
Object Flow /
Control Edge
Used to represent the path of objects moving
through the activity
Decision Node
Used to represent a conditional branch point
with one input and multiple outputs
Merge Node
Used to represent the merging of flows. It has
several inputs, but one output.
Fork
Used to represent a flow that may branch into
two or more parallel flows
Merge
Used to represent a flow that may branch into
two or more parallel flows
Signal Receipt Used to represent that the signal is received

rake
Further can be expanded into sub activity
diagram
swim lane Divides the diagram into vertical zones
Time Signal Timing condition can be specified
Example

Example
This diagram shows a sequence of actions, some of which may be parallel.
Two points to remember:
 Once an action is finished, there is an automatic outgoing transition.
 The diagram can show both control flow and data flow.
3.5.1 Guideline to Apply Activity Diagrams
1. Business Process Modeling
 Client uses activity diagrams to understand their current complex business processes by
visualizing them.
 The partitions are useful to see the multiple parties and parallel actions involved in the shipping
process, and the object nodes illustrate what's moving around.
 Example: Borrow books, return books use case of Library Information system
2. Data Flow Modeling
 Data flow diagrams (DFD) are to visualize the major steps and datainvolved in software system

processes.
 DFD are used to document the major data flows to explore a high-level design.
 Process steps are numbered to indicate order.
3. Concurrent Programming and Parallel Algorithm Modeling
 Parallel algorithms in concurrent programming problems involve multiple partitions, and fork
and join behavior.
 The UML activity diagram partitions can be used to represent different operating system threads
or processes.
 The object nodes can be used to model the shared objects and data.
 Forking can be used to model the creation and parallel execution of multiple threads or
processes, one per partition.
Example: NextGen Activity Diagram

Example: Borrow Books (Library Information System)

3.5.2 When to Use Activity Diagram
 Modeling work flow by using activities.
 Modeling business requirements.
 High level understanding of the system's functionalities.
 Investigating business requirements at a later stage.
Example

IMPLEMENTATION DIAGRAM
3.6 UML PACKAGE DIAGRAM
 It is used to illustrate the logical architecture of a system as layers, subsystems, packages.
 A layer can be modeled as a UML package.
 It is part of the Design Model and also be summarized as a view in the Software Architecture
Document.
 Logical Architecture is the large scale organization of the software classes intopackages,
subsystem and layers. It is called logical architecture because there’s no decision about how
these elements are deployed across different operating system processes or across physical
computers in a network.
 Layer is a coarse grained grouping of classes, packages, or subsystems that has cohesive
responsibility for major aspect of the system.
 There are 2 types of Layers
 Higher Layer (Contain more application specific services. Eg: UI layer)
 Lower layer (Contain more generalized services. Eg: Technical Services layer)
 Higher Layer calls upon services of lower layer, but vice versa is not.
 Typically layers in the Object Oriented System have 7 standard layers. The importantlayers
are
o User Interface: Has various I/O formats & forms.
o Application Logic and Domain Objects: Software objects representing domain
concepts (Eg: software class Sale) that fulfill application requirements, such as
calculating a sale total.
o Technical Services: General purpose objects and subsystems that provide supporting
technical services, such as interfacing with a database or errorlogging.
3.6.1 Architecture Types
 Strict layered architecture: A layer only calls upon the services of the layer directly below
it. This design is common in network protocol stacks, but not in information systems.
 Relaxed layered architecture: A higher layer calls upon several lower layers. Example: The UI
layer may call upon its directly subordinate application logic layer, and also upon elements of a
lower technical service layer, for logging and so forth.
3.6.2 Software Architecture
 Architecture is the set of significant decisions about the organisation of software system.
 Organisation shows their elements, interface, collaboration and their composition.

Layers shown with UML package diagram notation
3.6.3 Elements
Package
Package can group anything: classes,
other packages, use cases
Dependency Depended-on package
Fully qualified Name java::util::Date
To represent a namespace (outer
package named "java" with a nested
package named "util" with a Date class)
Example

Package Diagram: Library Information System
3.6.4 Guidelines
1. Design with Layers
 Organize the large-scale logical structure of a system into discrete layers of distinct, related
responsibilities, with clean, cohesive separations of concerns.
 Collaboration and coupling is from higher to lower layers; lower-to-higher layer coupling is
avoided.
 Source code changes are rippling throughout the system.
 Benefits of Layering
o Layers reduce coupling and increase cohesion
o Complexity is encapsulated and decomposable
o Lower layer contains reusable functions
o Development by teams is aided because of the logical segmentation
2. Cohesive responsibility
 Maintain separation of concerns.
 Responsibilities should not be mixed with responsibilities of other layers.
 Maintain high cohesion, model-view separation principle.
3.6.5 When to Use Package Diagram
 It is used in large scale systems to picture dependencies between majorelements in the system.
 Package diagrams represent a compile time grouping mechanism.

Example

3.7 Component and Deployment Diagrams
3.7.1 Deployment Diagram
 It shows deployment of software elements to the physical structure and the communication
(usually on a network) between physical elements.
 Two Nodes of Deployment Diagram:
o Device Node: This is a Physical Computing Resource representing a computer with
memory or mobile.
o Execution Environment Node: This is a software computing resource that runs
within an outer node (such as a computer) and which itself provides a service to host
and execute other executablesoftware elements. For example:
 An operating system (OS) is software that hosts and executes programs
 A virtual machine (VM, such as the Java or .NET VM) hosts and executes
programs
 A database engine (such as PostgreSQL) receives SQL program requestsand
executes them, and hosts/executes internal stored procedures (written in Java
or a proprietary language)
 A Web browser hosts and executes JavaScript, Java applets, Flash, andother
executable technologies
 A workflow engine
 A servlet container or EJB container
Elements
Device Node
Physical Computing Resource
Execution
Environment Node
{OS = Linux }
{JVM = sun Hot Spot 2.0}
A software computing resource
Communicationpath
Connection between nodes with
protocol name
Artifact Name of the project file

 As the UML specification suggests, many node types may show stereotypes, such as
«server», «OS», «database», or «browser».
 A device node or EEN may contain another EEN. Eg: Avirtual machine within an OS
within a computer.
 A particular EEN can be implied, or not shown, or indicated informally with aUML
property string; Eg: {OS=Linux}.
 Communication Path: The normal connection between nodes which may be labeled
with the protocol. These usually indicate the networkconnections.
 A node may contain and show an artifact a concrete physical element, usually afile.
 This includes executables such as JARs, assemblies, .exe files, and scripts.
 It also includes data files such as XML, HTML, and so forth.
Example: Next Generation POS System
 In the diagram, there are 2 servers namely DellpowerEdge 3600 with RedHat Linux OS,
Tomcat 6, Apache 2.1 are software computing resources, in tomcat server webstore.war file
is loaded.
 In the other server DellpowerEdge 3400 with RedHat Linux OS, database PostgresSQL 10
are software computing resources.
 There are 2 client nodes connected to server via HTTP & SOAP /HTTP protocol.
 In first client exe file is shown as artifact.
 In the other client, web base application is enabled by browser.

When to Use Deployment Diagram
 To model the hardware topology of a system.
 To model the embedded system.
 To model the hardware details for a client/server system.
 To model the hardware details of a distributed application.
 For Forward and Reverse engineering.
3.7.2 Component Diagram
 A component represents a modular part of a system that encapsulates its contents and whose
manifestation is replaceable within its environment.
 A component defines its behavior in terms of provided and required interfaces.
 A component serves as a type, whose conformance is defined by these provided and required
interfaces.
Features of UML Components
 It has interfaces
 It is modular, self-contained and replaceable
Elements
Component
with Provided
Interface
Stand-alone module.
Dependency
System getting services from the
component
Guidelines: Component-based modeling is suitable for relatively large-scaleelements, because
it is difficult to think about or design for many small, fine-grained replaceable parts.

Example: Next Generation POS System
When to Use Component Diagram
 Component diagrams are used to visualize the static implementation view of a system.
 Component diagrams are special type of UML diagrams used for different purposes.
 Component diagrams can be used to:
 Model the components of a system.
 Model the database schema.
 Model the executables of an application.
 Model the system's source code.
Model the components of a system
Example: Order System
Modeling a Physical Database
 Identify the classes in the model that represent the logical database schema.
 Select a strategy for mapping these classes to tables.
 To visualize, specify, construct, and document your mapping, create acomponent diagram
that contains components stereotyped as tables.
 Where possible, use tools to help you transform your logical design into aphysical design.

Modeling an Executable Release
 Identify the set of components to model.
 Consider the stereotype of each component in this set. find a small number of different kinds
of components (such as executables, libraries, tables, files, anddocuments).
 For each component in this set, consider its relationship to its neighbors. It shows only
dependencies among the comp.
Modeling Source Code
 Either by forward or reverse engineering identifies the set of source code files ofinterest and
model them as components stereotyped as files.
 For larger systems, use packages to show groups of source code files.
 Consider exposing a tagged value indicating such information as the version number of the
source code file, its author, and the date it was last changed. Usetools to manage the value of
this tag.
 Model the compilation dependencies among these files using dependencies.
Again, use tools to help generate and manage these dependencies.

CS8592 Object Oriented Analysis & Design - UNIT III

More Related Content

What's hot (20)

Similar to CS8592 Object Oriented Analysis & Design - UNIT III (20)

More from pkaviya (20)

Recently uploaded (20)

CS8592 Object Oriented Analysis & Design - UNIT III