Introduction to Unified Modeling Language (UML)

1. Unified Modeling Language UML Parag Shah Twitter: @coding_insights

2. Modeling Most manufacturing and building processes require the creation of a model before the actual product is created.

3. Models in architecture

4. Automobile models

12. Different views of a system

13. Different views of a system

15. Classes and their relations

16. Real time interactions

17. Data flow

18. Deployment

19. User Interface

20. … etc

23. OMT

26. In 1995 Ivar Jacobsen joined them and started merging OOSE

27. The unification resulted in UML 0.9 in 1996

29. Set of rules and notations for specifying a software system

30. The notation is graphical and extensible

32. Behavioral diagrams

33. Interaction diagrams

35. Object diagram

36. Component diagram

37. Composite structure diagram

38. Package diagram

39. Deployment diagram

41. Activity diagram

42. State machine diagram

44. Communication diagrams

45. Interaction overview diagrams

47. Class Diagrams Class diagrams represent the static structure of the classes in the software system, and illustrate attributes, operations, and relationships between the classes.

48. Class Diagrams – A class Person - name: String - age: int + toString: String Name Attributes Operations

50. Association … HAS-A

51. Aggregation … OWNS-A

52. Composition … Stronger OWNS-A

53. Generalization / inheritance … IS-A, IS-LIKE-A

57. Object Diagrams Object diagrams provide information about the relationships between instances of classes at a particular point in time.

58. Object Diagrams org1:Organization emp1:Employee + Id: 200010

60. Components are at a higher level of abstraction than classes

61. Components usually consist of multiple classes

64. Composite Structure Diagrams

66. Package diagrams show us how the software system is divided into packages and the dependencies among them

67. Package diagrams can show us a very high level view of components, layers, and dependencies in a software system

68. Package Diagrams Source: http://en.wikipedia.org/wiki/File:Package_Diagram.PNG

71. Activity Diagrams

72. State Machine Diagrams

73. Use Case Diagrams Use case diagrams show the interactions of users and external entities with the system being created. They are very good for depicting high level requirements of a system.

74. Use Case Diagrams Actor Use Case Boundary LogIn

75. Use Case Diagrams

76. Use Case Diagrams Use cases can also extend and include other use cases

77. Activity Diagrams Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. - Wikipedia

78. Activity Diagrams

79. State Machine Diagrams State machine diagrams are used to depict the state transitions of a single object in response to events. They are modeled in a similar way as activity diagrams.

81. Communication diagrams

82. Interaction overview diagrams

84. Sequence Diagrams - Entities Actor – represents external entities in the system. They could be human or external systems. General lifeline, represents an individual entity Entity, represents beans, and other objects that hold data or information. Boundary element, represents elements at the boundary of a system, such as UI elements or backend logic which deals with external systems. Control element, manages the flow of control for a scenario.

85. Sequence Diagrams - Messages Synchronous message Asynchronous message Self message

86. Sequence Diagram - Fragments Fragments are sections of logic which are executed given a particular condition.

87. Sequence Diagram

88. Communication Diagrams Communication diagrams (aka collaboration diagram) are similar to sequence diagrams, but they do not have lifelines, and are more free form in nature. The focus is usually object relationships between boundary, control, and entity types.

89. Communication Diagrams

90. Interaction Overview Diagrams Interaction overview diagram is a special type of activity diagram, where each node is a link to another type of interaction diagram.

91. Interaction Overview Diagrams

93. Reasons for modeling any system

94. UML is the unification of several modeling languages

97. UML quick reference by Allen Holub - http://www.holub.com/goodies/uml/

98. Cetus links on UML - http://www.cetus-links.org/oo_uml.html