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

4. Examples of data types Data type keywords Attributes Enumeration literals

5. The metamodel of data types

8. Overview of the UML diagrams

10. Basic notation for diagrams Diagram area Diagram header [<Diagram type>]<Name>[<Parameter>]

11. Example of a use case diagram Use case Booking use cases

17. Graphical symbols

18. UML standard stereotypes Serves to trace of requirements Abstraction <<trace>> A refinement relationship (e.g. Between a desing element and a pertaining analysis element) Abstraction <<refine>> The source element can, for instance, be derived from the target element by a calculation Abstraction <<derive>> The source element is an operation and the target element is a signal sent by that operation Dependency (usage) <<send>> The source element is responsible for the target element Dependency(usage) <<responsability>> The source element creates instances of the target element Note: This description is identical to the one of <<create>> Dependency(usage) <<instantiate>> The source element creates instances of the target element Dependency(usage) <<create>> Call dependency between operation or classes Dependency(usage) <<call>> Description UML element Stereotype

19. UML standard stereotypes An organizational motivated component Component <<buildComponent>> Utility class are collections of global variables and functions, which are grouped into a class, where they are defined as class attributes/operations Class <<utility>> Types define a set of operations and attributes, and they are generally abstract Class <<type>> A class with instances that are, in turn, classes Class <<metaclass>> An implementation class specially designed for a programming language, where an object may belong to one class only Class <<implementationClass>> Classes contain the primary logic. See <<auxiliary>> Class <<focus>> Classes that support other classes (<<focus>>) Class <<auxiliary>> A script file (can be executed on a computer) Artifact <<script>> Description UML element Stereotype

20. UML standard stereotypes A property that destroys instances of the class to which it belongs (e.g. Destructor) Behavioral feature <<destroy>> A property that creates instances of the class to which it belongs (e.g. Constructor) Behavioral feature <<create>> A package that contains model elements, which are reused in other packages Package <<modelLibrary>> A package that contains Framework elements Package <<framework>> A component that contains only implementation, not specification Component <<implement>> Description UML element Stereotype

24. The basic UML class There is no notation for an element because you would never user the element construct in UML models. The class is abstract.

26. The basic Relationship class

28. Directed relationships Note that we are dealing only with abstract and rather simple concepts.

30. The notation for comments

31. The basic metamodel concepts

33. The metamodel for NamedElement We are focusing in this section of the metamodel

35. Nested namespaces Qualified name Customers::CorporateCustomers:Insurance

39. The metamodel for NamedElement We are focusing in this section of the metamodel

40. Example of element and package import relationships <<import>> <<import>> <<access>> <<access>> BankAccount

44. Example – typed element & type Typed element Type

45. Typed elements metamodel Type and typed element are abstract classes. They have no properties

48. Example Multipicity & Cardinality Class model :Kunde r2:Bookings r2:Bookings r2:Bookings Object model Multiplicity=0..* Cardinality=3

51. The multiplicity metamodel

56. Example :Expression symbol=“+” op1:LiteralInteger value=1 op2:LiteralInteger value=1 operand operand Object Model for 1+1

57. The metamodel for value specifications