Object-Oriented Systems

Development:
Development
Using the Unified Modeling
Language

Chapter 4:
Object-Oriented Methodologies

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Goals

• Object-Oriented Methodologies
– The Rumbaugh et al. OMT
– The Booch methodology
– Jacobson's methodologies

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Goals (Con’t)

• Patterns
• Frameworks
• Unified Approach (UA)
• layered Architecture

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Basic Definitions
• A methodology is explained as the
science of methods.
• A method is a set of procedures in
which a specific goal is
approached step by step.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Too Many Methodologies
• 1986: Booch came up with the
object-oriented design concept,
the Booch method.
• 1987: Sally Shlaer and Steve
Mellor came up with
the concept of the
recursive design approach.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Too Many Methodologies (Con’t)
• 1989: Beck and Cunningham came up
with class-responsibility-
collaboration (CRC) cards.
• 1990: Wirfs-Brock, Wilkerson, and
Wiener came up with responsibility-
driven design.
• 1991: Peter Coad and Ed Yourdon
developed the Coad lightweight and
prototype-oriented approach.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Too Many Methodologies (Con’t)
• 1991: Jim Rumbaugh led a team at
the research labs of General Electric
to develop the object modeling
technique (OMT).
• 1994: Ivar Jacobson introduced the
concept of the use case.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Survey of Some of the Object-
Oriented Methodologies
• Many methodologies are available to
choose from for system development.
• Here, we look at the methodologies
developed by Rumbaugh et al.,
Booch, and Jacobson which are the
origins of the Unified Modeling
Language (UML) and the bases of the
UA.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Rumbaugh et. al.’s Object
Modeling Technique (OMT)
• OMT describes a method for the
analysis, design, and implementation
of a system using an object-oriented
technique.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 OMT (Con’t)
• OMT consists of four phases,
which can be performed
iteratively:
– 1. Analysis. The results are
objects and dynamic and
functional models.
– 2. System design. The result is a
structure of the basic
architecture of the system.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 OMT (Con’t)
– 3. Object design. This phase
produces a design document,
consisting of detailed objects
and dynamic and functional
models.
– 4. Implementation. This activity
produces reusable, extendible,
and robust code.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 OMT Modeling
• OMT separates modeling into
three different parts:
– 1. An object model, presented by the
object model and the data
dictionary.
– 2. A dynamic model, presented by
the state diagrams and event flow
diagrams.
– 3. A functional model, presented by
data flow and constraints.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 OMT Object Model
Client

firstName
lastName
pinCode ClientAccount Account Transaction

number AccountTransaction transDate

balance transTime
transType
deposit
amount
withdraw
createTransaction postBalance

CheckingAccount

Withdraw
CheckingSavingAccount
SavingsAccount

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 OMT Dynamic Model
No account has been selected

Account has been

Nothing is selected
selected

Select Checking or Select Checking

saving account account

Select transaction
type (withdraw, Enter the amount
deposit, transfer)

Confirmation

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 OMT Functional Model
Data
Store

Process Client Account

Data
Flow
Card
Reader PIN Code Process PIN Code

External
Entity

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Booch Methodology
• The Booch methodology covers
the analysis and design phases of
systems development.
• Booch sometimes is criticized for
his large set of symbols.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Booch Methodology (Con’t)
• The Booch method consists of the
following diagrams:
– Class diagrams
– Object diagrams
– State transition diagrams
– Module diagrams
– Process diagrams
– Interaction diagrams

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Booch Methodology (Con’t)
Car

color
manufacturer
superclass
cost

inherits

Ford

inherits

Mustang Taurus Escort

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Booch Methodology (Con’t)
Operator::TurnOffAlarm

Enabled
SoundAlarm
Silenced Sounding
SilenceAlarm

Enable Disable

AlarmFixed
Disabled

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Booch Methodology (Con’t)

• The Booch methodology

prescribes
– A macro development process

