Use Case UC_104

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_104
Name Configure Simulation Experiment
Primary Actor Simulation owner
Level User Goal
Description Describes the configuration which has to be made prior to starting a simulation experiment.
Pre-Condition Use case UC_102 (Set-up simulation manager application) has been successfully completed.
Post-Condition A simulation experiment is configured and ready to be run.

top ^

Main Success Scenario

  1. Actor chooses to add a new experiment
  2. System add a new experiment and displays it with a default name.
  3. Actor chooses to add a federation execution to the experiment.
  4. System add a new federation execution to the experiment and displays it to the user.
  5. Actor chooses to find available federates.
  6. System presents all federates which are currently available in the EODiSP network.
  7. Actor integrates as many federates as he wishes (i.e. as needed for a specific federation execution) from the list of available simulation models into an already existing federation execution.
  8. System retrieves information about federates which are to be integrated
  9. System displays an updated list of federates included in the federation.
  10. System locally copies information about a federate into the simulation experiment
  11. Actor may add as many federations as he wishes to the experiment.
  12. System displays an updated list of federation executions included in a simulation experiment.

top ^

Alternative Flows

a*. At any time, system detects an internal, unrecoverable error.

1. System tries to save unsaved data.

2. System signals error.

3. System exits.

4. Actor restarts the simulation manager application.

b*. At any time, actor chooses to update the list of available federates.

1. System presents an updated list of available federates.

c*. At any time, actor chooses to save the current state of the application (including all experiments) to the file system.

1. System saves the data.

1a. Actor chooses to load an already existing 'SimulationManagerProject' file.

1. See UC_108.

2. Go to step 12.

top ^