Activity Report

Overview

This form displays and/or prints a report summarizing the total monthly refunds/compensation given to customers.

Screen Layout

 Sample Compensation report
 -------------------------

Dairy Air Airlines
Compensation Report
Jan 20, 1997

Route           # compensated           Ticket Price            Total amount

Cal-Tor               4                   $1000.99                $2001.98
Cal-Edm               65                  $0.99                   $32.17
---------       -------------           ------------            ------------
Total                 69                    N/A                   $2034.15

This form will be simple: It will have a button for Daily Summary, a button for Monthly Summary and a button for Yearly Summary. There will be three fields for user input: Day, Month and Year. It will also have buttons at the bottom for Print and OK/Back/Cancel.

Events/Actions

The user will press one of the three central choice buttons after entering date specifics into the three fields. If the user presses Yearly Summary, the system will ignore any input in the other two fields and proceed to report on the information in the Year field. Pressing Monthly Summary will cause the program to use the information in the Year and Month fields, and pressing Daily Summary will require valid Day, Month and Year fields. The Print button will be activated after the desired report has been displayed on the screen. The user will have the option to either print or not, and can return to the Reports menu at any time.

Dairy Air comments and questions are in blue emphasis

This is quite close to what was specified in the Informal Requirement Specification. However, as specified in our clarifications,we require "a report listing the number of people compensated per month and the total value of the discounting broken down into flights." The specified report would just have to be repeated for each month. We also wanted a warning for any flights that have people on it who have been compensated more than once.

Error Handling

This form will only have to check that the user has entered a valid date for which at least one Flight record exists in the Flight table. If this is not the case, the user will be informed that
a) There are no records for that day, month or year or
b) The user has entered an invalid date (ex. 96/02/30 - nope!)

Forms Called by the Refund Report form

This form will not call any forms except to return the user to the Reports form. It will call the utility module responsible for printing.

Security Settings

Group Name Can Access?
Systems Admin

X
Plane Admin

 
Flight Admin

X
Booking Agents

 


Data Requirements

Flight table