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

Chapter 1 Players in the Systems Game Chapter 18 Object-Oriented Design and Modeling Using the UML Objectives Understand entity, interface, control, persistence, and system classes. Understand the concepts of dependency and navigability. Define visibility and explain its three levels. Understand the concept object responsibility and how it is related to message sending between object types. Describe the activities involved in object-oriented design. Differentiate between a design use-case narrative and an analysis use-case narrative. Describe CRC card modeling. Model class interactions with sequence diagrams. Construct a class diagram that reflects design specifics. Model object states with state machine diagrams. Understand the role of coupling and cohesion in object reuse. Describe the use of design patterns and two common design patterns. Differentiate between design patterns, object frameworks, and components. Understand the use of communication diagrams, component diagrams, and deployment diagrams. Object-Oriented Design Object-oriented design (OOD) – an approach used to specify the software solution in terms of collaborating objects, their attributes, and their methods. Continuation of object-oriented analysis Design Classes Types of Design Classes Entity Class - contains business related information and implements analysis classes. Interface Class - provides the means by which an actor interacts with the system. A window, dialogue box, or screen. For nonhuman actors, an application program interface (API). Control Class - contains application logic. Persistence Class - provides functionality to read and write to a database. System Class - handles operating system-specific functionality. Design Relationships - Dependency A dependency relationship is used to model the association between two classes: To indicate that when a change occurs in one class, it may affect the other class. To indicate the association between a persistent class and a transient class.