Introduction to UML

1. Introduction to UML Mohammad Zubair Ahmad Summer 2007

2. Acknowledgements • Most of the lecture slides were adopted from the slides of Mr. Shiyuan Jin’s UML class, EEL 5881, Fall 2003.

3. Overview • What is UML? • A brief history of UML and its origins. • Understanding the basics of UML. • UML diagrams • UML Modeling tools

4. What is UML? • The Unified Modeling Language (UML) is a industry-standard graphical language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling. • The UML uses mostly graphical notations to express the OO analysis and design of software projects.  • Simplifies the complex process of software design

5. Why UML for Modeling • Use graphical notation to communicate more clearly than natural language (imprecise) and code(too detailed). • Help acquire an overall view of a system. • UML is not dependent on any one language or technology. • UML moves us from fragmentationto standardization.

6. Year Version 2003: UML 2.0 2001: UML 1.4 1999: UML 1.3 1997: UML 1.0, 1.1 1996: UML 0.9 & 0.91 1995: Unified Method 0.8 OMT - 2 Booch ‘93 Other methods Booch ‘91 OMT - 1 History Time

7. Types of UML Diagrams Use Case Diagram: Displays the relationship among actors and use cases.  Class Diagram: Describe the types of objects in the system and various kinds of static relationship that exist among them. Sequence Diagram: Displays the time sequence of the objects participating in the interaction.

8. Types of UML Diagrams Collaboration Diagram Displays an interaction organized around the objects and their links to one another. State Diagram Displays the sequences of states that an object of an interaction goes through during its life in response to received stimuli, together with its responses and actions.

9. Use Case Diagram(core components) Actors:A role that a user plays with respect to the system,including human users and other systems. e.g.,inanimate physical objects (e.g. robot); an external system that needs some information from the current system. Use case: A set of scenarios that describe an interaction between a user and a system. System boundary: rectangle diagram representing the boundary between the actors and the system.

10. Use Case Diagram(core relationship) Association: communication between an actor and a use case; Represented by a solid line. Generalization: relationship between one general use case and one specific use case. Represented by a line with a triangular arrow head toward the parent use case.

11. Use Case Diagram(core relationship) Include: a dotted line labeled <<include>> beginning at base use case and ending with an arrows pointing to the include use case. The include relationship occurs when a chunk of behavior is similar across more than one use case. Use “include” in stead of copying the description of that behavior. <<include>> Extend: a dotted line labeled <<extend>> with an arrow toward the base case.The extending use case may add behavior to the base use case. The base class declares “extension points”. <<extend>>

12. Use Case Diagrams Use Case Boundary Actor Library System Borrow Employee Client Order Title Fine Remittance Supervisor •  A generalized description of how a system will be used.  •  Provides an overview of the intended functionality of the system

13. Use Case Diagrams(cont.) (TogetherSoft, Inc)

14. Use Case Diagrams(cont.) • Pay Bill is a parent use case and Bill Insurance is the child use case. (generalization) • Both Make Appointment and Request Medication include Check Patient Record as a subtask.(include) • The extension point is written inside the base case • Pay bill; the extending class Defer payment adds the behavior of this extension point. (extend)

15. Class • Each class is represented by a rectangle subdivided into three compartments • Name • Attributes • Operations • Modifiers are used to indicate visibility of attributes and operations. • ‘+’ is used to denote Public visibility (everyone) • ‘#’ is used to denote Protected visibility (friends and derived) • ‘-’ is used to denote Private visibility (no one) • By default, attributes are hidden and operations are visible. • The last two compartments may be omitted to simplify the class diagrams

16. Name Account_Name - Custom_Name - Balance Attributes +AddFunds( ) +WithDraw( ) +Transfer( ) Operations An example of Class

17. Multiplicity and Roles student 1 * University Person 0..1 * teacher employer Multiplicity Symbol Meaning 1 One and only one 0..1 Zero or one M..N From M to N (natural language) * From zero to any positive integer 0..* From zero to any positive integer 1..* From one to any positive integer Role Role “A given university groups many people; some act as students, others as teachers. A given student belongs to a single university; a given teacher may or may not be working for the university at a particular time.”

18. Class Diagram class Name Order Multiplicity: mandatory -dateReceived Attributes * Customer -isPrepaid 1 -number :String -name -price : Money -address Association +dispatch() Operations +creditRating() : String() +close() 1 Generalization {if Order.customer.creditRating is "poor", then Order.isPrepaid must be true } Corporate Customer Personal Customer -contactName -creditCard# Constraint (inside braces{}} -creditRating -creditLimit Multiplicity: Many value +remind() +billForMonth(Integer) * Multiplicity: optional 0..1 Employee * OrderLine -quantity: Integer 1 * Product -price: Money -isSatisfied: Boolean [from UML Distilled Third Edition]

