Report on Fines

Report on Fines

Interface Definitions:

Inputs to module:

• There are no inputs to this module.

The module report on fines is a sub module of the "library transaction" module. It is called from the first level of the Nexus booklenders software to let the librarian have some control of the fine data store. The call is done by a simple request at the top level with the click on a button using a mouse.

Inputs by user:

• None.

Outputs:

• This module has no output to the user other than a selection of sub-modules.

This module calls one or more of four sub modules. In all of these cases the module causes the sub-modules to query the databases for information concerning either the specific fields or a full report. These sub-modules call the Fine data store, Book data store or the Borrower data store for its required information.

Data Abstractions:

ID# is a positive integer number

call# is a positive integer number

borrowed is a date (see data stores for a definition)

returned is a date

due is a date

amount is a currency (see data stores for a definition)

first is a variable length string of characters denoting a first name.

last is a variable length string of characters denoting a last name.

middle is a variable length string of characters.

address is a variable length string of characters.

city is a variable length string of characters.

prov/state is a variable length string of characters.

code is a variable length string of characters.

type is an alphanumeric character.

cost is a currency

title is a variable length string of characters.

Sub-Modules:

1. Report (on overdue books)
2. Search (on specific field)
3. Modify (a field)
4. Print (a report)
   

Design:

Environment: GUI (graphical user interface)

Interface: Pop-up window ( see picture files )

The module will be a basic "call sub-module" module. The librarian will be informed that the report on fines is needed the "path" to take is that of a report on overdue books as any book that is overdue will as well require a fine unless the librarian removes such by way of the modify module.

ERROR HANDLING:

Upon the calling of an improper sub-module (i.e. want search got report) the sub-module will be equipped with a "Back" button for going back to the last level. All other errors will be handled by the sub-modules.

IMPORTS:

• None.
  

EXPORTS:

The module will export a request to activate a sub-module. This would include; Call to overdue: the call is made by a request to the module as the librarian makes a click on the appropriate button on window. Call to search: the call is made by a request to the module as the librarian makes a click on the appropriate button on window.

Call to modify: the call is made by a request to the module as the librarian makes a click on the appropriate button on window. Call to print: is done by modules search and overdue.

Sub-Module:

Overdue

Interface Definitions:

Inputs to module:

• This module is called by the report on fines module through a click on a button.

Inputs by user:

• Confirm the intent of librarian to have system form report.

Outputs:

This module returns a list of the overdue books on loan by the library and any outstanding fine that remains unpaid. The return will be in the form of a report and may be viewed on the screen or printed by the librarian (see print module). The report is, at this point in time, in the form of:

• Id#
• Call#
• borrowed
• due
• returned
• amount
• any field returned could or could not be filled at this time.
  

Data Abstractions:

ID# is a positive integer number

call# is a positive integer number

borrowed is a date (see data stores for a definition)

returned is a date

due is a date

amount is a currency (see data stores for a definition)

Sub-Modules:

• None.

Design:

Environment: GUI (graphical user interface)

Interface: Pop-up window ( see picture files )

Error Handling:

• If the librarian finds themselves in the "wrong place" then there will be a button for return up one level.
• If the librarian requests a report improperly the module will prompt for a validation for the module to proceed through a text box.
• If the librarian improperly asks for a print to be done the module will prompt for a validation for the module to proceed through the use of a text box.
  

Imports:

• The module imports the reports from the data store in the previously noted form.

Exports:

• The module will export the report to either the view screen or the module print. The values of the report are exported to the print in the form of a list of reports i.e.

report #1

report #2

etc...

Sub-Module

Search

Interface Definitions:

Input to module:

• This module is called by the report on fines module by way of the action of a click on a button by the librarian using the system. The module is as well called by the modify field module to remove redundancy of work done by two separate modules.

Input by user:

• The module will take the input in the form of a field to search by way of a button pushed with a mouse. The information to be used for the search will then be input by way of a text box.

Outputs:

• The module returns a report from the data store that includes all fields in the data store or returns a not found message.

Data Abstractions:

ID# is a positive integer number

call# is a positive integer number

borrowed is a date (see data stores for a definition)

returned is a date

due is a date

amount is a currency (see data stores for a definition)

Sub-Modules:

• None.

Design:

Environment: GUI (graphical user interface)

Interface: Pop-up window ( see picture files )

