Use Case: Executive, UserAdmin Package: Create_AlmaUser

All users of the ALMA observing system must be authenticated and provided with appropriate access privileges before using the facilities. Thus, this information (and other required data such as name, affiliation, addresses and e-mail) must be available in the ALMA database.

What is the interface for the input? GUI? Command line? or Both?

Goal:   Add new user to the database.

Contact Author:   P. Grosbol

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

• Administrator, an administrator, with special privileges to modify user information, performs the task to create and modify the AlmaUser database.
  

• Database with user information.
  
• Archive, receives transaction log?
  
• AlmaUser, gets added to the database.
  

  Priority:   Major

  Performance:   On the order of seconds

  Frequency of Use:   A few times per week

  Preconditions:

  1. Database with AlmaUser information is available.
  2. Administrator can be authenticated (e.g. by pre-loading the database with the information of the administrator).

  Basic Course:

  1. Administrator logs into the system and gets authenticated.
  2. An empty AlmaUser object is created.
  3. A UserID is selected.
  4. This userID must be unique and is therefore checked against existing UserID's in the database.
  5. The user is allocated to one or more privilege groups defined in the database.
  6. Additional information (such as name, affiliation, e-mail) is inserted.
  7. A default password is defined for the user.
  8. The new AlmaUser object is added to the database.
  9. Administrator logs out or continues with other related tasks.
  10. Alternative Course:
      
      • Administrator fails the authentication.
      • The processing is terminated.

  Postconditions:

  1. A new AlmaUser is created in the database.
  2. A transaction log is saved.
  3. New User is notified?
     

  Issues to be Determined or Resolved:  

  1. none at this time

  Last modified: 19sep03