You are on page 1of 26

Agenda

01 Basics

Lets get to know OOAD

02 BOOCH Method Theory

Concepts and in depth explanation of major sub topics

03 BOOCH Method Practical Application

Intuitive and Practical diagrammatic representation those concepts


Object Oriented Analysis and Design
Basic Terminology
Object
An object is a concept, abstraction, or thing with identity that has meaning for an application. Objects
often appear
as proper nouns or specific references in problem descriptions and discussions with users.

Class
A class describes a group of objects with the same properties (attributes), behavior (operations),
kinds of
relationships, and semantics.

Object Oriented
Superficially the term object-oriented (OO) means that we organize software as a collection of
discrete objects that
incorporate both data structure and behavior. It generally include four aspects: identity, classification,
inheritance, and polymorphism.
Object Oriented Analysis and Design
Basics
What is the purpose of a software?
Is developing software easy?

Basically, good structures have object-oriented tendency

OOAD is a popular technical approach for visual modeling throughout the development life
cycles for better communication and product quality.

Advantages:
 Changing requirements
 Easier to maintain
 More robust
 Code reuse
 Higher Level of Abstraction
Object Oriented Methodology
Object Oriented Methodology

• The Booch Methodology

• The Rumbaugh et al OMT

• The Jacobson’s et al methodology of a system

We are going to discuss “The BOOCH METHODOLOGY”


THE BOOCH METHODOLOGY
•The Booch methodology is a widely used
object oriented
method that helps to design the system using
the object paradigm.
•It covers the analysis and design phases of
the object oriented system.
The booch methodology consists of several
diagram
Diagram Uml correspondence
Class diagram Class diagram
Object diagram Object diagram
State transition diagram State chart diagram
Intersection diagram Sequence diagram
Module diagram Component diagram
Process diagram Deployment diagram
Booch Methodology

Macro

methodology
Development
Process
Booch

Micro
Development
Prcoess
The Macro Development Process

• Conceptualization
• Analysis and development of the model
• Design or create the system architecture
• Evolution or implementation
• Maintenance
Develop a model
of the desired
behavior(analysis)

Establish core Create an


requirements architecture
(Conceptualization) (Design)

Manage post Evolve the


delivery implementation
evolution
(Maintenance ) (Evolution)
Conceptualization
• Conceptualization:-
Establish the core requirement.
Establish a Set of Goals.
Develop a prototype
• For a new piece of software or even for the novel
adoption of an existing system there is a moment when
an idea for some application springs up in the mind of
the developer, the architect, the analyst or the end
use.
• The purpose of conceptualization is to establish the
vision for the idea and validate its assumptions.
Analysis
The purpose of the analysis is to provide a description of a problem.
In our terms, the purpose of the analysis is to provide a model of the
system’s behavior.
In analysis , we look towards a model as world by identifying the
classes and objects (and their roles , responsibilities and collaborations)
that form the vocabulary of the problem domain
function points ,denote the outwardly observable and testable behavior
of a system.
Products, In OOD , we capture these descriptions through scenarios,
where each scenario denotes some particular function point.
Activity, Two primary activities associated with analysis:
domain analysis
scenario planning
Design
The purpose of design to create an architecture for revolving
the implementation and to establish common tactical policies
that must be used by disparate elements of the system

• Design or create the system architecture


- class diagram to describe what classes exist and how they relate.
- object diagram describes what mechanisms are used to regulate
how objects collaborate.
- module diagram to map out where each class and object should
be declared.
- process diagram to describe which processor to allocate a process,
schedule for multiple processes on each relevant processor.
Products of Design
There are two primary products of design :-

• A description of the architecture


•Description of common tactical policies

Activities :- There are three activities associated with design


• Architecture Planning
• Tactical Design
• Release Planning
Evolution
• Evolution or implementation:-
iterations
Streams of software
Products:-
The primary product of evolution is a stream of executable releases
representing successive refinements to initial architectural.
Activities :-
The activities associated with evolution are:-
•Application of micro processes
•Change management
Maintenance
•make design add new requirements eliminate bugs.
•Maintenance is the activity of managing post-delivery evolution.
•More localize changes are made to the system as new requirements are added
and lingering bugs are stamped out.
• A punch list serves as the vehicle for collecting bugs and enhancement
requirments ,so that they can be prioritized for future releases.
•In addition to usual activities of evolution ,maintenance involves a planning
activity that prioritizes task on punch list.

The Micro Development Process
• The micro process is a description of the day–to–day activities by a
single or small group of software developers.
• Identify classes and objects
• Identify class and object semantics
• Identify class and object interfaces and implementations.
The Micro Development Process
Activities
- Establish a set of goals for proof of concept, including the time limit
with the effort is to be finished.
- Assemble an appropriate team to develop the prototype.
- Evaluate the resulting prototype and make an explicit decision for
product development or further exploration.
Class Diagram
Symbol showing class relations

1. Association

2. Inheritance Class Name

3. Has
Attributes
Operations
4. Using

5. Abstract Class

A
Class Diagram
Lets create a class diagram for banking system

User
Attributes
Operations
Bank Consortium
Attributes Attributes
Operations Operations
A

Transaction ATM
Online Tras. Attributes
Attributes
Attributes Operations
Operations
Operations
Object Diagram
Object Diagram: Conveys objects and links instead of classes and relationship

B: Bank
Attribute

Br1: Branch Br2: Brach


Code 134 Code 123
Nioda Gurgaon

Zonal Head. Qtr.


Zonal Head. Qtr.
Brn1: Brach
Code 007
New Delhi
State Transition Diagram
Alarm System: State of a Class based of external stimulus.

Initial State Operator: Turn of Alarm

Enabled

Silenced Sounding

Enable Disable

Disabled
Interaction Diagram
Grocery shopping: Diagrams showing how object classes influence each other

Customer Cart Orders item

Get item Get the price get the price

Give price

Recive price
Calculate price
Order price
Module Diagram
Grocery shopping
Diagrams showing how object classes influence each other

Bank atm acc


Process Diagram
Process symbols in Booch Methodologie
Presentation
by

Mr. Vishal Srivastav


&
Mr. Suraj Kr. Agarwal
Thank You

You might also like