Q. Explain Booch Methodology.

A. BOOCH METHOD:
 Booch developed Object-Oriented Design concept in 1986—and is widely used Object-Oriented
methodology.
 Covers Analysis and Design phases of object-oriented system.
 Produces detailed object oriented models.
 Booch sometimes is criticized for his large set of symbols…many of his symbols and diagrams are
never required.
 The main advantage of using Booch method is that you can document your object-oriented code.
 Booch provide so comprehensive OO- design method that the method can be somewhat imposing to
learn and especially tricky to figure out where to start.
 The Method:
 Start with class and object diagrams in analysis phase.
 Refine these diagrams in various phases.
 Add design symbols when you are ready to generate the code.
 DOCUMENT YOUR OBJECT ORIENTED CODE (if required).
The Booch method consists of following six diagrams:
 Class diagrams
 Object diagrams
 State Transition diagrams
 Module diagrams
 Interaction diagrams
 Process diagrams
Class diagrams:
A class diagram is used to show the existence of classes and their relationships in the logical view of a
system. A single class diagram represents a view of the class structure of a system. During analysis, we use
class diagram to indicate the common roles and responsibilities of the entities that provide the system’s
behavior. During design, we use classes diagram to capture the structure of the classes that form the
system’s architecture. It is denoted by a dotted cloud shape.
Notation:

Class relationship icons:

1
 Example:

Object diagrams:
An object diagram is used to show the existence of objects and their relationship in the logical design
of a system. A single object diagram is typically used to represent a scenario. During analysis object
diagrams are used to indicate the semantics of primary and secondary scenarios that provide a trace of
system’s behavior. During design, it is used to illustrate the semantics of mechanisms in the logical design
of a system. Objects interact through links to other objects.
Notation:

Fig: object icon Fig: object link icon

State transition diagrams:

A state transition diagram is used to show the state space of a given class, the events that causes a
transition from one state to another and the actions that result from a state change. A single state transition
diagram represents a view of the dynamic model of a single class or of the entire system. State transition
diagram show the event- ordered behavior of the system as a whole. During analysis it is use to indicate the
dynamic behavior of the system. During design it is used to capture the dynamic behavior of individual
classes.
Notation:

Fig: state icon Fig: state transition icon

Module diagrams:
A module diagram is used to show the allocation of classes and objects to modules in physical design
of the system. A single module diagram represents a view of the module structure of a system. During
development we use module diagram to indicate the physical layering and partitioning of our architecture.
The main program icon denotes a file that contains the root of program. The specification and body
icon denote files that contain declaration and definition of entities respectively. Subsystems represent
clusters of logically related modules.

2
 Notation:

Interaction diagrams:
An interaction diagram is used to trace the execution of the scenario in the same context as an object
diagram. It is a simpler way of representing the object diagram. The advantage of using interaction diagram
is that it is easier to read the passing of messages in relative order. This diagram tends to focus on events as
opposed to operations because events help to define boundaries of a system under development.
An interaction diagram appears in tabular form. Entities are written horizontally across top of the
diagram. A dashed vertical line is drawn below each object. Messages are shown horizontally and their
ordering is indicated by vertical positions.
Notation:

Process diagrams:
A process diagram is used to show the allocation of the processes to processors in the physical
design of the system. A single process diagram represents a view into the process structure of the system.
During development process diagram is used to indicate the physical collection of processors and devices
that serve as the platform for execution of a system.
A processor is a piece of hardware capable of executing programs and a name is required for each
processor. A device is a piece of hardware incapable of executing any program and there are no particular
constraints on the device names. Processor and device communicate with one another using undirected lines.
Notation:

The Booch methodology prescribes a Macro development process and a Micro development process.
The Macro Development Process:
The macro process serves as a controlling framework for the micro process and can take weeks and
even months. The primary concern of the macro process is technical management of the system. The macro
process focuses upon risk and architectural vision that have the greatest impact upon schedules, quality and
completeness. The macro process tends to track the following activities:
 Establish the core requirements for the software (conceptualization).
3
  Develop a model of the system’s desired behavior (analysis).
 Create architecture for the implementation (design).
 Evolve the implementation through successive refinement (evolution).
 Manage post delivery evolution (maintenance).
The Micro Development Process
Each macro development process has its own micro development processes. The micro process is a
description of the day-to-day activities by a single and small group of software developers, which could look
blurry to an outside viewer, since the analysis and design phases are not clearly defined.
The micro development process consists of the following steps:
 Identify the classes and objects.
 Identify the classes and object semantics.
 Identify the classes and object relationships.
 Identify the classes and object interfaces and implementation.

