The document discusses object oriented methodology and the unified modeling language (UML). It covers traditional software development life cycle models and object oriented approaches. The main object oriented approaches discussed are Rambaugh, Booch, and Jacobson methodologies. It also discusses the rational unified process and UML diagrams used in object oriented analysis and design. Common techniques for identifying classes are described such as noun phrase, common class patterns, use case driven modeling, and classes responsibilities and collaborators.
The document discusses object oriented methodology and the unified modeling language (UML). It covers traditional software development life cycle models and object oriented approaches. The main object oriented approaches discussed are Rambaugh, Booch, and Jacobson methodologies. It also discusses the rational unified process and UML diagrams used in object oriented analysis and design. Common techniques for identifying classes are described such as noun phrase, common class patterns, use case driven modeling, and classes responsibilities and collaborators.
The document discusses object oriented methodology and the unified modeling language (UML). It covers traditional software development life cycle models and object oriented approaches. The main object oriented approaches discussed are Rambaugh, Booch, and Jacobson methodologies. It also discusses the rational unified process and UML diagrams used in object oriented analysis and design. Common techniques for identifying classes are described such as noun phrase, common class patterns, use case driven modeling, and classes responsibilities and collaborators.
Unit 1 - Object oriented methodology Multiplicity
Software development life cycle model: OR association
1. Planning Association Class 2. Defining requirements N-Array Association 3. Designing Aggregation & Composition 4. Building Generalization 5. Testing 2. Use Case Diagram 6. Deployment 3. Behavior Diagram(Dynamic) Traditional life cycle models: 4. Sequence diagram 5. Collaboration diagram 1. Water fall model 6. State Chart Diagram 2. Iterative model 7. Activity Diagram 3. Spiral model 8. Implementation Diagram 4. V- model 9. Component Diagram 5. Big bang model 10. Deployment Diagram 6. RAD model Object oriented approach: UML class diagrams 1. Rambaugh et.al methodology (or) OMT Object model Functional model Unit 3 – object oriented analysis 2. Booch Methodology Usecase driven object analysis Macro development 1. Identify the actors Micro development 2. Develop a simple business process model 3. Jacabson et.al methodology using UML activity diagram Use cases 3. Develop the usecase Object oriented software engineering 4. Prepare interaction diagram (OOSE) : objectory 5. Developing a static UML diagram Object oriented business Engineering Identify classes (OOBE) Identify relationship Analysis phase Identify attributes Design and implementation Identify methods Testing phase 6. Iterate and Refine Rational unified process: Approaches for identifying classes Introduction 1. Noun phrase approach Object oriented analysis Object oriented design i. Identifying tentative class Iterative development & continous ii. Selecting classes from the relevant testing fuzzy category Modeling based on the UML iii. The via- net bank ATMsystem: UA proposed repository identifying class by using noun phrase Layered approach to software approach development iv. Initial list of noun phrases: candidate Business layer User interface (user) layer classes Access layer v. Reviewing redundant classes and building common vocabulary Unit 2 - UML diagram vi. Reviewing the class containing Introduction to UML adjectives UML diagrams vii. Reviewing the possible attributes 1. Class Diagram(Static) viii. Reviewing the class purpose Class Notation: Static Structure Object Diagram 2. Common class pattern approach Class Interface Diagram i. Concept class Binary association diagram ii. Event class Association Rule iii. Organization class Qualifier iv. People class v. Places class vi. Tangible things and device class 3. Usecase driven-sequence /collaboration modeling approach 4. Classes responsibilities and collaborators (CRC) approach i. CRC process ii. Via net bank ATM System – identifying class using CRC 5. Design axioms i. Theorem ii. Corollary