Use Case Description

 

  1. UC-6 Update User Preferences
    1. Use Case Summary

    This use case allows the user to set system and report break application preferences (default information specific to a user such as font size). The system initializes itself with user preferences which override the system default values and take effect before the application is displayed or at the time when the preferences are first applied.

     

  2. Flow of Events
    1. Basic Flow
  1. User selection preferences functionality.
  2. (System displays preferences user interface including existing preferences.)
  3. User selects preference to create or change.
  4. User applies preference.
  5. User exist preferences functionality.

User changes font size.

User changes office information (probably not).

User changes parameter format (exists on another screen).

User changes default browser (including if location changes).

User changes default execom directory.

{TO DO: consider appropriate warnings where necessary}

 

    1. Alternate Flows

 

  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.

    abides - The legacy system that actually produces the report.

     

  2. Pre-Conditions

    3. User has successfully logged into ABIDES-FE.

     

  3. Post-Conditions

    4. Preference creation or change is reflected in the executing system.

     

  4. Extension Points

    5. None.

     

  5. Supplemental Requirements

    6. None.

     

  6. Open Issues

None.