Unit-2 (OOAD)
Unit-2 (OOAD)
Rumbaugh Methodology
Booch Methodology
Jacobson Methodology
Patterns
Frameworks
Unified Approach
Unified Modeling Language
Use case
class diagram
Interactive Diagram
Collaboration Diagram
State Diagram
Activity Diagram.
Chapter Objectives
You should be able to define and understand
Object Oriented methodologies.
- The Rumbaugh OMT
- The Booch methodology
- Jacobson’s methodologies
Patterns
Frameworks
Rumbaugh’s Object Modeling Technique (OMT)
-A method for analysis,design and implementation by
an object oriented technique.
-fast and intuitive approach for identifying and
modeling all objects making up a system.
-Class attributes, methods, inheritance and association can
be expressed easily.
-Dynamic behavior of objects can be described using
the OMT dynamic model.
-Detailed specification of state transitions and their
-descriptions within a system
Four phases of OMT
(can be performed iteratively)
Analysis: objects,dynamic and
functional models
System Design: Basic architecture of
the system.
Object Design: static, dynamic and
functional models of objects.
Implementation: reusable, extendible
and robust code.
Three different parts of OMT
modeling
An object model - object model &
data dictionary
A dynamic model - state diagrams &
event flow diagrams
A functional model - data flow &
constraints
Object Model
structure of objects in a system.
Identity, relationships to other
objects, attributes and operations.
Object diagram
Object Diagram
Classes interconnected by
association lines
Classes- a set of individual objects
Association lines- relationship
among classes (i.e., objects of one
class to objects of another class)
OMT Dynamic Model
States, transitions, events and
actions
OMT state transition diagram-
network of states and events
OMT Functional Model
DFD- (Data Flow Diagram)
Shows flow of data between different
processes in a business.
Simple and intuitive method for
describing business processes without
focusing on the details of computer
systems.
Data Flow Diagram
Four primary symbols
Process- any function being performed
Data Flow- Direction of data element movement
and implementation
JACOBSON METHODOLOGIES
Use Cases.
Object Oriented Software
Engineering.
Object Oriented Business
Engineering.
Use Cases
Understanding system requirements
Interaction between Users and Systems
The use case description must contain
How and when the use case begins and ends.
The Interaction between the use case and its actors,
including when the interaction occurs and what is
exchanged.
How and when the use case will need data stored in
the system.
Exception to the flow of events
How and when concepts of the problem domain are
handled.
OOSE
Object Oriented Software
Engineering.
Objectory is built models
Use case model
Domain object model
Analysis object model
Implementation model
Test model
OOBE
Object Oriented Business
Engineering
OOBE is object modeling at the
enterprise level.
Analysis phase
Design and Implementation phase
Testing phase
E.g. Unit testing, integration and system
testing.
PATTERNS
It is an instructive information that
captures the essential structure
and insight of a successful family
of proven solutions to a recurring
problem that arises within a
certain context and system of
forces.
Good Pattern will do the
following
It solves a problem.
It is a proven concept.
The Solution is not obvious.
It describes a relationship.
The pattern has a significant
human component.
Patterns
Patterns
Static Dynamic
1. Class diagram
2. Use case diagram
3. Activity diagram
4. Sequence diagram
5. Collaboration diagram
6. State chart diagram
7. Component diagram
8. Deployment diagram
1. Class diagram
Class a set of objects that share the
same attributes, operations &
relationships.
It represented by a compartmentalized
rectangle.
It shows the structure of your
software.
3 compartments
1. Top
2. Middle
3. Bottom
1. Class diagram
1. Top shows class name
2. Middle shows class attributes
3. Bottom shows class operation
structure of a class.
displayed in the middle of the
compartmentalized
rectangle.
WITHDRAW
CASH
CUSTOMER DISPENSER
CHECK BALANCE
PRINTER
CHANGE PIN
LOGIN
2. Use case diagram (Pay
roll)
Actors employee & account
Customer
Disburse salary
Check loans
Calculate HRA
Calculate PF
Check salary
Prepare IT returns
3.Activity Diagram
It shows the flow of events with
our system & what is going on
inside a use case.
We draw the activity diagram for
each & every use case.
Login (use case) – (e.g.) ATM
It is showing flow of control from
activity to activity.
3.Activity Diagram
Activity it represents the
performance of a task within the
workflow.
Activity is represented by a lozenge
(horizontal top and bottom with convex
sides)
Start state shows the beginning of a
workflow on an activity diagram.
There is only one start state.
3.Activity Diagram
A start state is represented by a
solid circle.
Joint
3.Activity Diagram
A synchronization bar allows you to
show concurrent threads in a work
flow of a use case.
It represented by a thick horizontal
or vertical line.
3.Activity Diagram
A swimlane is used to partition an
activity diagram to help us better
understand who or what is
initiating an activity.
3.Activity Diagram – Login Use
case
[ Fals e ]
Sys tem prom pts to
reenter
[ True ]
Submi t( )
Vali date( )
getLoginDetails( )
5.Collaboration Diagram
It displays objects and their links to
one other.
: LoginForm
: Cus tom er
3: Validate( )
4: getLog inDetails ( )
: LoginControl ler
: Cus t om erInfo
6. State Chart Diagram
It shows the sequence of states.
A state is represented as a rounded
box, which may contain one or more
compartments.
Name compartment holds the
name of the state.
Internal transition compartment
list of actions / activities
Start & end states
7.Component Diagram
It shows relationship between the
components in the system.
1. Use-case view
2. Logical view
3. Process view
4. Component view (Implementation view)
5. Deployment view