Chapter7

2,065 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Chapter7

  1. 1. Session 7 Dynamic Model
  2. 2. Review <ul><li>Use Cases bring out the users of the system </li></ul><ul><li>Use Case Diagrams help to define the roles of actors </li></ul><ul><li>The services and interaction between users is described using Use Case Diagrams </li></ul><ul><li>Very often these are the first diagrams to be drawn while modeling a system </li></ul>
  3. 3. Objectives <ul><li>Discuss state diagram </li></ul><ul><li>Explain sequence diagram </li></ul><ul><li>Work with collaboration diagram and activity diagram </li></ul><ul><li>Explain the definitions of dynamic diagrams in UML </li></ul>
  4. 4. Message and Message Notations <ul><li>Message is drawn as a line with an arrow between sender and receiver of the message. The arrowhead indicates the type of the message sent </li></ul>
  5. 5. State Diagram <ul><li>State diagrams are one set of diagrams which helps to draw the dynamics of a system </li></ul><ul><li>The state of an object at any point in time is the condition of the object at that instant </li></ul><ul><li>State of the object is defined by all the attributes of the object and the links maintained by it </li></ul>
  6. 6. State and Transition <ul><li>The process of change in state is called state transition </li></ul><ul><li>Transitions are typically the result of the invocation of an operation that causes an important change in state </li></ul><ul><li>An action is something, in the case of a class it is an operation, which is invoked by/on the entity being modeled </li></ul>
  7. 7. Sub-state-1 <ul><li>The state of an object can have sub-states in it </li></ul><ul><li>A sub state is a part of the composite state </li></ul><ul><li>Sub States can be concurrent or sequential </li></ul>
  8. 8. Sub-state-2
  9. 9. Use state diagram
  10. 10. Sequence Diagram <ul><li>Illustrate interaction between objects; that is the messages sent and received between the objects </li></ul><ul><li>Have two axes </li></ul><ul><li>Vertical axis shows the time, where as the horizontal axis shows a set of objects </li></ul>
  11. 11. General Sequence Diagram-1 <ul><li>Events are depicted by horizontal lines </li></ul><ul><li>Objects by Vertical Lines </li></ul><ul><li>Time is depicted vertically starting from top. This means that the events should be depicted in the order in which they occur from top to bottom. </li></ul>
  12. 12. General Sequence Diagram-2 : Customer : Interface : Vendor Input Coin Verify Coin Reject Faulty Coin with Message Send Genuine Coin Vend Tea
  13. 13. Recursion <ul><li>Repetition of the same activity again and again until a condition is met </li></ul><ul><li>While showing recursion the event arrow comes back to the same object from where it started </li></ul>
  14. 14. Use Sequence Diagram
  15. 15. Collaboration Diagram-1 <ul><li>Describes interaction between objects just like the Sequence diagram but unlike the Sequence diagram the primary focus is on events </li></ul><ul><li>Objects are shown using the Class icon </li></ul><ul><li>Sequence in Collaboration diagram is shown by numbering the messages </li></ul><ul><li>Better for understanding all the effects on a given object and for procedural design </li></ul>
  16. 16. Collaboration Diagram-2
  17. 17. Activity Diagram-1 <ul><li>To capture action (work) when the operation is executing. This is the most common usage. </li></ul><ul><li>To describe how interactions between related objects take place </li></ul><ul><li>To describe a Use-Case’s performance in terms of actions and object state changes. </li></ul><ul><li>To capture internal process of an object </li></ul><ul><li>To describe the functional flow of the system in terms of objects </li></ul>
  18. 18. Activity Diagram-2
  19. 19. Activity Diagram-3
  20. 20. Activity diagram Concurrency <ul><li>Concurrency paths run at the same time and then join below </li></ul><ul><li>The split and merge are represented as solid horizontal lines </li></ul>
  21. 21. Signal-1 Signals Indicate input and output events <ul><li>The symbol for sending a signal is a convex pentagon. </li></ul><ul><li>The symbol for receiving a signal is a concave pentagon. </li></ul>Sending a signal Receiving a signal
  22. 22. Signal-2
  23. 23. Swimlanes
  24. 24. Use Activity Diagram
  25. 25. Summary <ul><li>State diagrams depict the dynamics of a system </li></ul><ul><li>State diagrams can have concurrent or sequential sub states </li></ul><ul><li>Sequence diagrams depict the interaction amongst objects. They might contain recursion. </li></ul><ul><li>Interaction between objects is shown using Collaboration Diagram </li></ul><ul><li>Activity Diagrams capture the activities and their results </li></ul><ul><li>Swimlanes simplify the activity diagram and help in understanding the distribution of activities amongst the objects </li></ul>

×