Department of Computer Science and Engineering

Title : Assignment of Booch, Rumbugh and Jacobson methodologies

Authors : Ali Bahrami ,Grady Booch, Robert A. Maksimchuk, Michael W. Engel, and Bobbi J. Young
Reference: www.chettinadtech.ac.in , www.scribd.com, www.srmuniv.ac.in

Booch Jacobson
The Booch’s methodology is a widely used object- oriented method that helps to design a system using the object Object-Oriented Software Engineering (OOSE) is a software design technique that is used in software design in
paradigm. It covers the analysis and design phases of an object-oriented system. object-oriented programming.
The Booch method consists of the following diagrams: OOSE is developed by Ivar Jacobson in 1992. OOSE is the first object-oriented design methodology that employs
 Class diagrams use cases in software design. OOSE is one of the precursors of the Unified Modeling Language (UML), such as
 Object diagrams Booch and OMT.
 State transition diagrams Object-oriented business engineering (OOBE)
 Interaction diagrams Object-oriented software engineering (OOSE)
 Module diagrams  It covers the entire life cycle
 Process diagrams  Stress traceability (enables reuse of analysis and design work) both forward and backward
The Booch methodology prescribes a macro development process and a micro development process. Enables reuse of analysis and design, reduce development time than reuse of code
The Macro Development Process At the heart of their methodologies is the usecase concept, which evolved objector
The macro process serves as a controlling framework for the micro process and can take weeks or even months. Use cases
The primary concern of the macro process is technical management of the system. In the macro process, the tradi-  Scenarios for understanding system requirements.
tional phases of analysis and design to a large extent are preserved.  Non formal text with no clear flow of events.
The macro development process consists of the following steps:  Text easy to read.
 Conceptualization  Formal style using pseudo code.
 Analysis and development of the model  Can be viewed as concrete or abstract (not initiated by actors).
 Design or create the system architecture Object oriented software Engineering: Objectory
 Evolution or implementation. OOSE- is a disciplinary process for the industrialized development of s/w, based on a use-case driven design.
 Maintenance Objectory is built around several different models
Each macro development process has its own micro development processes. 1.Use case model: defines outside (actor) & inside (use case) of the systems behaviour.
The micro process is a description of the day-to-day activities by a single or small group of software developers, 2.Domain object model: object of real world are mapped into the domain obj model.
which could look blurry to an outside viewer, since the analysis and design phases are not clearly defined. 3.Analysis object model: it presents how the source code should be carried out & written.
The micro development process consists of the following steps: 4.Implementation model: rep implementation of the system.
 Identify classes and objects. 5.Test model: constitutes the test plans, specification & reports.
 Identify class and object semantics. Object oriented business Engineering:
 Identify class and object relationships. OOBE is object modelling at the enterprise level.
 Identify class and object interfaces and implementation. Analysis phase
 Object Model
 Requirement
Analysis
 Design & implementation phase
 DBMS
 Distribution of Process
Testing phase
 Unit Testing
Rumbugh  Integration testing
 System Testing
The object-modeling technique (OMT) is an object modeling approach for software modeling and designing. It
was developed around 1991 by Rumbaugh, Blaha, Premerlani, Eddy and Lorensen as a method to devel-
op object-oriented systems and to support object-oriented programming. OMT describes object model or static
structure of the system.
Comparison
Describes the dynamic behavior of objects in a system using the OMT dynamic model. Booch Rumbaugh Jacobson
Four phases
 Analysis – results are objects, dynamic and functional models. Approach Object centered ap- Object centered ap- User centered approach.
 System design – gives a structure of the basic architecture. proach. proach.
 Object design – produces a design document. Phases Covered Analysis, design and im- Analysis, design and im- All phases of life phase
plementation phases. plementation phases. cycle.
 Implementation – produces reusable code.
OMT separates modeling in to three different parts Strength Strong method for pro- Strong method for pro- Strong method for pro-
ducing detailed object ducing object model ducing user driven re-
 Object Model – presented by object model and the data dictionary.
oriented design models. static structure of the quirements and object
 Dynamic model - presented by the state diagrams and event Flow diagrams.
system. oriented analysis model.
 Functional Model – presented by data flow and constraints. Weakness Focus entirely on design Cannot fully express the Do not treat OOP to the
OBJECT MODEL and not on analysis. requirements. same level as other
 Object model describes the structure of objects in a system, their identity and relationships to other objects, methods.
attributes, and operations. Uni-directional relation- Uses. Directed Association.
 The object model is represented graphically with an object diagram. ship
THE OMT DYNAMIC MODEL Bi-directional relation- Associations Associations Acquaintance Relation-
OMT provides a detailed and comprehensive dynamic model ship ships.
 The OMT state transition diagram is a network of states and events. Diagrams used Class diagram, state Data flow diagrams, Use case diagram.
 Each state receives one or more events, at which it makes the transition to the next state. transition diagram, ob- state transmission dia-
 The next state depends on the current state as well as the events ject diagram, timing dia- gram, class/object dia-
gram, Module diagram, gram.
The OMT FUNCTIONAL MODEL
process diagram.
The OMT data flow diagram (DFD) shows the flow of data between different processing in a business.
Data Flow Diagrams use four primary symbols:
 The process is any function being performed Conclusion
 The data flow shows the direction of data element movement Object-Oriented Analysis and design are critical for the success of any type of software related development.
 The data store is a location where data are stored. Analysis help us do the right thing and Design help us do the thing right. The use of Unified Modeling Lan-
 An external entity is a source or destination of a data element. guage can help teams have a better understanding of their project and deliver quality products that meet re-
quirements.

Submitted By
Jaickey Joy Minj UR16CS257
P. Likhith Reddy UR16CS258