UML is a modeling language used to visualize, specify, construct, and document software systems. It provides standard graphical notations for modeling structural and behavioral aspects of a system using diagrams. The key UML diagram types are structural diagrams (e.g. class, component), behavioral diagrams (e.g. use case, activity), and interaction diagrams (e.g. sequence, communication). UML was created through the unification of several popular modeling languages in the 1990s and is now managed by the Object Management Group.

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

5. Why is modeling important ? For better communication among stake holders

6. Why is modeling important ? For documenting high level design decisions

7. Why is modeling important ? For risk reduction

8. Why is modeling important ? For what-if analysis

9. Why is modeling important ? Allows re-use of design components and patterns across projects

10. Why is modeling important ? If you don't do modeling, you may have to ...

11. Different views of a system Every system can be viewed from multiple perspectives or views

12. Different views of a system

13. Different views of a system

14. Views in a software system Modules

15. Classes and their relations

16. Real time interactions

17. Data flow

18. Deployment

19. User Interface

20. … etc

21. Many modeling languages Between 1970 and late 1980's many people experimented with modeling techniques and notations

22. Some popular notations Booch

23. OMT

24. OOSE (object oriented software engineering methodology – Ivar Jacobsen) Clearly unification was required

25. Unification In 1994 Grady Booch and James Rumbaugh started unifying Booch and OMT at Rational Corporation

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

27. The unification resulted in UML 0.9 in 1996

28. UML Managed by the OMG

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

30. The notation is graphical and extensible

31. UML Diagrams Structural diagrams

32. Behavioral diagrams

33. Interaction diagrams

34. UML Structural Diagrams Class diagram

35. Object diagram

36. Component diagram

37. Composite structure diagram

38. Package diagram

39. Deployment diagram

40. UML Behavioral Diagrams Use case diagram

41. Activity diagram

42. State machine diagram

43. UML Interactions Diagrams Sequence diagrams

44. Communication diagrams

45. Interaction overview diagrams

46. UML Structural Diagrams Structural diagrams depict structural aspects (static relationships) of a system

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

49. Class Diagrams Class diagrams are also used to denote dependencies Weak dependency … USES-A

50. Association … HAS-A

51. Aggregation … OWNS-A

52. Composition … Stronger OWNS-A

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

54. Class Diagrams Associations

55. Class Diagrams Composition is a stronger association

56. Class Diagrams Inheritance

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