Use Case Description

 

  1. UC-1 Logon
    1. Brief Description

    This use case is required by all ABIDES-FE users. It confirms the user is a valid ABIDES host user (i.e., is a valid UNIX account on the platform on which ABIDES executes) and, if a valid user, determines the user’s authorized data by querying the ABIDES authorization tables, the user’s office symbol, and the user’s preferences.

     

  2. Flow of Events
    1. Basic Flow
  1. ABIDES User (User) initiates application.
  2. (System displays Logon screen.)
  3. User enters ABIDES user id and password.
  4. User selects OK. [A-1]
  5. (System validates user id and password. [E-1])
  6. (System retrieves user’s authorized data [E-2], office symbol [E-3], and user interface preferences.)
  7. (System displays main ABIDES-FE screen.)

 

    1. Alternate Flows
      1. A-1 - User Cancels Logon
  1. User selects cancel.
  2. (System confirms cancel.)
  3. (System closes Logon screen and exits application.)

 

      1. E-1 - User ID and/or Password are Invalid
  1. (System displays an explanatory error message to the user.)
  2. (System permits user to resubmit ABIDES user id and password. Follow main flow from step 2.)

 

      1. E-2 - System cannot retrieve user’s authorized data.
  1. (System displays an explanatory error message to the user, including suggestions for system administrator to reestablish account).
  2. User dismisses error message.
  3. (System closes Logon screen and exits application.)

 

      1. E-3 - System cannot retrieve user’s office symbol.
  1. (System displays an explanatory error message to the user, including suggestions for system administrator to establish default office symbol for user).
  2. (System prevents subsequent restoring or saving of Execoms.)
  3. User dismisses error message.
  4. (System displays main ABIDES-FE screen.)

 

  1. Participating Actors

    2. ABIDES User - Any interactive user of the ABIDES-FE Report Break. It is assumed that they require reports to analyze the state of the budget.

     

  2. Pre-Conditions

    3. None.

     

  3. Post-Conditions

    4. User must be logged into ABIDES-FE as a result of execution of main flow.

     

  4. Extension Points

    5. None.

     

  5. Supplemental Requirements
    6.

    Known User Roles

    For example, "all update files" is only available to SAF/FMBP.

    Role

    Capability

    x

    update all files

    z

    a

     

  6. Open Issues

None.