Actors: CCD specialist or DE.
Outline: the user uses the engineering interface to see the camera's state, edit and reload the engineering profile and take test exposures.
Related use cases:
Typical course of events:Access the DAS computer Change a camera
| User action | System response | |
| 1. | Use case begins when the user needs to change the settings for a camera that is connected to the DAS computer. | |
| 2. | Runs use-case access DAS to get into the DAS computer. | As per subordinate use-case. |
| 3. | Gives the command udaseng. | Displays the entry page of the engineering interface. |
| 4. | Presses the scan for cameras button. | Displays an updated list of the states of cameras. |
| 5. | Checks that the camera of choice is "on-line" or "idle" or "busy"; selects the camera in the display and presses the show details buttons. | Displays the state of the camera. |
| 6. | Does one or more test exposures using the controls in the engineering interface. Examines the results on the DAS' image-display. | Takes pictures and displays them. |
| 7. | Presses the edit profile button. | Displays the camera's profile in a text editor. |
| 8. | Edits the profile data; presses the update profile button. | Checks the profile data. If it is valid, stores the modified profile on disc and restarts the camera, causing it to use the new profile. |
| 9. | Repeats steps 5..8 until satisfied, bored or defeated. |
Variations:
Notes:In step 5, if the camera is shown as disconnected, run use-case change camera to connect it, then go back to step 4. Steps 5..7 can be done in any order. Once step 8 is done, it is necessary to go back to step 5 to get control of the restarted camera. The state displayed in step 5 is a mimic display that updates in real time.
When the profile is saved, it over-writes the previous profile and the system itself does not keep a back-up copy. The user can take a copy of the profile if desired.