Use Case UC_204

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_204
Name Manage Federates in the Model Manager Application
Primary Actor Model Owner
Level User Goal
Description This use case describes the interactions required to configure the model manager and put in a state where it is ready to integrate additional federates and to make them available to certain simulation manager applications.
Pre-Condition Use case UC_202 (Set-up model manager application) has been successfully completed.
Post-Condition Some (or all) federates included in the model manager application are ready to be integrated into a simulation experiment.

top ^

Main Success Scenario

  1. Actor stops the model manager application if it is running.
  2. Actor copies a federate to the appropriate location in the model manager using operating system tools.
  3. Actor starts the model manager application.
  4. System automatically locates all federates that are in the appropriate location.
  5. System displays all federates from this location in a list.
  6. Actor chooses to register or de-register a federates in the model repository. The actor might repeat this step as often as necessary.
  7. System registers or de-registers the federate in the model repository.
  8. Actor chooses to save the current configuration.
  9. System saves the configuration to the model repository.
  10. Actor chooses to manage permissions for each of the registered federates.
  11. System displays a dialog that allows the actor to choose the simulation managers that have access to each federate. The list shows all simulation manager applications that are registered in the model repository to which the model manager application is currently connected to.
  12. Actor chooses to save the current configuration.
  13. System saves the configuration to the model repository.

top ^

Alternative Flows

7a. No network connection to the repository available.

1. System displays error.

2. System aborts operation.

7b. Actor chooses to register federate.

1. System connects to the EODiSP federate repository.

2. System transfers information about the federate to the repository to uniquely identify it.

7b. Actor chooses to deregister federate.

1. System connects to the EODiSP federate repository.

2. System instructs global repository to deregister federate.

11a. No simulation manager application is registered in the EODiSP network.

1. The actor waits until at least one simulation manager application has been registered in the EODiSP network.

top ^