Chapter7

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Chapter7 - Presentation Transcript

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

    + ohiseeohisee, 2 years ago

    custom

    173 views, 0 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 173
      • 173 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 4
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories