Use case: start the central intelligence (CIA) and ICS

Purpose: to make the observing system ready for use.

Actors: any user.

Outline: the user gives the startobssys command. The system confirms and rcords the user's identity. The system determines what software is running on the system computer and what is lacking for the previously-chosen configuration; it starts any programs that should be running but aren't. At the end of the operation, the system's mimic displays are active, the observation log is active and its display is up.

Related use cases:

Typical course of events:

User action System response

1. User logs in to the system computer using the standard observing account.

2. User gives the obssys command. System offers a menu of instrument/detector/version choices and requires the user to confirm his/her identity.

3. User confirms identity. User selects from the menu. System records the responses, and selects the necessary applications, but does not start any software.

4. User gives the startobssys command. System starts all displays and servers needed on the system computer for the chosen configuration. System locates the remote sub-systems (TCS and cameras); cameras go from the "on-line" state to the "idle" state. System passes configuration details as necessary to the DAS.

	User action	System response
1.	User logs in to the system computer using the standard observing account.
2.	User gives the obssys command.	System offers a menu of instrument/detector/version choices and requires the user to confirm his/her identity.
3.	User confirms identity. User selects from the menu.	System records the responses, and selects the necessary applications, but does not start any software.
4.	User gives the startobssys command.	System starts all displays and servers needed on the system computer for the chosen configuration. System locates the remote sub-systems (TCS and cameras); cameras go from the "on-line" state to the "idle" state. System passes configuration details as necessary to the DAS.