Note for Object Oriented Modeling and Design - OOMD by Abhishek Apoorv

Topics ( 9 )

Text from page-1

Object Oriented Modeling and Design 10CS71 OBJECT ORIENTED MODELING AND DESING Subject Code: 10CS71 Hours/Week : 04 Total Hours : 52 PART - A UNIT - 1 I.A. Marks : 25 Exam Hours: 03 Exam Marks: 100 7 Hours INTRODUCTION, MODELING CONCEPTS, CLASS MODELING: What is Object Orientation? What is OO development? OO themes; Evidence for usefulness of OO development; OO modeling history. Modeling as Design Technique: Modeling; abstraction; The three models. Class Modeling: Object and class concepts; Link and associations concepts; Generalization and inheritance; A sample class model; Navigation of class models; Practical tips. UNIT - 2 6 Hours ADVANCED CLASS MODELING, STATE MODELING: Advanced object and class concepts; Association ends; N-ary associations; Aggregation; Abstract classes; Multiple inheritance; Metadata; Reification; Constraints; Derived data; Packages; Practical tips. State Modeling: Events, States, Transitions and Conditions; State diagrams; State diagram behavior; Practical tips. UNIT - 3 6 Hours ADVANCED STATE MODELING, INTERACTION MODELING: Advanced State Modeling: Nested state diagrams; Nested states; Signal generalization; Concurrency; A sample state model; Relation of class and state models; Practical tips. Interaction Modeling: Use case models; Sequence models; Activity models. Use case relationships; Procedural sequence models; Special constructs for activity models. UNIT - 4 7 Hours PROCESS OVERVIEW, SYSTEM CONCEPTION, DOMAIN ANALYSIS: Process Overview: Development stages; Development life cycle. System Conception: Devising a system concept; Elaborating a concept; Preparing a problem statement. Domain Analysis: Overview of analysis; Domain class model; Domain state model; Domain interaction model; Iterating the analysis. PART - B UNIT - 5 7 Hours APPLICATION ANALYSIS, SYSTEM DESIGN: Application Analysis: Application interaction model; Application class model; Application state model; Adding operations. Overview of system design; Estimating performance; Making a reuse plan; Breaking a system in to sub-systems; Identifying concurrency; Allocation of sub-systems; Management of data storage; Handling global resources; Choosing a Dr. SMCE, Bangalore Page 1

Text from page-2

Object Oriented Modeling and Design 10CS71 software control strategy; Handling boundary conditions; Setting the trade-off priorities; Common architectural styles; Architecture of the ATM system as the example. UNIT - 6 7 Hours CLASS DESIGN, IMPLEMENTATION MODELING, LEGACY SYSTEMS: Class Design: Overview of class design; Bridging the gap; Realizing use cases; Designing algorithms; Recursing downwards, Refactoring; Design optimization; Reification of behavior; Adjustment of inheritance; Organizing a class design; ATM example. Implementation Modeling: Overview of implementation; Fine-tuning classes; Fine-tuning generalizations; Realizing associations; Testing. Legacy Systems: Reverse engineering; Building the class models; Building the interaction model; Building the state model; Reverse engineering tips; Wrapping; Maintenance. UNIT - 7 6 Hours DESIGN PATTERNS – 1: What is a pattern and what makes a pattern? Pattern categories; Relationships between patterns; Pattern description. Communication Patterns: Forwarder-Receiver; Client-Dispatcher-Server; PublisherSubscriber. UNIT - 8 6 Hours DESIGN PATTERNS – 2, IDIOMS: Management Patterns: Command processor; View handler. Idioms: Introduction; What can idioms provide? Idioms and style; Where to find idioms; Counted Pointer example. TEXT BOOKS: Text Books: 1. Michael Blaha, James Rumbaugh: Object-Oriented Modeling and Design with UML, 2nd Edition, Pearson Education, 2005. (Chapters 1 to 17, 23) 2. Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal: Pattern-Oriented Software Architecture, A System of Patterns, Volume 1, John Wiley and Sons, 2007. (Chapters 1, 3.5, 3.6, 4) Reference Books: 1. Grady Booch et al: Object-Oriented Analysis and Design with Applications, 3rd Edition, Pearson Education, 2007. 2. Brahma Dathan, Sarnath Ramnath: Object-Oriented Analysis, Design, and Implementation, Universities Press, 2009. 3. Hans-Erik Eriksson, Magnus Penker, Brian Lyons, David Fado: UML 2 Toolkit, Wiley- Dreamtech India, 2004. 4. Simon Bennett, Steve McRobb and Ray Farmer: Object-Oriented Systems Analysis and Design Using UML, 2nd Edition, Tata McGraw-Hill, 2002. Dr. SMCE, Bangalore Page 2

Text from page-3

Object Oriented Modeling and Design 10CS71 INDEX SHEET PART A : UNIT 1: INTRODUCTION, MODELING Page no. 4 -31 CONCEPTS, CLASS MODELING: UNIT 2: ADVANCED CLASS MODELING, 32 – 49 STATE MODELING UNIT 3: ADVANCED STATE MODELING, 50 – 79 INTERACTION MODELING UNIT 4: PROCESS OVERVIEW, SYSTEM 80 – 83 CONCEPTION, DOMAIN ANALYSIS PART – B UNIT 5: APPLICATION ANALYSIS, SYSTEM Page no. 84 – 112 DESIGN UNIT 6: CLASS DESIGN, IMPLEMENTATION 113 – 127 MODELING, LEGACY SYSTEMS UNIT 7: DESIGN PATTERNS – 1 128 – 145 UNIT 8: DESIGN PATTERNS – 2, IDIOMS 146 - 162 Dr. SMCE, Bangalore Page 3

Text from page-4

Object Oriented Modeling and Design 10CS71 Unit1: INTRODUCTION, MODELING CONCEPTS, CLASS MODELING: Syllabus • • • • • • • • • • • • • • ---7hr What is object orientation? What is oo development? Oo themes Evidence for usefulness of oo development Oo modeling history Modeling Abstraction The tree models Objects and class concepts Link and association concepts Generalization and inheritance A sample class model Navigation of class models Practical tips INTRODUCTION Note 1: Intention of this subject (object oriented modeling and design) is to learn how to apply object -oriented concepts to all the stages of the software development life cycle. Note 2: Object-oriented modeling and design is a way of thinking about problems using models organized around real world concepts. The fundamental construct is the object, which combines both data structure and behavior. WHAT IS OBJECT ORIENTATION? 1  Definition: OO means that we organize software as a collection of discrete objects (that incorporate both data structure and behavior). 1 There are four aspects (characteristics) required by an OO approacho Identity. • Classification. • Inheritance. • Polymorphism. 1  Ident ity: • Identity means that data is quantized into discrete, distinguishable entities called objects. • E.g. for objects: personal computer, bicycle, queen in chess etc. Dr. SMCE, Bangalore Page 4