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

UC6 - Iteration 3

UC6: User instructs visualization GUI to break on specific simulation event.


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


Stakeholders and Interests:

ODIN Developer:
Wants execution of simulation playback to halt when a noteworthy event occurs. This will allow the ODIN developer to inspect the network more closely at this specific instance in time.

Preconditions:


Success Guarantee (Postconditions):

On request, the simulation is paused when a noteworthy event occurs. See open issues for discussion about this event.

Main Success Scenario

  1. The simulation is started with a specified ONA file and the simulation starts to run.
  2. If the user wants the simulation to break execution, they will click the checkbox that says "Break on Event".
  3. If a command entry of this type is processed in the ONA file, execution of the simulation will stop.
  4. The log entry for this event will be displayed at the bottom of the screen, along with the timestamp of the event (in milliseconds).
  5. The user will be able to perform all normal functions with the graph, in addition to two new functions (step and resume) which are detailed in UC6.1 and UC6.2

Extensions (Alternative Flows):

Once a break of execution has occurred, two new functionality features are possible. These are detailed in UC6.1 - Iteration 3 - Stepping during breaked execution and UC6.2 - Iteration 3 - Resuming from breaked execution.

Special Requirements:

The simulation must be running for a break to occur.

Technology and Data Variation List:

None.

Frequency of Occurrence:

The option to break is set to off by default, so with no user interaction to change this setting a break will not occur during normal execution. Once this setting is enabled a break could occur at any undetermined time while the simulation is running.

Open Issues:




Links to this Page