unit-2 - UNIT-II CHAPTER 4 OBJECT ORIENTED METHODOLOGIES OBJECTIVES At the end of this chapter students should be able to Define and understand the

unit-2 - UNIT-II CHAPTER 4 OBJECT ORIENTED METHODOLOGIES...

This preview shows page 1 - 6 out of 64 pages.

1 UNIT-II CHAPTER- 4 OBJECT ORIENTED METHODOLOGIES OBJECTIVES: At the end of this chapter, students should be able to Define and understand the software development process Describe the object-oriented systems development List and explain the object-oriented methodologies INTRODUCTION: Basic Definitions A methodology is explained as the science of methods. A method is a set of procedures in which a specific goal is approached step by step. 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.
Image of page 1
2 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. O bject-Oriented Systems Development: Using the Unified Modeling Language Goals Object-Oriented Methodologies The Rumbaugh et al. OMT The Booch methodology Jacobson's methodologies Unified Approach (UA) layered Architecture
Image of page 2
3 Survey of Some of the Object-Oriented Methodologies Many methodologies are available to choose from for system development. Here, we look at the methodologies developed by Rumbaugh et al., Booch, and Jacobson which are the origins of the Unified Modeling Language (UML) and the bases of the UA. Rumbaugh et. al.’s Object Modeling Technique (OMT) OMT describes a method for the analysis, design, and implementation of a system using an object-oriented technique. OMT consists of four phases, which can be performed iteratively: 1. Analysis . The results are objects and dynamic and functional models. 2. System design . The result is a structure of the basic architecture of the system. 3. Object design . This phase produces a design document, consisting of detailed objects and dynamic and functional models. 4. Implementation . This activity produces reusable, extendible, and robust code.
Image of page 3
4 OMT Modeling OMT separates modeling into three different parts: 1. An object model , presented by the object model and the data dictionary. 2. A dynamic model , presented by the state diagrams and event flow diagrams. 3. A functional model , presented by data flow and constraints. Object Model Describes structure of objects in system Identity Relationship to other objects Attributes Operations Represented graphically with object diagram Contains classes interconnected by association lines Each class represents a set of individual objects Association line represents set of links from objects of one class to objects of another class
Image of page 4
5 OMT Object Model of a Bank System OMT Dynamic Model OMT state transition diagram is a network of states & events
Image of page 5
Image of page 6

You've reached the end of your free preview.

Want to read all 64 pages?

  • Spring '16
  • Prasanth t
  • Object Oriented, OMT

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes