1. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 1 UML unified modeling language 1994 first attempts - largely theoretical 1997 UML becomes an industry standard... ongoing evolution and efforts to standardize 2005 Nov.Dec. version 2.0 2007 Aug. version 2.1 general-purpose visual modeling language can be used from requirements engineering to implementation for real-time embedded systems, management decision support systems, high user interaction systems... language and platform neutral but excellent support for O-O languages (Smalltalk, Java, Python...) can be used with any SDLC methodology

2. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 2 diagrams : classclasses, interfaces, relationships, collaboration objectinstances of things found in class diagrams use casemodeling the behaviors of a system sequencetime-ordering of messages collaborationstructural organization of objects aka communication state chartevent-ordered behaviour of objects aka state machine activityflow of control between objects componentimplementation view deploymentrun-time processing interaction overview of activity diagrams timingbased on state chart diagrams composite structure depict internal structures packageoverview of class and other diagrams UML unified modeling language

3. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 3 functional requirements view from users' point of view dynamic behaviour view collaboration among objects and changes to internal states of objects static structural view objects, attributes, operations and relationships http://en.wikipedia.org/wiki/Unified_Modeling_Language

4. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 4 basic premise of UML we can model software and other systems as collections of collaborating objects class diagram component diagram deployment diagram object diagram activity diagram state chart diagram collaboration diagram sequence diagram use case diagram static model showing system structure dynamic model showing system behaviour Arlow, Neustadt. UML and the Unified Process: Practical Object-Oriented analsis and Design. Addison Wesley. 2002. fig. 1.6 adaptated

5. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 5 design view process view deployment view implementation view use case view vocabulary functionality behavior performance scalability throughput system assembly configuration management system topology distribution delivery installation modeling a system’s architecture Booch, Jacobson, Rumbaugh. The Unified Modeling Language User Guide. Addison Wesley. 1999. fig. 2-20

6. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 6 collaboration objects work together in order to provide the system functionality communication objects collaborate by sending messages to other objects requesting the others to perform operations association objects have to know about other objects in order to send these messages responsibility objects only contain data and methods relevant to their own responsibilities some concepts

7. University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 UML 7 an object's operations can only be called by a message with a valid operation signature other objects send messages requesting services an object's data can only be accessed by it's own operations the representation of an object's data is hidden inside encapsulation