Use Case: Executive, AlmaAdmin Package: Alma_TransferInfo

The ALMA Observing System will store most of its operational state information as logs in a database (e.g. changes, commands, errors and warnings). These data are stored in XML format defined by ALMA and not necessarily easy to ingest in the external tool (to be defined) which will be used for generation of operational reports and maintenance of the system.

This Use Case illustrates the request by an administrator to get log information for a well defined time range ingested into the external administrative tool.

Goal:   Administrator gets log information

Contact Author:   P. Grosbol

Role(s)/Actor(s):
Primary:  

• Administrator
  

• Database
  

Priority:   Critical

Performance:   On the order of minutes

Frequency of Use:   A few times per week

Preconditions:

1. ALMA archive is available for access to logging and error information
2. ALMA software is installed on system
3. The external administrative tool is available and running

Basic Course:

1. The administrator starts the AlmaAdmin tools
2. It verifies that it can connect to both the ALMA archive and the external administrative tool
3. The administrator specifies which kind of data should be transfered and for which time period.
4. AlmaAdmin requests the requested data from the archive
5. The data are re-formatted to suit the external administrative tool and submitted to it.
6. A summary of the transfer is provided to the administrator.
7. Alternative Course:
   
   • If no connection can be established to either the archive or the external tool, the application terminated with an error message.
   • If no data are available for the request, a warning is issued.

Postconditions:

1. New information is ingested into the administrative tool

Issues to be Determined or Resolved:  

1. none at this time

Last modified: 31oct03