Use Cases for Experiment Control
Use Cases are a statement of the expect actions that the Experiment Control sub-system is expected to perform. They not only define the behaviour of the sub-system. but also define, in terms of actors, the external interactions of the sub-system.
Control Supernova DAQ Sub-System
Actors
- Operator - A person or process that wants to start or stop the supernova DAQ sub-system.
- sn - The supernova DAQ sub-system, which can be started and stopped.
Control Processing and Filtering Sub-System.
Actors
- Operator - A person or process that wants to start or stop the processing and filtering sub-system.
- PnF - The processing and filtering sub-system, which can be started and stopped.
Control SPADE Sub-System
Actors
- Operator - A person or process that wants to start or stop the SPADE sub-system.
- SPADE - The SPADE sub-system, which can be started and stopped.
Control Cluster Montoring Sub-System
Actors
- Operator - A person or process that wants to start or stop the cluster monitoring sub-system.
- cluster - The cluster monitoring sub-system, which can be started and stopped.
Control a Data-Taking Run
Actors
- Operator - A person or process that wants to start or stop a data-taking run.
- DAQ - The IceCube daq acquisition sub-system, which can be started and stopped.
- TWR - The Amanda daq acquisition sub-system, which can be started and stopped.
- Run Summary DBMS - The DBMS that stores run summaries.
Continuous Data-Taking
Actors
- Operator - A person or process that wants to start or stop continuous data-taking.
- DAQ - The IceCube daq acquisition sub-system, which can be interrogated about its current state.
- TWR - The Amanda daq acquisition sub-system, which can be interrogated about its current state.
- Run Summary DBMS - The DBMS that stores run summaries.
Control a Flasher Run
Actors
- Operator - A person or process that wants to start or stop a flasher run.
- DAQ - The IceCube daq acquisition sub-system, which can be started, stopped and updated to run with new flasher configurations.
- Run Summary DBMS - The DBMS that stores run summaries.
- Flasher DBMS - The DBMS that stores flasher configurations.
Check a Sub-System's State
Actors
- Operator - A person or process that wants to check the state of a sub-system.
- DAQ - The IceCube daq acquisition sub-system, which can be interrogated about its current state.
- TWR - The Amanda daq acquisition sub-system, which can be interrogated about its current state.
- sn - The supernova DAQ sub-system, which can be interrogated about its current state.
- PnF - The processing and flitering sub-system, which can be interrogated about its current state.
- SPADE - The SPADE sub-system, which can be interrogated about its current state.
- Cluster - The clustering sub-system, which can be interrogated about its current state.
Summarize a Sub-System
Actors
- Operator - A person or process that wants to inspect a sub-system's summary.
- DAQ - The IceCube daq acquisition sub-system, which can be interrogated about the current values of some of its attributes.
- TWR - The Amanda daq acquisition sub-system, which can be interrogated about the current values of some of its attributes.
- sn - The supernova DAQ sub-system, which can be interrogated about the current values of some of its attributes.
- PnF - The processing and flitering sub-system, which can be interrogated about the current values of some of its attributes.
- SPADE - The SPADE sub-system, which can be interrogated about the current values of some of its attributes.
- Cluster - The clustering sub-system, which can be interrogated about the current values of some of its attributes.
Monitoring the Status of the detector
Actors
- Operator - A person or process that wants to start, stop or modify the detector status operations.
- email - An email sub-system that sends out email messages to a list of recipients.
- Status Web Pages - A Collection of XML, XSL and HTML pages that display the current status and history of the detector.
