View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide

UC6.2 - Iteration 3

UC6.2: Resume Execution


Primary Actor: Peer-to-peer Researcher / ODIN Developer.


Stakeholders and Interests:

ODIN Developer:
Wants to stop stepping through the simulation one step at a time and let the program run the simulation by itself.

Preconditions:


Success Guarantee (Postconditions):

When execution is resumed, the viewer will exit its breaked state and continue running the ONA file.

Main Success Scenario

  1. The user clicks the "Resume" button while the simulation is breaked.
  2. The viewer will exit the breaked state.
  3. The "Step" and "Resume" buttons will disappear.
  4. The "Break on Event" checkbox will reappear and its state will be checked.
  5. The simulation will continue running by itself at the simulation speed specified by the speed slider.

Extensions (Alternative Flows):

If the current line is the last command in the ONA file, pressing "Resume" will result in the simulation ending, and a message indicating the simulation has ended.

Special Requirements:

The simulation must be breaked for the Resume button to be visible.

Technology and Data Variation List:

None.

Frequency of Occurrence:

Realistically the user will not want to step through every command in a request / response sequence. Therefore it can be estimated that the "Resume" button will be pushed as many times (or fewer) as a break occurs.

Open Issues:


The current plan is to hide the "Break on Event" checkbox and show the "Step" and "Resume" buttons when breaked. The downside to this is that the user can't set the "Break on Event" option until resuming. Hopefully it will be sufficient to leave this option selected as the default state. This makes it impossible to miss a desired breaking point.



Links to this Page