The document discusses various aspects of the design phase of software development including: 1. The design phase builds upon artifacts created in the analysis phase like use cases and conceptual models. Interaction diagrams are created to show how objects communicate and collaborate. 2. Real use cases describe detailed interface designs. Class diagrams summarize class definitions and relationships. Responsibilities are assigned to classes using patterns like expert, controller, and others. 3. Interaction diagrams illustrate object interactions and are dependent on prior artifacts. Collaboration and sequence diagrams represent different notation for the same interactions. Guidelines are provided for creating interaction diagrams.

1. DESIGN PHASE Objectives Motivate the transition from analysis to design.

3. Design Phase Initiation Interaction Diagram Shows communication of objects Requires greatest principles of assigning responsibility and use of design patterns Real Usecases Class Diagram Summarizes definition of class implemented in software Describes concrete input and output technologies

5. Real Buy Items Use Case

9. Sequence diagram Illustrate interaction in a kind of fence format as shown Collaboration diagram Illustrate object interaction in a graphical or network format Interaction Diagrams

10. Example: Collaboration Diagram : POST 1:enterItem(upc,quantity)

13. Pictorial representation between artifacts: Interaction Diagram Buy Item

17. Illustrating Messages 1. Messages between objects are represented via a labeled arrow on a link line. 2. Any number of messages may flow along this link 3. A sequence number is added to show the sequential order of messages in the current thread of control .

19. Illustrating Iteration Iteration is indicated by following the sequence number with a star(‘*’). This expresses that the message is being sent repeatedly, in a loop, to the receiver For Example: In case of Departmental Stores to show different salelineitem added to the sale which is created by Sale Terminal.

20. Iteration clause To express more than one message happening within the same iteration clause (for example, a set of messages within a for loop), repeat the iteration clause on each message Multiple messages within the same iteration clause.

22. Illustrating Message Number Sequencing Sequence numbering

23. Illustrating Conditional Messages Conditional message

26. Illustrating Messages to Multiobjects A message to a multiobject icon indicates that is sent to the collection object itself. For example, in Figure the size message is being sent to a java.util.Vector instance in order to query the number of elements in the Vector. In the UML 1.1, messages to a multiobject are not broadcast to each element

27. Illustrating Messages to Class Object Messages to class object ( static method invocation ) 1:sd1:=getSaleDate():Date Sale

28. Basics of Pattern

38. Basic PATTERNS FOR ASSIGNING RESPONSIBILITIES GRASP: General Responsibility Assignment Software Patterns P

59. Violation of Don’t Talk to Stranger Don’t Talk To Stranger Example: POST

60. DETERMINING VISIBILITY

63. Example: Collaboration Diagram : POST 1:enterItem(upc,quantity)

64. DESIGN CLASS DIAGRAMS

70. Class Diagram - POST : <<parameter>> << local >>

71. OOAD Summary

72. OOAD Summary………

73. OOAD Summary………

74. A New Begining