Use Case UC_110

This page describes one of the use cases of the EODiSP. An overview of the use case concept as it is used in the EODiSP project and of all the use cases defined for the project is provided in a dedicated page which also describes the conventions that are used to define the use case.

Contents

Overview

Identifier UC_110
Name Experiment Abort
Primary Actor Simulation owner
Level Subfunction
Description Aborts a running simulation experiment before it is finished. There is no recovery, once a simulation experiment has been aborted. All simulation data which are not stored are lost.
Pre-Condition A simulation experiment which is controlled by this simulation manager application is currently running (see Use Case UC_102 Run Experiment).
Post-Condition Simulation manager is in a clean state and ready to start a new simulation experiment.

top ^

Main Success Scenario

  1. Actor chooses to abort the running simulation experiment.
  2. System sends a message to all participating model manager applications asking them to deregister all federates from the simulation experiment, to stop them, and to enter a clean state.
  3. System waits until all federates have resigned from the federation and are in a stopped state.
  4. System reinitialises itself and enters a clean state.

top ^

Alternative Flows

3a. System detects an error when sending a request to abort a federate.

1. System signals error.

2. Actor acknowledges the error.

3. Actor hard-resets a the experiment.

4. System reinitializes itself and enters a clean state.

top ^