1. UML 2-OMG certification course (OCUP Fundamental-4) Instructor: M.C. Ricardo Quintero

6. Simple example of a sequence diagram sd Identify Authorized Person log() ok:Boolean Lifelines Only 1 interaction Local attribute

7. The lifeline metamodel

10. Lifelines & set types res[2]:BookingList :BookingList :Booking A set type Using a selector to select one element from a set type Multiobjects 1.x not permited

12. The metamodel for event occurrences

13. Notation forms for various message types S T asynchronous call(syncronous) reply lost message found message U new

17. The metamodel for messages

20. Example of sequences-valid sequences Interaction Example S T p r p! p* q! r* r! q Secuencias válidas de interacción: <p!,p*,q!,r!, r*, q*> <p!, r!, p*, q!, r*, q*>

23. Adding a GeneralOrdering relationship to the example Interaction Example S T p r p! p* q! r* r! q Provoca que la secuencia ahora sea inválida, porque el evento r! tiene que ocurrir antes que p* <p!,p*,q!,r!, r*, q*>

25. The metamodel for interactions

26. State Invariants on a lifeline S State X {self.list->size().notEmpty()} {self.listA->size()> self.listB->size()}

31. Example of a communication diagram Interaction System start :System :Subsystem2 :SubSystem1 2:initialize() 1:initialize()

33. Example of a timing diagram

35. Example of an interaction overview diagram

39. Example of use case diagram

40. The metamodel for use cases and actors

43. Notation for actors <<actor>> Actor External System The block (in the right) is not a UML symbol, is a user-specific symbol.

46. Several notations for use cases Use case Use case Use case Extension points Standard notation Using the name underneath the ellipse As a behaviored classifier. This representation is suitable, i.e., when a large number of extension points have to be defined

47. Representing the system underlying a use case <<subsystem>> Booking System Agent Book vechicle Cancel booking It is a component with the stereotype <<subsystem>>

48. A use case belonging to a classifier <<subsystem>> Booking System Book vechicle Cancel booking A use case can belong to a classifier, by a special Classifier model element enhanced by the property to own use cases

51. The metamodel for use cases and actors (again...)

53. Include relationship Pay out cash Identify authorized person <<include>> Pay out cash 1.Include:Identify authorized person 2.Determine pay-out amount 3. Check pay-out possibility 4. Pay out cash Identify authorized person 1. Read customer card 2. Check card lock 3. Ask for PIN 4. Check PIN

54. Extend relationship A extension points P B <<extend>> Condition:{boolean expression} extension point: p Use case A is extended by use case B at the extension point P under certain condition. If no condition is specified, then the extension will allways occur. It is not necessary that an actor be connected to the extended use case

55. Example of use case diagram with use case relationships Can you specify the kind of relationships (include or extend) of the dashed arrows?