Lecture 16Object Oriented Modeling Methods.ppt

Lecture 16:Object Oriented Modeling Methods Basics of Object Oriented Analysis Notations used Modeling Process Variants Coad-Yourdon Shlaer-Mellor Fusion UML Advantages and Disadvantages Object Oriented Analysis Background Model the requirements in terms of objects and the services they provide Grew out of object oriented design partitions the problem in a different way from structured approaches Poor fit moving from Structured Analysis to Object Oriented Design Motivation OOA is (claimed to be) more ‘natural’ As a system evolves, the functions (processes) it performs tend to change, but the objects tend to remain unchanged… …so a structured analysis model will get out of date, but an object oriented model will not… …hence the claim that object-oriented systems are more maintainable OOA emphasizes importance of well-defined interfaces between objects compared to ambiguities of dataflow relationships NOTE: OO applies to requirements engineering because it is a modeling tool. But in RE we are modeling domain objects, not the design of the new system Modeling primitives Objects an entity that has state, attributes and services Interested in problem-domain objects for requirements analysis Classes Provide a way of grouping objects with similar attributes or services Classes form an abstraction hierarchy though ‘is_a’ relationships Attributes Together represent an object’s state May specify type, visibility and modifiability of each attribute Relationships ‘is_a’ classification relations ‘part_of’ assembly relationships ‘associations’ between classes Methods (services, functions) These are the operations that all objects in a class can do… …when called on to do so by other objects E.g. Constructors/Destructors (if objects are created dynamically) E.g. Set/Get (access to the object’s state) Message Passing How objects invoke services of other objects Use Cases/Scenarios Sequences of message passing between objects Represent specific interactions Key Principles Classifi