Scribd
Upload
40 views13 pages

18mit13c U2

This document discusses several object-oriented methodologies: - The Rumbaugh Object Modeling Technique (OMT) uses objects, dynamic and functional models across four phases: analysis, system design, object design, and implementation. - The Booch methodology uses class, object, state transition, module, and interaction diagrams. It prescribes macro and micro development processes. - Jacobson's methodologies include use cases, object-oriented software engineering (OOSE) using use case, domain, analysis, implementation, and test models, and object-oriented business engineering (OOBE) modeling at the enterprise level.

Uploaded by

Yuvaraj V, Assistant Professor, BCA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
40 views13 pages

18mit13c U2

This document discusses several object-oriented methodologies: - The Rumbaugh Object Modeling Technique (OMT) uses objects, dynamic and functional models across four phases: analysis, system design, object design, and implementation. - The Booch methodology uses class, object, state transition, module, and interaction diagrams. It prescribes macro and micro development processes. - Jacobson's methodologies include use cases, object-oriented software engineering (OOSE) using use case, domain, analysis, implementation, and test models, and object-oriented business engineering (OOBE) modeling at the enterprise level.

Uploaded by

Yuvaraj V, Assistant Professor, BCA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

OBJECT ORIENTED ANALYSIS AND

DESIGN
UNIT-II: Object-Oriented Methodologies- Rumbaugh Object modeling technique-The
Booch methodology-The Jacobson methodologies- The Unified Approach- UML- Class
Diagrams- Dynamic Modeling.

TEXT BOOK
Ali Bahrami, “Object Oriented Systems Development”, TATA McGraw-Hill Edition, 2008.

PREPARED BY
Dr. D. Devakumari
→Object-Oriented Methodologies

→Rumbaugh Object modeling


technique

→The Booch methodology

→The Jacobson methodologies

→ The Unified Approach

→UML

→Class Diagrams

→Dynamic Modeling.
OBJECT-ORIENTED METHODOLOGIES
• The Rumbaugh et al.
O M T.

• The Booch Methodology.

• Jacobson’s
Methodologies.

• Unified approach (UA).


RUMBAUGH OBJECT MODELING TECHNIQUE
• 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 modelling

– An object model - object model & data dictionary

– A dynamic model - state diagrams & event flow diagrams

– A functional model - data flow & constraints


Object Model
– Classes interconnected by association lines
– Classes- a set of individual objects The O MT object model of a
bank system.The boxes represent
– Association lines- relationship among classes (i.e., objects of
one class to objects of another class) classes and the filled triangle
represents specialization.
Association between Account
and
Transaction is one to many;
since one account can have
many transactions, the filled circle
represents many (zero or more). The
relationship between Client
and Account classes is one to one:
A client can have only one
account and account can belong to
only one person (in this model
joint accounts are not allowed).
O M T Dynamic Model
– States, transitions, events and actions
– OMT state transition diagram-network of states and
events

State transition diagram for


the
bank application user

interface. The boxe


round s

represent states and


arrows represent
the
transitions.
O M T 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
– Data Store – Location where data is stored
– External Entity-Source or Destination of a data element
THE BOOCH METHODOLOGY
Diagrams of Booch method

• Class diagrams describe roles and responsibilities of objects

• Object diagrams describe the desired behaviour of the system in terms of


scenarios

• State transition diagrams state of a class based on a stimulus

• Module diagrams to map out where each class & object should be declared

• Process diagrams to determine to which processor to allocate a process

• Interaction diagrams describes behaviour of the system in terms of scenarios.

Booch method prescribes:


• Macro Development Process
• Micro Development Process
Macro Development Process
• Steps for macro development process
1.Conceptualization
2.Analysis & Development of the model
3.Design or create the system
architecture
4.Evolution or implementation
5.Maintenance

Object modeling using Booch notation. The arrows


represent specialization; for example, class Taurus is
subclass of the class Ford.
Micro Development Process
• Each macro process has its own micro development
process

Steps:

- Identify classes & objects

- Identify class & objects semantics

- Identify class & object relationship

- Identify class & objects interface and implementation


THE 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.
O O S E - Object Oriented Software
Engineering.
• Objectory is built around several different models:
– Use case model.The use-case model defines the outside (actors) and inside (use case) of
the systems behaviour.
– Domain object model.The objects of the “real” world are mapped into the domain
object model.
– Analysis object model.The analysis object model presents how the source code
(implementation) should be carried out and written.
– Implementation model.The implementation model represents the implementation of
the system.
– Test model.The test model constitutes the test plans, specifications, and reports.
O O B E - Object Oriented Business Engineering
• OOBE is object modeling at the enterprise level.
– Analysis phase
– D esign and Implementation phase
– Testing phase
• E.g. Unit testing, integration and system testing.

You might also like