Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Unified Modeling Language [UML]
  2. 2. <ul><li>UML </li></ul><ul><li>UML diagrams </li></ul><ul><li>UML diagram classification </li></ul><ul><li>Class diagrams </li></ul><ul><li>Sequence diagrams </li></ul>agenda
  3. 3. UML <ul><li>Standard methodology language for specifying, visualizing, constructing, and documenting all the work products or artifacts of a software system. </li></ul><ul><li>the reasons behind modeling can be summed up in two words: </li></ul><ul><li>readability – ( brings clarity – ease of understanding ) </li></ul><ul><li>reusability </li></ul>
  4. 4. MODEL A model is a pattern of something to be made. It’s a representation of something in the real world.
  5. 5. UML is . . . <ul><li>NOT a method or methodology. </li></ul><ul><li>does NOT indicate a particular process. </li></ul><ul><li>NOT a programming language </li></ul>
  6. 6. UML diagrams <ul><li>use case </li></ul><ul><li>class </li></ul><ul><li>sequence </li></ul><ul><li>collaboration </li></ul><ul><li>state </li></ul><ul><li>activity </li></ul><ul><li>component </li></ul><ul><li>deployment </li></ul><ul><li>entity-relationship </li></ul>
  7. 7. UML diagram classification <ul><li>Static </li></ul><ul><li>Dynamic </li></ul><ul><li>Implementation </li></ul>
  8. 8. <ul><li>Static </li></ul><ul><li>Dynamic </li></ul><ul><li>Implementation </li></ul><ul><li>use case </li></ul><ul><li>class </li></ul><ul><li>sequence </li></ul><ul><li>collaboration </li></ul><ul><li>state </li></ul><ul><li>activity </li></ul><ul><li>deployment </li></ul><ul><li>component </li></ul>
  9. 9. use case dgms <ul><li>DESCRIBES the relationships and dependencies between a group of Use Cases and the Actors participating in the process. </li></ul><ul><li>NOT suited to represent the design, and canNOT describe the internals of a system. </li></ul><ul><li>It tells , what the system should do but do NOT — and canNOT — specify how this is to be achieved. </li></ul>
  10. 10. actor & useCase <ul><li>Actors is an external entity (outside of the system) that interacts with the system by participating (and often initiating) a Use Case. </li></ul><ul><li>Actors do NOT represent the physical people or systems, but their role. </li></ul><ul><li>UseCase descriptions explains the processes or activities that take place in the Use Case. </li></ul>
  11. 11. <ul><li>It’s related to at least one actor. </li></ul><ul><li>Has an initiator (i.e. an actor). </li></ul><ul><li>Leads to a relevant result (a result with “business value”). </li></ul>use case dgms contd . . .
  12. 12. class dgms <ul><li>Class defines the attributes and the methods of a set of objects. </li></ul><ul><li>In UML, Classes are represented by rectangles, with the name of the class, and can also show the attributes and operations of the class in two other “compartments” inside the rectangle. </li></ul>
  13. 13. <ul><li>+ for public </li></ul><ul><li># for protected </li></ul><ul><li>- for private </li></ul>
  14. 14. generalization associations aggregation composition CHAPTER BOOK 1.. * BASE DERIVED EMPLOYEE COMPANY 1 1.. * WHEEL CAR
  15. 15. sequence dgms <ul><li>Shows the message exchange (i.e. method call) between several Objects in a specific time-delimited situation. </li></ul><ul><li>Objects are represented through vertical dashed lines, with the name of the Object on the top. The time axis is also vertical, increasing downwards, so that messages are sent from one Object to another in the form of arrows with the operation and parameters name. </li></ul>
  16. 16. States dgms <ul><li>Shows the different states of an Object during its life and the stimuli that cause the Object to change its state. </li></ul>
  17. 17. activity dgms <ul><li>It describes the sequence of activities in a system with the help of Activities. Activity Diagrams are a special form of State Diagrams, that only (or mostly) contains Activities. </li></ul>
  18. 18. EA diagram classification Behavioral Structural
  19. 19. Behavioral Diagrams Portrays the behavioral features of a system or business function. <ul><li>Activity Diagrams </li></ul><ul><li>Use Case Diagrams </li></ul><ul><li>State Machine Diagrams </li></ul><ul><li>Timing Diagrams </li></ul><ul><li>Sequence Diagrams </li></ul><ul><li>Communication Diagrams </li></ul><ul><li>Interaction Overview Diagrams </li></ul>
  20. 20. Structural Diagrams Portrays the structural elements composing a system or function. <ul><li>Class Diagrams </li></ul><ul><li>Composite Structure Diagrams </li></ul><ul><li>Component Diagrams </li></ul><ul><li>Deployment Diagrams </li></ul><ul><li>Object Diagrams </li></ul><ul><li>Package Diagrams </li></ul>
  21. 21. Class diagrams
  22. 23. Sequence diagrams
  23. 25. Merci