– A micro development process.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Macro Development Process
• The macro development process
consists of the following steps:
– 1. Conceptualization
– 2. Analysis and development of the
model.
– 3. Design or create the system
architecture.
– 4. Evolution or implementation.
– 5. Maintenance.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 The Micro Development Process
• The micro development process
consists of the following steps:
– 1. Identify classes and objects.
– 2. Identify class and object semantics.
– 3. Identify class and object
relationships.
– 4. Identify class and object interfaces
and implementation.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Jacobson et al. Methodologies
• The Jacobson et al. methodologies
(e.g., OOBE, OOSE, and
Objectory) cover the entire life
cycle and stress traceability
between the different phases.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Use Cases
• Use cases are scenarios for
understanding system requirements.
• A use case is an interaction between
users and a system.
• The use-case model captures the
goal of the user and the
responsibility of the
system to its users.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Use Cases (Con’t)
• 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.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Use Cases (Con’t)
– How and when the use case will
store data in the system.
– Exceptions to the flow of events.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Library

Checking out books

Getting an
Interlibrary loan

Doing research

Reading books,
Member
Newspapers

Purchasing Supplies
Supplier

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Object-Oriented Software
Engineering: Objectory
• Object-oriented software
engineering (OOSE), also called
Objectory, is a method of object-
oriented development with the
specific aim to fit the
development of large, real-time
systems.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Objectory (Con’t)
• Objectory is built around several
different models:
– Use case model.
– Domain object model.
– Analysis object model.
Implementation model.
– Test model.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Object-Oriented Business
Engineering (OOBE)
• Object-oriented business
engineering (OOBE) is object
modeling at the enterprise level.
• Use cases again are the central
vehicle for modeling, providing
traceability throughout the
software engineering processes.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Use-case model

Tested in
Realized by
Express in Structured by
Implemented by

OK
NOT OK

Domain Object Analysis Design model Implementation Testing model

model model model

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 OOBE (Con’t)

• OOBE consists of :
– Analysis phase
– Design
– Implementation phases and
– Testing phase.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Patterns
• A pattern 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.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Patterns (Con’t)
• The main idea behind using
patterns is to provide
documentation to help categorize
and communicate about solutions
to recurring problems.
• The pattern has a name to
facilitate discussion and the
information it represents.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Patterns (Con’t)
• A good pattern will do the
following:
• It solves a problem. Patterns
capture solutions, not just abstract
principles or strategies.
• It is a proven concept. Patterns
capture solutions with a track
record, not theories or speculation.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Patterns (Con’t)
• The solution is not obvious. The
best patterns generate a solution
to a problem indirectly—a
necessary approach for the most
difficult problems of design.
• It describes a relationship. Patterns
do not just describe modules, but
describe deeper system structures
and mechanisms.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Patterns (Con’t)
• The pattern has a significant
human component.
• All software serves human
comfort or quality of life; the best
patterns explicitly appeal to
aesthetics and utility.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Capturing Patterns
• Guidelines for capturing patterns:
– Focus on practicability.
– Aggressive disregard of originality.
– Nonanonymous review.
– Writers' workshops instead of
presentations.
– Careful editing.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Frameworks
• A framework is a way of
presenting a generic solution to a
problem that can be applied to all
levels in a development.
• A single framework typically
encompasses several design
patterns and can be viewed as the
implementation of a system of
design patterns.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Differences Between Design
Patterns and Frameworks
• Design patterns are more abstract
than frameworks.
• Design patterns are smaller
architectural elements than
frameworks.
• Design patterns are less specialized
than frameworks.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Unified Approach
• The idea behind the UA is not to
introduce yet another
methodology.
• The main motivation here is to
combine the best practices,
processes, methodologies, and
guidelines along with UML
notations and diagrams.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Develop Use- Develop Identify classes,
Cases, activity Refine
interaction relationships, and
diagrams diagrams attributes &
Identify Actors prototyping iterate
methods

Construction O-O Analysis

