Actors: any user.
Outline: the user logs into the DAS computer and starts all the attached cameras. The user then manipulates the CIA to get access to the cameras of choice.
Associated use-cases:
Typical course of events:User action | System response | |
---|---|---|
1. | Begins with the DAS shut down. | |
2. | Runs use-case access DAS. | As per subordinate use-case. |
3. | Gives the startobssys command. | Determines which cameras are in the "unclaimed" state. Moves those cameras to the "on-line" state. Reports to the user the state of all the cameras. |
4. | Checks the state of the cameras needed for the work. | Shows the relevant cameras as "on-line". |
5. | Runs use-case start CIA and ICS. | Finds the relevant cameras and puts them in the "idle" state. |
Step 3 implies that the system can work out a number of lists: which cameras have profiles; which interfaces to cameras are present on the computer; of the interfaces, which are in use; of the interfaces in use, which are used by server programmes and which by lab. programmes; of the interfaces not in use, the detector IDs of the attached cameras.