The module queries the database application for the match of a given field and returns the match or matches to the librarian in a text box.

Error Handling:

Upon receiving a syntax error or an error in the input that is not the same type as the field being searched the module shall inform the librarian of the error made and ask for a correction. The module will have full allowances for the librarian to remove what he/she has typed in and replace it. The module will as well have a return to different field choice by way of click buttons and a return to calling module. The module will prompt the librarian, when the print is chosen, if they really wish a print done. (This may save paper and cost).

Imports:

• The module imports the reports from the data store in the previously noted form.

Exports:

• The module will export a report to either the screen or the print module for printing. The module returns a call by the modify module to search for the record it has been requested to modify.

Sub-Module

Modify

Interface Definitions:

Input to module:

• The module Modify is called by the module report on fines with a button click by a librarian.

Input by librarian:

• The module takes input from the librarian using it to first search for the record to be modified and then lets the librarian update the specified field by way of a text box for both of these inputs. The search input is done by use of the search module and has the same interface.

Outputs:

• The module returns to the data store an updated copy of the record and a confirmation of the changes made to the librarian.

Data Abstractions:

ID# is a positive integer number

call# is a positive integer number

borrowed is a date (see data stores for a definition)

returned is a date

due is a date

amount is a currency (see data stores for a definition)

Sub-Modules

• None

Design:

Environment: GUI (graphical user interface)

Interface: Pop-up window ( see picture files )

The module does a request to the search module with the field input by the librarian. The search module returns the report for that given field and the librarian is then prompted for the field they wish to update. When the update is done and the librarian confirms that the update is correct the module writes the report to the data store.

Error Handling:

Upon receiving a syntax error or an error in the input that is not the same type as the field being modified the module shall inform the librarian of the error made by way of a text box and ask for a correction to be entered in a text box.

The module will have full allowances for the librarian to remove what he/she has typed in and replace it( i.e. backspace to remove characters ...). The module will not allow the removal of a full record but will allow the librarian to adjust all fields except Id# to allow that a record always be there for future reference.

Imports:

• The result of the search done (a report) for the report to be modified is returned to the modify module from the search module.

Exports:

• The modified report is returned to the data store.
  

Sub-Module

Print

Interface Definitions:

Input to module:

• The print module is called by two modules the search and the overdue modules. The input to the module are the reports that it uses to format a mailing list and the necessary billing forms for the library.

Input by user:

The preference for the module to output a format for a mailing list or a billing list. There as well will be a form letter for the billing to be used if the librarian so wishes with the fields to be inserted into it. The choice will be input by way of push on buttons.

Outputs:

This data store outputs a record to the printer for the use of the librarian in this form:

• last first middle
• address
• city
• province
• code
  • For the mailing list for subsequent billing and
• title
• fee
• due
• amount
  

These are set in the form of a list and if the librarian requires a format for a mailing label or a billing letter they will be prompted and the form will be filled out and printed. The buttons to select which format and the confirmation of each step are output to the librarian.

Data Abstractions:

Id# is a positive integer number

call# is a positive integer number

borrowed is a date (see data stores for a definition)

returned is a date

due is a date

amount is a currency (see data stores for a definition)

first is a variable length string of characters denoting a first name.

last is a variable length string of characters denoting a last name.

middle is a variable length string of characters.

address is a variable length string of characters.

city is a variable length string of characters.

prov/state is a variable length string of characters.

code is a variable length string of characters.

type is an alphanumeric character.

fee is a currency

title is a variable length string of characters.

Sub-Modules:

• None

Design:

Environment: GUI ( graphical user interface )

Interface:

• The call is made to this module and the module itself does an information gathering and then sends the files created to some form of printer.
  

Error Handling:

• The lack of a correctly installed or connected printer will cause the module to send a signal back to the calling module. Upon the input of an empty field the module will output one (1) empty list, letter or mailing label.

Imports:

• All information that is handled by this module is imported from the modules overdue and search. The module then uses this information to interface with the other modules (search borrower and search book ) to acquire the needed information for a proper printout to be done. The required information is in the form of address, city, prov/state, code, first, last, middle, title and fee.

Exports:

The key fields are output to the respective search modules to help retrieve required data. These are the Id# for the borrower and the Call# for the book. The module will export the forms built to a printer for the creation of the required lists, letters and mailing labels.

Back to the Overall Design Index