Component Layered
Based Repository Approach
Development of use-cases,
analysis,
Continuous design, UI,
Testing and past
Experiences
Patterns
User satisfaction Documentation UML Based
usability tests, & Traceability Modeling
quality assurance
test O-O Design
Design classes, Apply Design Designv view User satisfaction &
their attributes, Axioms and access Usability tests
methods, Layers and based on use cases
association, Build UML class
diagram prototypes
structure ...
Continuous Testing

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Unified Approach (UA)
• The unified approach to software
development revolves around (but
is not limited to) the following
processes and components.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 UA Processes (Con’t)
• The processes are:
– Use-case driven development.
– Object-oriented analysis.
– Object-oriented design.
– Incremental development and
prototyping.
– Continuous testing.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 UA Methods and Technology
• The methods and technology
employed includes:
– Unified modeling language (UML)
used for modeling.
– Layered approach.
– Repository for object-oriented
system development patterns and
frameworks.
– Promoting Component-based
development.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 UA Object-Oriented Analysis:
Use-Case Driven
• The use-case model captures the
user requirements.
• The objects found during analysis
lead us to model the classes.
• The interaction between objects
provide a map for the design
phase to model the relationships
and designing classes.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 UA Object-Oriented Design
• Booch provides the most comprehensive
object-oriented design method.
• However, Booch methods can be
somewhat imposing to learn and
especially tricky to figure out where to
start.
• UA realizes this by combining Jacobson
et al.'s analysis with Booch's design
concept to create a comprehensive design
process.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Iterative Development and
Continuous Testing
• The UA encourages the
integration of testing plans from
day 1 of the project.
• Usage scenarios or Use Cases can
become test scenarios; therefore,
use cases will drive the usability
testing.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Modeling Based on the Unified
Modeling Language
• The UA uses the unified modeling
language (UML) to describe and
model the analysis and design
phases of system development.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The UA Proposed Repository
• The requirement, analysis, design, and
implementation documents should be
stored in the repository, so reports can
be run on them for traceability.
• This allows us to produce designs that
are traceable across requirements,
analysis, design, implementation, and
testing.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 The Layered Approach to
Software Development
• Most systems developed with
today's CASE tools or client-server
application development
environments tend to lean toward
what is known as two-layered
architecture: interface and data.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Two-Layer Architecture
• In a two-layer system, user
interface screens are tied directly
to the data through routines that
sit directly behind the screens.

Name
Address
Title
Owner Data

Workstation

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Problem With the Two-Layer
Architecture
• This approach results in objects
that are very specialized and
cannot be reused easily in other
projects.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Three-Layer Architecture
• Your objects are completely
independent of how:
– they are represented to the user
(through an interface) or
– how they are physically stored.

Name
Address
Title
Owner Data

Workstation

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 User Interface layer
This layer is typically responsible
for two major aspects of the
applications:
• Responding to user interaction
• Displaying business objects.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Business Layer
• The responsibilities of the
business layer are very straight-
forward:
• model the objects of the business
and how they interact to
accomplish the business
processes.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Business Layer: Real Objects
(Con’t)
These objects should not be
responsible for:
• Displaying details
• Data access details

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Access Layer
• The access layer contains objects
that know how to communicate
with the place where the data
actually resides,
• Whether it be a relational
database, mainframe,
Internet, or file.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Access Layer
• The access layer has two major
responsibilities:
• Translate request
• Translate result

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Three-Layered Architecture

Access
Layer

Business
Layer

View
Layer

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Summary
• we looked at current trends in
object-oriented methodologies,
which have been toward
combining the best aspects of
today's most popular methods.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill

 Summary (Con’t)
• Each method has its strengths.
Rumbaugh et al. have a strong method
for producing object models.
• Jacobson et al. have a strong method
for producing user-driven requirement
and object-oriented analysis models.
• Booch has a strong method for
producing detailed object-oriented
design models.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Summary (Con’t)
• Each method has weakness, too. While
OMT has strong methods for modeling
the problem domain, OMT models
cannot fully express the requirements.
• Jacobson, although covering a fairly
wide range of the life cycle, does not
treat object-oriented design to the same
level as Booch, who focuses almost
entirely on design, not analysis.
Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill
 Summary (Con’t)
• The UA is an attempt to combine
the best practices, processes, and
guidelines along with UML
notations and diagrams for better
understanding of object-oriented
concepts and object-oriented
system development.

Object-Oriented Systems Development Bahrami ? Irwin/ McGraw-Hill