DesigningwithInteractionandDesignClassDiagrams.pptVIP

Designing with Interaction and Design Class Diagrams Chapters 15 16 Applying UML and Patterns Craig Larman Two kinds of UML Interaction Diagrams Sequence Diagrams: show object interactions arranged in time sequence, vertically Communication Diagrams: show object interactions arranged as a flow of objects and their links to each other, numerically Semantically equivalent, structurally different Sequence diagram emphasize time ordering Communication diagrams make object linkages explicit Interaction Diagram notation Sequence diagram notation What does vertical placement communicate? Communication Diagram: makePayment Control logic in Interaction Diagrams Conditional Message [ variable = value ] : message() Message is sent only if clause evaluates to true Iteration (Looping) * [ i := 1..N ]: message() “*” is required; [ ... ] clause is optional Communication diagrams add Seq. Numbers before conditional messages or loops Logic in sequence diagrams:which notation do you prefer? Logic in communication diagrams Loops in sequence diagrams:which notation do you prefer? Iteration in communication diagrams Asynchronous calls Polymorphism:How is it shown in interaction diagrams? Chapter 16 Design Class Diagrams (DCDs) During analysis, emphasize domain concepts During design, shift to software artifacts UML has no explicit notation for DCDs Uniform UML notation supports smoother development from analysis to design Domain model vs. Design Class Diagram – differences? Developing a Domain Class Diagram:the NextGen POS DCD 1) Identify software classes: Register Sale  ProductCatalog ProductSpecification  Store SalesLineItem  Payment 2) Begin drawing a class diagram 3) Include the attributes from the domain model How to show attribute collections? 4) Add method names —from interaction diagrams —model class interaction diagrams in parallel Parameters, return types optional?—readability vs. code generation Method body pseudo-code also optional 5)