UNIT- I

DAY- 6
-K. Indhu
 GOALS
• BASIC DEFINITIONS
– METHOD
– METHODOLOGY
• VARIOUS METHODOLOGIES INVENTED
DURING RESEARCH.
• OBJECT-ORIENTED METHODOLOGIES
– The Rumbaugh et al. OMT
– The Booch methodology
– Jacobson's methodologies

27-DEC-13 K. INDHU 2
 BASIC DEFINITIONS
• What is a method?
• A method is a set of procedures in which a
specific goal is approached step by step.

• What is a methodology?
• A methodology is explained as the science of
methods.

27-DEC-13 K. INDHU 3
 TOO MANY METHODOLOGIES
YEAR METHODOLOGY INVENTED
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.
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.
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.

27-DEC-13 K. INDHU 4
 SURVEY OF METHODOLOGIES
• Many methodologies are available to choose from
for system development.

• But, we concentrate at the methodologies

developed by-
1. Rumbaugh et al.,
2. Booch and,
3. Jacobson
– which are the origins of the Unified Modeling
Language (UML) and the bases of the UA, that is Unified
Approach.

27-DEC-13 K. INDHU 5
 RUMBAUGH ET. AL.’S OMT
• Jim Rumbaugh’s Object Modeling Technique
(OMT)
– Describes a method for the analysis, design and
implementation of a system using an object-oriented
technique.
– OMT is a fast and intuitive approach for identifying
and modeling all the objects .
– Details such as class attributes, method, inheritance,
association also can be expressed easily.
– OMT lets us specify detailed state transitions and
their descriptions within a system.

27-DEC-13 K. INDHU 6
 RUMBAUGH ET. AL.’S OMT
• Jim Rumbaugh’s Object Modeling Technique consists
of four phases, which can be performed iteratively:-
1. Analysis:- The results are objects and dynamic and
functional models.
2. System Design:- The results are a structure of the basic
architecture of the system.
3. Object Design:- This phase produces a design document,
consisting of detailed objects static, dynamic and
functional models.
4. Implementation:- This activity produces re-usable,
extendible and robust code.

27-DEC-13 K. INDHU 7
 RUMBAUGH ET. AL.’S OMT
• Jim Rumbaugh’s Object Modeling Technique
(OMT) separates models into three different
parts:-

1. An Object model- describes the structure of

objects in a system.
2. A Dynamic model– depicts states, events and
transition and actions.
3. A Functional model- shows the flow of data
between different processes.

27-DEC-13 K. INDHU 8
 RUMBAUGH ET. AL.’S OMT
1. OMT Object Model:-
– Describes the structure of objects in a system; their identity,
relationships to other objects,

– Attributes of the object

– Operations of the object

– The object model is represented graphically with an object diagram.

– The object diagram contains classes interconnected by association

lines.

27-DEC-13 K. INDHU 9
 OMT OBJECT MODEL

27-DEC-13 K. INDHU 10
 RUMBAUGH ET. AL.’S OMT
2. OMT Dynamic Model:-
• It depicts states, transitions, event and actions.
• Each state, after receiving one or more events, makes the transition to the next
state.

27-DEC-13 K. INDHU 11
 OMT FUNCTIONAL MODEL

27-DEC-13 K. INDHU 12
 RUMBAUGH ET. AL.’S OMT
3. OMT Functional Model:-
• The OMT data flow diagram(DFD) shows the flow of data between different
processes in a business.

• DFD uses four primary symbols:-

1. The process is any function being performed; for (eg) verify Password(PIN) in the ATM
system.
2. The data flow shows the direction of data element movement; for example, PIN code.
3. The data store is a location where data are stored; for example, account is a data store
in ATM example.
4. An external entity is a source or destination of a data element; for example, the ATM
Card Reader.

• OVERALL RUMBAUGH ET AL. OMT METHODOLOGY PROVIDES ONE OF

THE STRONGEST TOOL SETS FOR ANALYSIS & DESIGN OF OBJECT
ORIENTED SYSTEMS.

27-DEC-13 K. INDHU 13
 THE BOOCH METHODOLOGY
• It designs the system using object paradigm.

• It describes
1. Macro development process
2. Micro development Process

• The Booch method consists of the following diagrams:

– Class diagrams
– Object diagrams
– State transition diagrams
– Module diagrams
– Process diagrams
– Interaction diagrams

