UML

1. UML The Unified Modeling Language

2. Brief Summary of UML(The Unified Modeling Language) • The UML is a language for • visualizing • specifying • constructing • Documenting • It is used to understand, design, browse, configure, maintain, and control information about systems. • The UML uses mostly graphical notations to express the OO analysis and design of software projects.  • Simplifies the complex process of software design

3. Object Oriented Modeling

4. Goals of UML • Provides a common language for describing both components and architectures • Supports language-independent analysis and design • Provides a common method for developing both information systems and technical applications • Enables seamless transition from analysis to design to implementation • Scales from small to large projects • Facilitates iterative development

5. UML Assessment • UML is messy, imprecise, complex. • You don’t have to know or use every feature of UML any more than you need to know or use every feature of a large software application or programming language. • UML can be and has been used in many different ways in real-world development projects. • UML is more than a visual notation. UML models can be used to generate code and test cases.

6. Model: • Models are the language of designer, in many disciplines • Models are representations of the system to-be-built or as-built • Models are vehicle for communications with various stakeholders • Models allow reasoning about some characteristic of the real system

7. Types of UML Diagrams • Use Case Diagram • Class Diagram • Sequence Diagram • Collaboration Diagram • State Diagram • Activity Diagram • Interaction Diagram • Deployment Diagram • Component Diagram This is only a subset of diagrams … but are most widely used

8. Use Case Diagram • Used for describing a set of user scenarios • Mainly used for capturing user requirements • Work like a contract between end user and software developers

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 describing an interaction between a user and a system, including alternatives. 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 a special use case (used for defining special alternatives) 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 insertion of additional behavior into a base use case that explicitly describes the insertion <<include>> Extend: a dotted line labeled <<extend>> with an arrow toward the base case.The insertion of additional behavior into a base use case that does not know about it. 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 diagram • A class is a collection of objects with common structure, common behavior, common relationships and common semantics • Classes are found by examining the objects in sequence and collaboration diagram • A class is drawn as a rectangle with three compartments • Classes should be named using the vocabulary of the domain • Naming standards should be created • e.g., all classes are singular nouns starting with a capital letter • Detailed class diagrams are used for developers

16. Class representation • 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.

17. Name Account_Name - Customer_Name - Balance Attributes +addFunds( ) #withDraw( ) +transfer( ) Operations An example of Class

18. OO Relationships • There are two kinds of Relationships • Generalization (parent-child relationship) • Association (student enrolls in course) • Associations can be further classified as • Aggregation • Composition

19. OO Relationships:Generalization Supertype Example: Customer Regular Customer Loyalty Customer Subtype2 Subtype1 or: Customer - Generalization expresses a parent/child relationship among related classes. - Used for abstracting details in several layers Regular Customer Loyalty Customer

20. OO Relationships: Association • Represent relationship between instances of classes • Student enrolls in a course • Courses have students • Courses have exams • Etc. • Association has two ends • Role names (e.g. enrolls) • Multiplicity (e.g. One course can have many students) • Navigability (unidirectional, bidirectional)

21. Association: Multiplicity and Roles student 1 * University Person 0..1 * teacher employer Role 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 “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.”

22. 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) 0..1 Multiplicity: optional * Employee * OrderLine -quantity: Integer 1 * Product -price: Money -isSatisfied: Boolean [from UML Distilled Third Edition]

23. Association: Model to Implementation * 4 Course Student Class Student { Course enrolls[4]; } Class Course { Student have[]; } has enrolls

24. Automobile Transmission Engine OO Relationships:Composition Composition: expresses a relationship among instances of related classes. It is a specific kind of Whole-Partrelationship. Whole Class Class W ClassP2 ClassP1 Part Classes Example

25. OO Relationships: Aggregation Container Class ClassC Aggregation: expresses a relationship among instances of related classes. It is a specific kind of Container-Containee relationship. AGGREGATION Class E2 Class E1 Containee Classes Example Bag Milk Apples

26. 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.

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

28. Sequence Diagram:Object interaction A sequence diagram displays an interaction as a two-dimensional chart. The vertical dimension is the time axis; time proceeds down the page. The horizontal dimension shows the roles that represent individual objects in the collaboration.Each role is represented by a vertical column containing a head symbol and a vertical line—a lifeline. A B Synchronous Asynchronous Self-Call: A message that an Object sends to itself. Condition: indicates when a message is sent. The message is sent only if the condition is true. Condition [condition] remove() Iteration *[for each] remove() Self-Call

29. 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

30. 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.

31. 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.

32. 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

33. State Diagrams(Traffic light example) Start Traffic Light State Red Transition Yellow timer expires Yellow Red timer expiers Green timer expires Green Event

34. Activity Diagram

35. Activity Diagram • Built during analysis and design • Purpose • Model business workflows • Model operations • Developed by analysts, designers and implementers

36. The Physical Model • The component diagram shows the relationship between software components, their dependencies, communication, location and other conditions. • A deployment diagram illustrates the physical deployment of the system into a production (or test) environment. It shows where components will be located, on what servers, machines or hardware. It may illustrate network links, LAN bandwidth & etc.

37. The Physical Model This diagram shows the relationships among software and hardware components involved in real estate transactions.

38. Component Diagram • Captures the physical structure of the implementation • Built as part of architectural specification • Purpose • Organize source code • Construct an executable release • Specify a physical database • Developed by architects and programmers

39. Deployment Diagram • Captures the topology of a system’s hardware • Built as part of architectural specification • Purpose • Specify the distribution of components • Identify performance bottlenecks • Developed by architects, networking engineers, and system engineers

40. Classes, interfaces, collaborations Components Use cases Use Case View Activity, Active classes Nodes Organization Package, subsystem Dynamics Interaction, State machine Architecture and the UML DesignView Implementation View Process View Deployment View