Suggested Workflow for integration of the FESA3 Database in the deployment process for operational FESA3 software

From FESA3 2.0.1 on the FESA3 database is integrated in the deployment process for operational FESA3 software. The distinction will be made depending on the state of the FESA3 class or deploy-unit. The state can be one of the following:

state	meaning
development	FESA3 software is under development
inUse	Not defined yet, a possible use would be to use this state for mockup FESA3 software that is used for testing application software
operational	Productive FESA3 software
deprecated	Intended for classes that are not used anymore

Releasing operational FESA3 software for FESA3 2.0.1

The current procedure for storing information on FESA3 classes for operational software is as follows:

1. Define the FESA3 class state to be operational. If the class has already been released make sure the classes version number is higher.
2. Deliver the FESA3 class
3. Define the FESA3 deploy-unit state to be operational. If the deploy-unit has already been released make sure the deploy-units version number is higher.
4. Select the instantiation document that should be in the database. Select Export FESA Instance from the toolbar or the FESA context menu.

For the future this is highly likely to change.

-- SolveighMatthies - 09 Sep 2014