This page describes one of the test cases of the EODiSP. The test case described in this page instantiates a nominal scenario of the use case UC_204.

This test case uses the EarthCARE Simulator as a test platform. The simulator is operated in its default configuration.

Overview

Identifier	TC_204
Name	Set-up Model Manager Application
Primary Actor	ETH_2 Model Owner
Description	Describes the steps to arrive at a running, fully functional model manager application.
Pre-Condition	Test case TC_202 (Set-up Model Manager Application) has been successfully completed.
Post-Condition	All federates owned by ETH_2 required to run the EarthCARE Simulation are registered in the repository and ready to be used by the simulation manager

Steps

1. Actor exits the model manager application if it is still running.
2. Actor copies all federates that he will need for the EarthCARE simulator to the data/federates directory in the current working directory of the model manager. Copying is done by using ordinary operating system tools.
3. Actor starts the model manager application.
4. System shows all federates that have just been copied.
5. Actor chooses to connect to the repository by either pressing the Connect Icon or by selecting Connect from the Repository menu.
6. System connects to the Repository and indicates an established connection by disabling the connect icon
7. Actor chooses, for each of the federates, to register it in the model repository application by right-clicking on the federate an selecting Register Federate.
8. Actor chooses to upload the changes by either clicking the Up-Arrow Button or by selecting Save to Repository from the Repository menu.
9. Actor manages the permissions for each registered federate. This is done by right-clicking on the federate and selecting Manage Permissions.
10. System shows the permission dialog.
11. Actor chooses to allow every simulation manager that participates in the EarthCARE simulator to use the selected federate.
12. Actor chooses to upload the changes by either clicking the Up-Arrow Button or by selecting Save to Repository from the Repository menu.
13. Actor adds additional information for each registered federate by right-clicking on the federate and selecting Add Additional Information.
14. System shows the dialog.
15. Actor adds information about the machine on which the federate is running (e.g. operating system, Java version, etc.).
16. Actor chooses to upload the changes by either clicking the Up-Arrow Button or by selecting Save to Repository from the Repository menu.