Use Case Specification

 

  1. Manage Breaks
    1. Brief Description

    This use case enables the Budget Analyst to control the manner in which data are grouped and the detailed information which applies to the groupings.

     

  2. Flow of Events
    1. Main Flow - Break Headers

Definition: Provides the capability to produce a report using the last break as the column headers. Only one year of data may be printed using this option.

Usage: Create Basic Report: Budget Analyst must enter at least two breaks for this option to work.

Association: Break Headers Total

  1. Budget Analyst selects 23 = break headers {bh}
  2. (System uses last break entered for the column header.)

Default: Maximum of 100 break headers. Exceeded when test_db with all appropriations was selected.

Result: since only one year of data is displayed, additional columns for the data element wrap to the next page.

 

    1. Alternate Flows
      1. Break Headers Total

        2. Definition: Provides the capability when break headers option is selected, to add an additional column called "TOTAL PROGRAM" which totals the data for the line.

        Usage: Budget Analyst must select Break Headers in order to use this option.

        1. Budget Analyst selects 38 = break headers total {bht}

        {TBD: expected results, more input?}

         

      2. Additional Data Elements

Definition: Provides the capability to select additional data elements that will be printed on the same line as the last break. Allows Budget Analyst to change the sort order of the report.

  1. Budget Analyst selects 13 = additional data elements {ade}
  2. (System displays menu to get Budget Analyst’s breaks for the last break line.)
  3. (System displays current sort order)
  4. (System prompts Budget Analyst to accept or change the sort order)
  5. Budget Analyst enters new sort order or accepts the current sort order.

 

      1. Page Break

Definition: Provides the capability to start a new page each time the data element chosen for a break changes.

  1. Budget Analyst selects 10 = page break {pb}
  2. (System displays available breaks from breaks previously chosen.)
  3. Budget Analyst select data element on which to perform page breaks (only one is allowed).

 

      1. Suppress Data Element

        2. Definition: Provides the capability to suppress the printing of the data element abbreviation and value.

        1. Budget Analyst selects 26 = suppress data element {sde}

        2. (System suppresses all data elements chosen for breaks.)

         

      2. Suppress Break Totals

Definition: Provides the capability to suppress the total lines for selected breaks.

  1. Budget Analyst selects 22 = suppress break totals {sbt}
  2. (System displays totals to suppress from breaks chosen. If three are chosen, first two selected are available for suppression of totals.)

 

      1. No Record Aggregation

Definition: Provides the capability to prevent records with the same breaks from being aggregated into a single record.

  1. Budget Analyst selects 34 = no record aggregation {nag}

 

  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 creating or updating a F&FP Report Break and at least one break has been selected.

     

  3. Post-Conditions

    4. System produces report with the Budget Analyst’s requested changes to the breaks.

     

  4. Extension Points

    5. None.

     

  5. Supplemental Requirements

    6. None.

     

  6. Open Issues

None.