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.
- 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
- 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
- 34. UML Structural Diagrams Class diagram
- 35. Object diagram
- 38. Package diagram
- 40. UML Behavioral Diagrams Use case diagram
- 41. Activity diagram
- 43. UML Interactions Diagrams Sequence 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
- 52. Composition … Stronger OWNS-A
- 53. Generalization / inheritance … IS-A, IS-LIKE-A
- 55. Class Diagrams Composition is a stronger association
- 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
- 59. Component Diagrams Component diagrams show how the components of a system relate to each other
- 60. Components are at a higher level of abstraction than classes
- 61. Components usually consist of multiple classes
- 62. Component Diagrams Acknowledgement – Many thanks to Scott Ambler for giving me permission to use this diagram from his article on UML 2 Component Diagrams
- 63. Composite Structure Diagrams Composite structure diagrams show the internal structure of a class and the collaborations that are made possible
- 65. Package Diagrams Package diagrams show the organization of namespaces in a software system
- 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
- 69. Behavioral Diagrams Behavioral diagrams depict behavioral aspects of a system
- 70. Diagrams Use Case 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
- 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
- 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.
- 80. Interaction Diagrams Interaction diagrams depict the interactions in a system Sequence diagrams
- 83. Sequence Diagrams Sequence diagrams show how entities in a system interact including the messages that are passed in the order of execution
- 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.
- 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.
- 92. Summary What is a model ?
- 93. Reasons for modeling any system
- 94. UML is the unification of several modeling languages
- 95. Summary UML diagrams Structural diagrams Diagrams: class, object, component, composite structure, package, deployment diagram Behavioral diagrams Diagrams: use case, activity, state machine diagrams Interaction diagrams Diagrams: sequence, communication, interaction overview
- 96. Resources Several articles on UML by Scott Ambler - http://www.agilemodeling.com/artifacts/
- 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