Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 39 views

    Week 14 Timing Diagram

    Uploaded by

    Neha
    This document discusses timing diagrams, which show the interaction of objects and state changes over time. It outlines the basic elements of timing diagrams including lifelines, states, events, messages, durations, and constraints. Examples are provided to illustrate how timing diagrams can be used to represent scenarios involving resources shared by objects, different object priorities, and modeling the stages of a disease. Timing diagrams are useful for reasoning about time-based behavior and interactions between systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Week 14 Timing Diagram

    Uploaded by

    Neha
    39 views30 pages
    This document discusses timing diagrams, which show the interaction of objects and state changes over time. It outlines the basic elements of timing diagrams including lifelines, states, events, messages, durations, and constraints. Examples are provided to illustrate how timing diagrams can be used to represent scenarios involving resources shared by objects, different object priorities, and modeling the stages of a disease. Timing diagrams are useful for reasoning about time-based behavior and interactions between systems.

    Original Title

    Week 14 timing diagram

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses timing diagrams, which show the interaction of objects and state changes over time. It outlines the basic elements of timing diagrams including lifelines, states, events, messages, durations, and constraints. Examples are provided to illustrate how timing diagrams can be used to represent scenarios involving resources shared by objects, different object priorities, and modeling the stages of a disease. Timing diagrams are useful for reasoning about time-based behavior and interactions between systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    39 views30 pages

    Week 14 Timing Diagram

    Uploaded by

    Neha
    This document discusses timing diagrams, which show the interaction of objects and state changes over time. It outlines the basic elements of timing diagrams including lifelines, states, events, messages, durations, and constraints. Examples are provided to illustrate how timing diagrams can be used to represent scenarios involving resources shared by objects, different object priorities, and modeling the stages of a disease. Timing diagrams are useful for reasoning about time-based behavior and interactions between systems.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 30

    Software Design and

    Timing Diagram Analysis


    CS-324

    Lecture # 35,36
    30 Nov, 2 Dec

    Rubab Jaffar
    rubab.jaffar@nu.edu.pk
    Today’s Outline
    • Interaction Diagram
    o Timing Diagram

    • Elements of Timing Diagram


    • Timing Diagram Notations
    • Examples

    SDA 2
    Timing Diagrams
    • A timing diagram allows you to show the interaction of
    objects and changes in state for those objects along a
    time axis.
    • A timing diagram provides a convenient way to show
    active objects and their state changes during their
    interactions with other active objects and system
    resources.
    • The X-axis of the timing diagram has the time units, while
    the Y-axis shows the objects and their states.
    • Timing diagrams describe behavior of both
    individual classifiers & interactions of classifiers, focusing
    attention on time of events causing changes in the
    modeled conditions of the lifelines.

    SDA 3
    Timing Diagram Elements
    • Timing Diagrams are Interaction diagram for
    reasoning about time.
    • Basic elements: lifelines, states, duration/time
    constraints, destruction, events, messages

    SDA 4
    Lifeline
    • Lifeline is a named element which represents
    an individual participant in the interaction. Lifelines
    represent only one interacting entity.
    • Lifeline on the timing diagrams is represented by
    the name of classifier or the instance it represents. It
    could be placed inside diagram frame or a
    "swimlane".

    representing instances of
    SDA System and Virus 5
    State or Condition
    Timeline
    • Timing diagram could show states of the
    participating classifier or attribute, or some
    testable conditions, such as a discrete or
    enumerable value of an attribute.

    • Timeline shows Virus changing its state between


    Dormant, Propagation, Triggering and Execution
    state

    SDA 6
    Duration Constraint
    • Duration constraint is an interval constraint that
    refers to a duration interval. The duration interval is
    duration used to determine whether the constraint
    is satisfied.
    • E.g., Ice should melt into water in 1 to 6 minutes

    SDA 7
    Time Constraint
    • Time constraint is an interval constraint that refers to
    a time interval. The time interval is time expression
    used to determine whether the constraint is
    satisfied.
    • Typically this graphical association is a small line,
    e.g., between an occurrence specification and a
    time interval.
    • E.g., Person should wake up between 5:40 am and
    6 am

    SDA 8
    Destruction Occurrence
    • Destruction occurrence is a message occurrence which
    represents the destruction of the instance described by
    the lifeline.
    • It may result in the subsequent destruction of other
    objects that this object owns by composition.
    • No other occurrence may appear after the destruction
    event on a given lifeline.
    • Notation
    • The destruction event is depicted
    by a cross in the form of an X
    at the end of a timeline.

    SDA 9
    Carpark Example

    SDA 10
    Carpark Example

    SDA 11
    Ex 1: Coffee Pot
    • Let's take a simple scenario based on the pump and
    hotplate for a coffee pot. Let's imagine a rule that says
    that at least 10 seconds must pass between the pump
    coming on and the hotplate coming on. When the
    water reservoir becomes empty, the pump switches
    off, and the hotplate cannot stay on for more than 15
    minutes more.

    SDA 12
    Timing Diagram
    Notations
    • There are two basic flavors of timing diagram,
    o Concise notation
    o Robust notation

    • Showing states as lines – They are known as State


    Lifeline diagram or robust notations
    • Showing states as areas - They are known as Value
    Lifeline diagram or consise notations

    SDA 13
    Timing diagram-concise
    notation
    • Life Cycle of Seminar
    • The critical states that the seminar exhibits
    o Proposed,
    o Scheduled,
    o Enrolling Students,
    o Being Taught,
    o Final Exams,
    o Closed

    SDA 14
    Timing diagram-robust
    notation
    • Happenings while a seminar is being taught.
    • The professor delivers the seminar and marks
    student work
    • The teaching assistant develops the course material
    by doing the research on course material and then
    update the material just in time for it to be taught.
    • Total duration of seminar is 13 weeks. Events/stimuli,
    such as Holiday Break and Break Ends indicate the
    reason for the change.
    • The arrows between timelines are messages
    between the objects.

    SDA 15
    SDA 16
    Another Example

    SDA 17
    Example 1
    • Figure 6.19 shows a case where two active objects
    share a common resource. In this case, both
    objects show a trade that requires the execution
    engine for some time. One object is for a “platinum”
    user who is guaranteed a trade within 10 time units,
    and the other is a “gold” user who has no
    performance guarantee. The user objects have a
    waiting and executing state along with an idle
    state. The execution engine has a processing state
    that takes five time units for each trade and an
    executing state that takes two time units.

    SDA 18
    Example 1
    • Different priority objects shown on a timing diagram.

    SDA 19
    Ex 2: Website Latency
    • An example of timing diagram which shows
    some duration constraints for a fabricated website
    to evaluate how long web user should wait to see
    something rendered on his/her display.
    • After web user enters web page URL, the URL should
    be resolved to some IP address. DNS resolution can
    add some tangible waiting time to the response
    latency as perceived by user. Latency delays
    related to DNS resolution could range from 1 ms
    (local DNS cache) to several seconds.

    SDA 20
    Ex 2: Website Latency
    • With simple Model–View–Control (MVC)
    implementation, Java servlet gets control and
    requests some data from "model". Communication
    with data sources usually takes some discernible
    time. After data is received and processed, servlet
    forwards request processing to JSP ("view"). Buffered
    HTTP response is sent back to the browser.
    • Web browser takes some time to process HTTP
    response and HTML page to start rendering the
    page view to the web client. (Note, that after that it
    could take even more time for the web browser to
    request other resources like CSS, JavaScript, images,
    which is not shown on the diagram.)

    SDA 21
    SDA 22
    Ex2 : Notations

    SDA 23
    Ex 3: Stages of Alzheimer’s
    Disease
    • Alzheimer's disease (AD) is a a progressive,
    ultimately fatal brain disease that causes loss of
    memory and intellectual abilities. The cause of the
    disease is unknown. AD has no cure and is one of
    the leading causes of death in the United States.
    • For Alzheimer’s disease doctor may use a
    diagnostic framework with three to seven levels
    (stages). Progression through these stages may last
    from 8 to 10 years, and in some cases up to 20 years
    from the time neuron changes start.
    • Example of timing diagram below shows timing for
    the seven stage framework.

    SDA 24
    Ex 3: Stages of Alzheimer’s
    Disease

    SDA 25
    Ex : 4

    SDA 26
    Example
    • Let us understand timing diagram with an example.
    I have an automatic door, it stays open for 300 ms,
    after that it is programmed to close itself. While
    closing it will raise an alarm for 200ms indicating
    others that the door is closing.

    SDA 27
    State Life line

    SDA 28
    Value lifeline

    SDA 29
    That is all

    SDA 30

    You might also like