Q. Explain Rambaugh OMT

A. RUMBAUGH’S OBJECT MODELING TECHNIQUE:
 In 1991 Jim Rumbaugh developed the Object modeling Technique (OMT).
 It describes a method for the analysis, design and implementation of a system using an object
oriented technique.
 It is fast, intuitive approach for identifying and modeling all the objects making up a system.
 OMT methodology provides one of the strongest tool sets for the analysis and design of object
oriented system.
 OMT consist of four phases, which can be performed iteratively:
o Analysis: The results are objects and dynamic and functional models.
o System design:The results are the structure of the basic architecture of the system along with
high level strategy decisions.
o Object design: This phase produces a design document, consisting of detailed objects
static, dynamic, and functional models.
o Implementation: This activity produces reusable, extendible and robust code.

OMT separates modeling into three different parts:

o Object model, presented by the object model and the data dictionary.
o Dynamic model, presented by the state diagrams and event flow diagram.
o Functional model, presented by data flow and constraints.

The Object Model:

The model describes the structure of objects in a system: their identity, relationships to other objects,
and operations. The object model is represented graphically with an object diagram. The object diagram
contains classes interconnected by association lines. Each class represents a set of individual objects. The
association lines establish relationships among the classes. Each association line represents a set of links
from the objects of one class to the objects of another class.

4
 Notation:

Fig: Class icon Fig: Object icon

The OMT Dynamic Model:

OMT provides a detailed and comprehensive dynamic model, in addition to letting you depict states,
transitions, events, and actions. The OMT state transition diagram is a network of states and events, each
state receives one or more events, at which time it makes the transition to the next state. The next depends
on the current state as well as the events.
Notation:

name
Fig: State icon Fig: Start icon and transitions

The OMT Functional Model:

The OMT data flow diagram (DFD) shows the flow of the data between different processes in a
business. An OMT DFD provides a simple and intuitive method for describing business process without
focusing on the details of computer systems.
Data flow diagrams use four primary symbols:
1. The process is any function being performed; for example, verify Password
or 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 the ATM example.
4. An external entity is a source or destination of a data element; for example,
the ATM card reader.

WHAT IS SOFTWARE TESTING?

SOFTWARE TESTING:
Testing is the process used to help to identify the correctness, completeness and quality of developed
computer software.
Testing can never completely establish the correctness of arbitrary computer software.
Testing is nothing but criticism or comparison, i.e comparing the actual value with expected one.
There are many approaches to software testing but effective testing of complex products is essentially
a process of investigation, not merely a matter of creating and following wrote procedure.
One definition of testing is “the process of questioning a product in order to evaluate it”, Where the
“questions” are things the tester tries to do with the product, and the product answers with its behavior in
reaction to the probing of the tester.
Although most of the intellectual processes of testing are nearly identical to that of review or
inspection, the word testing is connoted to mean the dynamic analysis of the product –putting the product
through its paces.
5
 The quality of the application can, and normally does, vary widely from system to system but some of
the common quality attributes include reliability, stability, portability, maintainability and usability.

Software testing matrix:

It is a document which maps requirements with test cases. By preparing traceablility matrix we can ensure
that we have covered all functionalities in our test cases. Traceability matrix is a document matrix is a
document defines mapping between customer requirements and prepared test cases. It is a proof of
document to ensure that all the specifications are been tested and the application is bug free.

Grady Booch Jim Rumbaugh Ivar Jacobson

Developed OOD concept Developed OMT in 1991 Introduced OOSE and

in 1986 Use-Case concept in
1994

Phases Prescribes two Has four phases: OOBE has three

processes: Macro Analysis, System Design, phases: Analysis,
development process, Object design, Design and
Micro development Implementation Implementation,
process Testing

Models or Six diagrams: Three models: Five models:

Diagrams
 Class diagrams  Object model  Use-case model
 Object diagrams  Class diagram  Domain object
 State Transition  Object diagram model
diagrams  Dynamic model  Analysis object
 Module diagrams  State transition model
 Process diagrams diagram  Implementation
 Interaction diagrams  Functional model model
 Data flow diagram  Test model

Strength Well suited for Produces detailed object Good for producing
describing the object oriented design models user- driven analysis
model or the static models
structure of the syst.

Weakness OMT cannot fully Booch focuses totally on Deemphasize object

6
 express the requirements design and not analysis modelling

Class
Notations

(Dashed ambiguous
blob) (Rectangle)

Object
Notations

(rounded
(ambiguous blob) rectangle)