Use Case UC_312
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_312 |
| Name | Generate Wrapper Code for a Standalone Executable |
| Primary Actor | Model owner |
| Level | User Goal |
| Description | Describes the steps to create the code that wraps an existing executable with a defined in- and/or output as a federate that can be integrated into the EODiSP. |
| Pre-Condition | (1) The input and output of a standalone executable is known. (2) The support application is running. (TBC) |
| Post-Condition | (1) The code that implements the federate wrapper for the standalone executable is available. |
Main Success Scenario
- Actor creates a new SOM file (see use case UC_316).
- Actor chooses to generate the federate interface implementation code from the SOM.
- System generates the federate interface implementation code.
- Actor implements the connector code that connects the federate interface implementation code with the standalone executable.