27-DEC-13 K. INDHU 14
 CLASS DIAGRAM EXAMPLE

27-DEC-13 K. INDHU 15
 CLASS DIAGRAM EXAMPLE

27-DEC-13 K. INDHU 16
 CLASS DIAGRAM- ATM

27-DEC-13 K. INDHU 17
 OBJECT DIAGRAM EXAMPLE

27-DEC-13 K. INDHU 18
 STATE TRANSITION DIAGRAM EXAMPLE

27-DEC-13 K. INDHU 19
 THE BOOCH METHODOLOGY
• The macro development process consists of the following steps:-
1. Conceptualization:-
– During this, Establish the Core Requirements of the System.
2. Analysis and development of the Model:-
– In this step, we use the class diagram to describe the roles and responsibilities
that objects are to carry out.
3. Design or create the system architecture:-
– We use the class diagram to decide what classes exist and how they relate to each
other.
– We use the object diagram to decide how object collaborate.
4. Evolution or implementation:-
– Refine the system through many iterations.
– Produce Software Implementations.
5. Maintenance:-
– To add new requirements and eliminate bugs, if any.

27-DEC-13 K. INDHU 20
 THE BOOCH METHODOLOGY
• Each macro development process has its own
micro development processes.
• In general, the micro development process consists
of the following steps:-

1. Identify classes and objects.

2. Identify class and object semantics (grammar of
particular language).
3. Identify class and object relationships.
4. Identify class and object interfaces & implementation.

27-DEC-13 K. INDHU 21
 THE JACOBSON ET AL. METHODOLOGIES
• It consist of-
1. Use Cases & Use Case Diagram,
2. Object oriented Software Engineering(OOSE):
Objectory,
3. Object oriented Business Engineering(OOBE)

• It covers the entire life cycle of development.

• Heart of the methodologies – USE CASE Concept.

27-DEC-13 K. INDHU 22
 USE CASES
• Use cases are scenarios for understanding system requirements.
• A Use Case is an interaction between an end-user and a system.
• The use-case model captures all kinds of users and their
respective responsibilities to the system.
• Use Cases can be described as one of the following:-
– Non-formal Text with no clear flow of event.
– Text, easy to read but with a clear flow of events to follow
– Formal styles using pseudo code.

• Every single Use Case should describe one main flow of events.

27-DEC-13 K. INDHU 23
 USE CASE DIAGRAM

27-DEC-13 K. INDHU 24
 SIMPLE USE CASE DIAGRAM

27-DEC-13 K. INDHU 25
 USE CASES
• The Use Case Diagram employs 2 kinds of relationships:-
1. Extends &
2. Uses

1. The Extends relationship is used when we have one use case

that is similar to another use case but does a bit more.
• That is, the second use case(that is similar to first use case)
extends the functionality of the 1st Use Case.(like subclass in
inheritance)

2. The Uses relationship re-uses common behavior in different

use cases.

27-DEC-13 K. INDHU 26
 USE CASES
• Use Cases could be viewed as-
1. Concrete or,
2. Abstract.

1. An abstract use case is-

– not complete and
– has no actors that initiate it,
– but it is used by another use case.
2. Abstract use cases are the ones that have uses or
extends relationships.
27-DEC-13 K. INDHU 27
 OBJECT ORIENTED SOFTWARE ENGINEERING-
OBJECTORY
• This process used to develop large real time system.

• It is a use case driven development process.

• Objectory is built around several different models:-

– Use case model
• Actors, Use-Cases of each Actor
– Domain object model
• Classes, their Associations
– Analysis object model
• How the source code should be carried out and written.
– Implementation model
• Implementation of the system.
– Test Model
• Test Plans, Test Reports.

27-DEC-13 K. INDHU 28
 OBJECT ORIENTED BUSINESS ENGINEERING
• OOBE is object modeling at the enterprise level.
• OOBE consists of below 3 phases-
1. ANALYSIS PHASE:-
• define the system to be built in terms of problem domain object
model, the requirement model, and the analysis model
• This reduces complexity of the system.
2. DESIGN & IMPLEMENTATION PHASE:-
• The implementation environment must be identified for the design
model.
• Analysis objects are translated into design objects.
3. TESTING PHASE:-
• This level includes unit testing, integration testing and system
testing.

27-DEC-13 K. INDHU 29
HAPPY LEARNING!!!