Objectives

1. 9

2. Objectives • Explain the purpose and objectives of object-oriented design • Develop design class diagrams • Develop interaction diagrams based on the principles of object responsibility and use case controllers Object-Oriented Analysis and Design and the Unified Process

3. Objectives (continued) • Develop detailed sequence diagrams as the core process in systems design • Develop communication diagrams as part of systems design • Document the architecture design using package diagrams Object-Oriented Analysis and Design and the Unified Process

4. What is Object-Oriented Design? • The bridge between a user’s requirements and programming for the new system • “Blueprints”, or design models, are necessary to build systems • An adaptive approach to development • Requirements and design are done incrementally within an iteration • A complete set of designs may not be developed at one time Object-Oriented Analysis and Design and the Unified Process

5. Object-Oriented Design Process • Create a first-cut model of the design class diagrams • Develop interaction diagrams for each use case or scenario • Update the design class diagrams • Method names, attributes, and navigation visibility • Partition the design class diagrams into related functions using package diagrams Object-Oriented Analysis and Design and the Unified Process

6. Object-oriented event-driven program flow Object-Oriented Analysis and Design and the Unified Process

7. Designing with Class Diagrams • Class name and stereotype information • Attribute information • Visibility, type-expression, name, initial value, and properties • Method signature • Visibility, name, type-expression, and parameter list • Use the entire signature to identify a method to distinguish between overloaded methods Object-Oriented Analysis and Design and the Unified Process

8. Example of class Customer http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

9. Example of class Student Object-Oriented Analysis and Design and the Unified Process

10. Class diagram with relationships http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

11. Class diagram with generalization relationship http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

12. RMO design class diagram Object-Oriented Analysis and Design and the Unified Process

13. Designing with Sequence Diagrams • An SSD captures the interactions between the system and the external world represented by actors • The system is treated like a black box • A detailed sequence diagram uses all of the same elements as an SSD • The :System object is replaced by all of the internal objects and messages within the system Object-Oriented Analysis and Design and the Unified Process

14. Designing with Sequence Diagrams (con’t) Sequence diagrams demonstrate the behavior of objects in a use case by describing the objects and the messages they pass.  The diagrams are read left to right and descending.  The example below shows an object of class 1 start the behavior by sending a message to an object of class 2.  Messages pass between the different objects until the object of class 1 receives the final message. http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

15. Designing with Sequence Diagrams (con’t) The object an Order Entry Window is created and sends a message to an Order object to prepare the order. Next the Order object checks to see if the item is in stock and if the [InStock] condition is met it sends a message to create an new Delivery Item object. If the item is [OutOfStock] it sends a message back to the Order Entry Window object stating that the object is out of stack.   http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

16. Designing with Communication Diagrams • Shows a view of the use case that emphasizes coupling • Uses the same symbols as a sequence diagram for actors, objects, and messages • Lifeline symbols are not used • Link symbols indicate that two items share a message • Numbers indicate the sequence in which messages are sent Object-Oriented Analysis and Design and the Unified Process

17. Designing with Communication Diagrams (con’t) http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

18. Designing with Communication Diagrams (con’t) The example below shows a simple collaboration diagram for the placing an order use case.  This time the class name is shown to demonstrate that all of objects of that class will behave the same way. http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm Object-Oriented Analysis and Design and the Unified Process

19. A communication diagram for Create new order Object-Oriented Analysis and Design and the Unified Process

20. Package Diagrams-Structuring the Major Components • Associates classes of related groups • One option is to separate the view, domain, and data access layers into separate packages • Indicate dependency relationships • Shows which elements affect other elements in a system • May exist between packages, or between classes within packages • Packages can be nested Object-Oriented Analysis and Design and the Unified Process

21. Partial design for a three-layer package diagram for RMO Object-Oriented Analysis and Design and the Unified Process

22. Summary • Design is driven by use cases • Two primary models developed during design • Design class diagrams • Sequence class diagrams • Communication diagrams are a viable alternative to sequence diagrams Object-Oriented Analysis and Design and the Unified Process