金陵学院软件系统分析与设计课件chap10_OOA.pptVIP

Chapter 10 Object-Oriented Analysis and Modeling Using the UML Objectives Define object modeling and explain its benefits. Recognize and understand the basic concepts and constructs of object modeling. Define the UML and its various types of diagrams. Evolve a business requirements use-case model into a system analysis use-case model. Construct an activity diagram. Discover objects and classes, and their relationships. Construct a class diagram. Introduction to Object Modeling Object-oriented analysis (OOA) – an approach used to study existing objects to see if they can be reused or adapted for new uses define new or modified objects that will be combined with existing objects into a useful business computing application Object modeling – a technique for identifying objects within the systems environment and the relationships between those objects. Introduction to the UML Unified Modeling Language (UML) – a set of modeling conventions that is used to specify or describe a software system in terms of objects. The UML does not prescribe a method for developing systems—only a notation that is now widely accepted as a standard for object modeling. Objects Attributes Object – something that is or is capable of being seen, touched, or otherwise sensed, and about which users store data and associate behavior. Person, place, thing, or event Employee, customer, instructor, student Warehouse, office, building, room Product, vehicle, computer, videotape Attribute – the data that represent characteristics of interest about an object. Objects Object Instances Object instance – each specific person, place, thing, or event, as well as the values for the attributes of that object. Behavior Encapsulation Behavior – the set of things that the object can do that correspond to functions that act on the object’s data (or attributes). In object-oriented circles, an object’s behavior is commonly referred to as a method, operation, or service. Encapsulation – the packaging