19. OO Relationships:Generalization Supertype Example: Customer Regular Customer Loyalty Customer Subtype2 Subtype1 or: Customer Generalization expresses a relationship among related classes. It is a class that includes its subclasses. Regular Customer Loyalty Customer

20. Automobile Transmission Engine OO Relationships: Composition COMPOSITION Composition: expresses a relationship among instances of related classes. It is a specific kind of Whole-Part relationship. It expresses a relationship where an instance of the Whole-class has the responsibility to create and initialize instances of each Part-class. It may also be used to express a relationship where instancesof the Part-classes have privileged access or visibility tocertain attributes and/or behaviors defined by theWhole-class. Composition should also be used to express relationship whereinstances of the Whole-class have exclusive access to and control of instances of the Part-classes. Composition should be used to express a relationship wherethe behavior of Part instances is undefined without beingrelated to an instance of the Whole. And, conversely, the behavior of the Whole is ill-defined or incomplete if one or more of the Part instances are undefined. Whole Class Class W ClassP2 ClassP1 Part Classes Example [From Dr.David A. Workman]

21. OO Relationships: Aggregation Container Class ClassC Aggregation: expresses a relationship among instances of related classes. It is a specific kind of Container-Containee relationship. It expresses a relationship where an instance of the Container-class has the responsibility to hold and maintaininstances of each Containee-class that have been createdoutside the auspices of the Container-class. Aggregation should be used to express a more informalrelationship than composition expresses. That is, it is anappropriate relationship where the Container and its Containees can be manipulated independently. Aggregation is appropriate when Container and Containeeshave no special access privileges to each other. AGGREGATION Class E2 Class E1 Containee Classes Example Bag Milk Apples [From Dr.David A. Workman]

22. Aggregation vs. Composition • Composition is really a strong form of aggregation • components have only one owner • components cannot exist independent of their owner • components live or die with their owner • e.g. Each car has an engine that can not be shared with other cars. • Aggregations may form "part of" the aggregate, but may not be essential to it. They may also exist independent of the aggregate. • e.g. Apples may exist independent of the bag.

23. Sequence Diagram(make a call) Caller Phone Recipient Picks up Dial tone Dial Ring notification Ring Picks up Hello

24. A Create B X Return Deletion Lifeline Sequence Diagrams – Object Life Spans • Creation • Create message • Object life starts at that point • Activation • Symbolized by rectangular stripes • Place on the lifeline where object is activated. • Rectangle also denotes when object is deactivated. • Deletion • Placing an ‘X’ on lifeline • Object’s life ends at that point Activation bar

25. Sequence Diagram Message • Sequence diagrams demonstrate the behavior of objects in a use case by describing the objects and the messages they pass. • The horizontal dimension shows the objects participating in the interaction. • The vertical arrangement of messages indicates their order. • The labels may contain the seq. # to indicate concurrency.

26. Interaction Diagrams: Collaboration diagrams start 6: remove reservation 3 : [not available] reserve title User Reservations 5: title available 6 : borrow title 1: look up 2: title data 4 : title returned Catalog 5 : hold title • Shows the relationship between objects and the order of messages passed between them.  between them. • The objects are listed as rectangles and arrows indicate the messages being passed • The numbers next to the messages are called sequence numbers. They show the sequence of the messages as they are passed between the objects.  • convey the same information as sequence diagrams, but focus on object roles instead of the time sequence.

27. State Diagrams(Billing Example) State Diagrams show the sequences of states an object goes through during its life cycle in response to stimuli, together with its responses and actions; an abstraction of all possible behaviors. End Start Unpaid Paid Invoice created paying Invoice destroying

28. State Diagrams(Traffic light example) Start Traffic Light State Red Transition Yellow timer expires Yellow Car trips sensor Green timer expires Green Event

29. UML Modeling Tools • Rational Rose (www.rational.com) by IBM • UML Studio 7.1 ( http://www.pragsoft.com/) by Pragsoft Corporation Capable of handling very large models (tens of thousands of classes). Educational License US$ 125.00; Freeware version. • TogetherSoft Control Center; TogetherSoft Solo (http://www.borland.com/together/index.html) by Borland • ArgoUML (free software)(http://www.apple.com/downloads/macosx/development_tools/argouml.html ) OpenSource; written in java • Others (http://www.objectsbydesign.com/tools/umltools_byCompany.html )

30. UML studio 7.1

31. Reference 1. UML Distilled: A Brief Guide to the Standard Object Modeling LanguageMartin Fowler, Kendall Scott 2. Practical UML --- A Hands-On Introduction for Developers http://www.togethersoft.com/services/practical_guides/umlonlinecourse/ 3. OO Concepts in UML. Dr. David A. Workman, School of EE and CS. UCF. 4.Software Engineering Principles and Practice. Second Edition; Hans van Vliet.