1. Final Notes on the UML CS 123/231

2. UML Diagramming Techniques zClass Diagrams zUse Case Diagrams zInteraction Diagrams Õ Sequence diagrams ÕCollaboration diagrams zState Diagrams zOthers (e.g., Activity Diagrams, Packages)

3. Activity Diagram zRepresents sequence of activities zDepicts condition, iteration, and parallel activities zWhen to use: ÕAnalyzing use cases xAlternate way of describing a use case xDepicting use case sequences/workflow ÕDescribing method behavior

4. Activity Diagram Notation zOval - activity zStart and end buttons zLinks between ovals to depict sequence zDiamond – conditional branch and merge zBar – fork and join (concurrent activities)

5. About Activity Diagrams zHelps in understanding system behavior, but … zIt does not provide an object-oriented perspective! zSuggestion: just use as a tool to clarify complex sequential/parallel relationships between behavioral components

6. CRC Cards zNot really part of the UML ÕBut helps in construction of Class Diagrams and Interaction Diagrams zCRC: Class-Responsibility-Collaboration zRole-playing: ÕTeam members represent classes ÕEach member/class holds an index card

7. CRC Cards, continued zTeam goes through each use case and role-play object interaction zResponsibilities (which end up being methods) are noted on the index card zUse of an index card is deliberate ÕResponsibilities ought to be evenly distributed across the classes that interact ÕOverloaded classes become immediately apparent

8. CRC Cards and UML Diagrams zRole-playing activity for each use case maps directly to interaction diagram construction zEach card provide class details (methods) for the class diagram

9. Package Diagrams zRecall: Architectural Design ÕDivide a system into subsystems ÕDepicted using a block diagram zOO alternative: Package Diagrams ÕPackage Subsystem zPackage: group of classes zDependencies between packages

10. Package Diagram Notation zFolder: Package zDotted arrow between folders: dependency link zTwo variations ÕAbbreviated: name in folder ÕDetailed: name on folder tab, rectangles representing classes in folder area

11. Using the UML zUse the UML as a communication tool across the different stages of software engineering zPrimarily a design tool but helpful in analysis as well zImportant to note what stage or perspective you are in

12. Perspectives zConceptual (analysis) ÕFocus on domain and requirements ÕUse case diagram, high-level class diagram, maybe some activity diagrams zSpecification (design) ÕFocus on solution/programming details zImplementation ÕFocus on code

13. Phases in the Rational Unified Process zInception ÕFeasibility Study ÕAnalysis zElaboration ÕAnalysis ÕDesign zConstruction ÕImplementation and Testing