Use Case Description

 

  1. Getting Help
    1. Brief Description

    This use case represents how the Budget Analyst will interact with the on-line user manual, context sensitive help and information which is specific to ABIDES-FE.

     

  2. Flow of Events
    1. Basic Flow
  1. Budget Analyst requests general help information regarding ABIDES-FE (installation, logging in, etc.)
  2. (System displays help palette.)

 

    1. Alternate Flows
      1. A-1 Budget Analyst views content specific ABIDES-FE help (e.g., option definition and usage, relationship, etc.).

        2.  

      2. A-2 Budget Analyst views information regarding data element definitions and relationships.

        3.  

      3. E-1 Help is not displayed.

        4.  

      4. E-2 Information displayed is incorrect.
      5. Supplemental Requirements

The end users will have to supply many of the definitions and information regarding the relationships between the data elements.

{TBD: may want to include the F&FP keycode and break out by appropriation.}

 

  1. Participating Actors

    2. Budget Analyst - 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. Budget Analyst is logged into the system.

     

  3. Post-Conditions

    4. System displays the help information that the Budget Analyst requested.

     

  4. Extension Points

    5. None.

     

  5. Supplemental Requirements

    6. None.

     

  6. Open Issues

None.