Deploy Procedure of FESA3

Before Deployment of a FESA3 Deploy-Unit

• Creation of FESA3 class(es) / source-code generation / compilation
• Creation of FESA3 deploy-unit containing FESA3 class(es)
• Precondition: used FESA3 class(es) are in the same workspace as FESA3 deploy-unit

Steps during Deployment Process

Preconditions

• Only productive (operational) versions of FESA3 class(es) should be contained in a FESA3 deploy-unit
• Only productive (operational) versions of FESA3 deploy-units should be considered during deployment
• Only productive (operational) versions of FESA3 deploy-units and FESA3 class(es) should be stored in SVN

Steps undertaken during Deployment Process

Automatically

• Status Quo: source-code generation / compilation / linking of FESA3 deploy-unit

Necessary / Missing

• Automatic source-code generation / compilation / linking of all FESA3 classes contained in FESA3 deploy-unit -> Precondition: used classes have to be in the same workspace.
• It has to checked that all the used FESA3 classes have the same state (e.g. "operational")

Issues to consider for SVN repository handling

• Only acceptable files such as source files, documentation and files that cannot be regenerated will be stored in the repository.
• Ignored by default will be the folders generated, bin and build