Requirements and Use Cases

The design of the database schema, the organisation of the database into separate files and the implementation of the data access libraries (DALs) have to satisfy the following use cases:

• load the whole system during the standard run control state sequence from ``initial'' to ``running''.
• load a partial system, eg a subset of the crates or crates with a subset of modules.
• stop a run and a start a new one loading a newly selected trigger menu and using any new calibrations which may have appeared (ie these operations must be completely handled just at the transition between ``configured'' and ``running'').
• take a calibration run and produce new calibration files.
• view/edit the calibration database.
• create test calibration databases, eg with all channels set to the same value.
• store/retrieve calibration data in/from the offline conditions database.
• change the trigger menu or produce a new trigger menu offline and distribute it to the processor system.