| VoidWorks Software Inc. Overall Design Complete Document |
Springfield Library would like to thank VoidWorks Software Inc. for their proposal for a library management system. While it appears most of our customer and book management requirements have been met, we seek further clarification with regard to the Overall Design Document.
Before negociating a final contract, there are several issues we need to have
addressed:
Specific areas of concern have also been annotated in red, italicized font throughout this document.
|
| Summary |
| Module Definitions |
| The module definitions described in this document are set out as follows: |
|
| Data Stores |
The data stores we have implemented for this system are as follows:
|
The following data stores will be implemented if there is a need to
be constantly modifying the information contained within them - otherwise
that information will be hardcoded into the system
|
|
| Overview |
| The Book Admininstration module will have a window displaying five main features, which buttons will be assigned to implement its certain task. There will be 'Add Book', 'Add Book Copy', 'Delete Book Copy', 'View Book', 'View Book Copy' buttons, and a QUIT button to do none of the above tasks. The 'Add Book' button will take the user to a window where the user can add a book. Similar with 'Add Book Copy' but the user will be adding a book copy instead. 'Delete Book Copy' will display another window that allow the user to delete a book copy. 'View Book' button will allow the user to view and/or modify book information. 'View Book Copy' button will alow the user to view and/or modify a book copy. |
| Data Flow Diagrams |
| These are clickable imagemaps. |
| Level 1 |
| Level 2 |
| Add a Book |
| Inputs |
How are keywords delimited? This will be important to the data entry clerks. Which "three" of Book, CD, CD-ROM, Film, Laserdisk and Journal will be included in the pull-down menu? Since all six of these media types are currently used in our library, it is essential for them all to be listed as menu options. |
Title, Author, Publisher and Category should be case-sensitive.
| Outputs |
| Upon acceptance and verification of the book data the book will be added to the database. |
We will need verification from the system to tell us when transactions are OK.
| If an unrecoverable error (such as read write errors to the database) occurs the module will output the error code to the error handling module. |
What happens if there is a read/write error to the database? Will the database be in the same state as before the error occured? Should this kind of error be reported to an administrator?
| A unique call number will be automatically generated by the system for the book. |
| Number of copies will be automatically set to one by the system once the book has been added. |
| Imports |
| From automatic generator |
|
| NOTE: The automatic generator will generate a unique integer for the call number for that particular book. The value will be in sequential order ranging from 0 - 999999999. The number of copies will be set to 1 when the book is originally added. |
| Error conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field. (All necessary fields must be complete) |
| Book already exists in the database. |
| Description |
|
| Walkthrough |
| The user fills in the appropriate data into the data fields and presses the 'ADD' button. If there is an error in one or more of the fields or the ISBN number is already in use, these errors are displayed in an error window once the ADD button has been pressed. Once all errors are corrected (if there were any), the ADD button is pressed to add the new book to the database. If at any time the user wishes to leave, clicking on the QUIT button will exit them from the 'Add Book' window. |
| Add Book Copy |
| Inputs |
|
| Outputs |
| Upon acceptance and verification of the ISBN number, the following will be display in a window: ISBN #, title, author, publisher, subject, book category, media type, cost of book, version, edition. |
| If an unrecoverable error (such as read write errors to the databse) occurs the module will output the error code to the error handling module. |
| Imports |
From Books data store
|
From automatic generator
|
| NOTE: The automatic generator will generate a unique integer for the call number for that particular book. The value will be in sequential order ranging from 0 - 999999999. The number of copies will be set to 1 when the book is originally added. |
| Error conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field. (ISBN number not specified.) |
| Book does not exist in database. |
| Description |
|
| Walkthrough |
| The user fills in the ISBN number of the book that he/she wants to add a book copy to and presses the 'OK' button. If there is an error with the syntax of the ISBN number or the ISBN number cannot be found in the database, these errors are displayed in an error window. Once all errors are corrected (if there were any), the 'OK' button is pressed at which time the data for the book that will have a copy added is displayed. The user then preoceeds to enter in data for the appropriate fields and presses the 'ADD' button. If there are any errors with the data added, this will be displayed in an error window. Once all errors are corrected (if there were any), pressing the 'ADD' button will add the book copy to the database. If, at any time, the user wants to leave, clicking on the respective QUIT or CANCEL buttons will exit them from the window. |
| Delete a Book Copy |
| Inputs |
|
| Outputs |
| Upon acceptance and verification of the ISBN number, the following will be display in a window: ISBN #, title, author, publisher, subject, book category, media type, cost of book, version, edition, call number, location, floor, circulation status, due date (if any), and customer number (if any). Once a user accepts to proceed with the book's deletion, the book will be removed from the database. |
| If an unrecoverable error (such as read write errors to the database) occurs the module will output the error code to the error handling module. |
| Imports |
From Books data store
|
From loans data store
|
From customer data store
|
| Error conditions |
| Syntax error on input to the call number field. |
| Input missing from field. (Call number not specified.) |
| Book does not exist in database. |
| Book is out on loan or is on hold. |
| Description |
|
| Walkthrough |
| The user fills in the call number of the book that he/she wishes to delete and presses the 'Delete' button. If there is an error with the syntax of the call number or the call number cannot be found in the database, these errors are displayed in an error window. Once all errors are corrected (if there were any), the DELETE button is pressed at which time the data for the book to be deleted is displayed, and the the user is asked whether the deletion should proceed. If the user selects the 'YES' button, the book will be permanently removed from the database. If the user wants to go back without deleting the book, the 'NO' button should be pressed. If, at any time, the user wishes to leave, clicking on the QUIT button will exit them from the 'Delete Book' window. |
| View a Book |
| Inputs |
|
| Outputs |
| Upon acceptance and verification of the ISBN number, the following will be display in a window: ISBN #, title, author, publisher, subject, book category, media type, cost of book, version, edition, call number(s), location(s), floor(s), circulation status(es). |
| If an unrecoverable error (such as read write errors to the databse) occurs the module will output the error code to the error handling module. |
| Imports |
From Books data store
|
| Error conditions |
| Syntax error on input to the ISBN number field. |
| Input missing from field. (ISBN number not specified.) |
| Book does not exist in database. |
| Description |
|
| Walkthrough |
| The user fills in the ISBN number of the book that he/she wishes to view. If there is an error with the syntax of the ISBN number or the ISBN number cannot be found in the database, these errors are displayed in an error window. Once all errors are corrected (if there were any), the VIEW button is pressed at which time the data representing that ISBN number is displayed. From there, the user may choose to modify and save the data (see section 4(a) Modifying a Book). Clicking on any QUIT button will exit the user from the window he/she is in. |
| a) Modify a Book |
| Inputs |
|
| (Note: ISBN # was already entered as an input from previous module - View a Book) |
| Outputs |
| Upon acceptance and verification of the book data the book information will be modified and saved to the database. |
| If an unrecoverable error (such as read write errors to the databse) occurs the module will output the error code to the error handling module. |
| Imports |
| none |
| Error conditions |
| Syntax error on input to the cost field. |
| Input missing from field. |
| Description |
|
| Walkthrough |
| The user clicks on the 'MODIFY' button, thus allowing the user to edit/modify book information. The user then can modify the appropriate data of the data fields and press the 'SAVE' button. If there is an error in one or more of the fields these errors are displayed in an error window once the 'SAVE' button has been pressed. Once all errors are corrected (if there were any), the 'SAVE' button is pressed once again to save/update any changes made of the book information into the database. If at any time the user wishes to leave, clicking on the QUIT button will abort the modification of book information. |
| View Book Copy |
| Inputs |
|
| Outputs |
| location, floor, circulation status |
| Upon acceptance and verification of the call number, the following will be display in a window: ISBN #, title, author, publisher, subject, book category, media type, cost of book, version, edition, call number(s), location(s), floor(s), circulation status(es). |
| If an unrecoverable error (such as read write errors to the databse) occurs the module will output the error code to the error handling module. |
| Imports |
From Books data store
|
From loans data store
|
From customer data store
|
| Error Conditions |
| Syntax error on input to the call number field. |
| Input missing from field. (call number not specified.) |
| Book copy does not exist in database. |
| Description |
|
| Walkthrough |
| The user fills in the call number of the book that he/she wishes to view. If there is an error with the syntax of the call number or the call number cannot be found in the database, these errors are displayed in an error window. Once all errors are corrected (if there were any), the VIEW button is pressed at which time the data representing that call number is displayed. From there, the user may choose to modify and save the data (see section 5(a) Modifying a Book Copy). Clicking on any QUIT button will exit the user from the window he/she is in. |
| a) Modify Book Copy |
| Inputs |
|
| (Note: call number was already entered as an input from previous module - View Book Copy) |
| Outputs |
| Upon acceptance and verification of the book data the book copy information will be modified and saved to the database. |
| If an unrecoverable error (such as read write errors to the databse) occurs the module will output the error code to the error handling module. |
| Imports |
| None |
| Error conditions |
| Syntax errors on inputs to the fields with required formats. (i.e. invalid number range for floor number) |
| Input missing from field. |
| Description |
|
| Walkthrough |
| The user clicks on the 'MODIFY' button, thus allowing the user to edit/modify the book copy information. The user then can modify the appropriate data of the data fields and press the 'SAVE' button. If there is an error in one or more of the fields these errors are displayed in an error window once the 'SAVE' button has been pressed. Once all errors are corrected (if there were any), the 'SAVE' button is pressed once again to save/update any changes made of the book copy information into the database. If at any time the user wishes to leave, clicking on the QUIT button will abort the modification of the book copy information. |
|
| Data Flow Diagrams |
| These are clickable image maps. |
| Level 1 |
| Level 2 |
| Add Customer Module |
| Input |
First and Last names should be case-senstive. Maximum books defaults to twenty five books per customer. The default value can be modified by the supervisor, not the customer. Maximum fine defaults to ten dollars per customer. The default value can be modified by the supervisor, not the customer. |
| Outputs |
| Upon acceptance and verification of the customer data the customer will be added to the database. |
| If an unrecoverable error (such as read write errors to the database) occurs the module will output the error code to the error handling module. |
| Recoverable errors (such as duplicate customer) will be dynamically handled by this module through user interaction. |
| Error Conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field. (all fields must be complete) |
| Customer already exists in the database. |
| A change to the default values for Max Books, Max Fines or Restricted with out the valid supervisor password. |
| Hardware error is an unrecoverable error that will be processed by the error module. |
| Description |
|
| Walkthrough |
| The librarian inputs all of the customer's information in the appropriate fields. The librarian selects the 'Add' button to add this customer to the database. If there is a duplicate name in the database, the librarian can shrink the results list by inputting additional information for other fields (such as phone number) and then pressing the 'Search' button. By looking at the duplicate names list, the librarian can decide to continue to add the customer by pressing the 'Yes' button or discontinue by pressing the 'No' button. If the librarian modified restricted information, the approval of a supervisor will be required. |
| Search Customer |
| Inputs |
|
| Outputs |
| If an unrecoverable error (such as read write errors to the database) occurs the module will output the error code to the error handling module and discontinue the process. |
| With success, a list (also displayed on this screen) of the exact matches to the input criteria. This list will contain the First and Last Name and Telephone number. |
| Selecting an entry from the list (either by single click on the entry and then pressing the select button or by double clicking on the entry) will display the View/Update customer screen with the selected entry filled in. |
| Error Conditions |
| Hardware error is an unrecoverable error that will be processed by the error module. |
| Format errors in fields that impose a structure on the input. |
| Description |
|
| Walkthrough |
| Librarian enters the search criteria in the appropriate fields following the correct format. Librarian clicks on the 'Search' button. Search will return a list that matched the criteria. Librarian can either double click an entry or single click and then select 'Select' to display the View/Update screen. If the Librarian selects another entry the View/Update screen will be refreshed. To print or save the list the librarian need only select the appropriate button. When Finished the user selects 'Quit'. |
| View/Update |
| Inputs (obtained from the Search Customer module) |
|
| Outputs |
| Upon acceptance and verification of the customer data the customer will be modified in the database. |
| If an unrecoverable error (such as read write errors to the database) occurs the module will output the error code to the error handling module. |
| Recoverable errors (no modifications made) will be dynamically handled by this module through user interaction. |
| Error Conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field. (all fields must be complete) |
| A change to the default values for Max Books, Max Fines or Restricted with out the valid supervisor password. |
| Hardware error is an unrecoverable error that will be processed by the error module. |
| Modify requested with no changes made. |
| Description |
| The View/Update module will allow the librarian to look at and or modify the customers last name, first name, phone number, address, city, province, postal code, country, max books and max fines. The user will also see all of the books that the selected customer has on load or on hold and be able to print this along with all of the information about the customer. The user will also be able to permanently remove a customer from the database. |
| Buttons present: UPDATE, PRINT, SAVE, REMOVE, QUIT |
|
| Walkthrough |
| The user selected a customer from the search customer screen. The librarian then modifies whatever information they choose conforming to the appropriate format for each field. The user clicks on the "Update" button. The customer's information is updated. The librarian then decides (strangely) to delete the customer by clicking on the "Remove" button. The librarian confirms the request by clicking on the "Yes" button. The customer is removed from the database, never to be seen again... |
| Supervisor Approval |
| Inputs |
| Supervisor password and the message to display. |
| Outputs |
| Confirmation that the approval was successful or not. |
| Errors |
| None |
| Description |
| A small window will pop up and display the message that was
supplied to this module.
There is a field where the supervisor can enter the supervisor
password.
Buttons Present: OK, QUIT |
|
| Walkthrough |
| The supervisor types in an incorrect supervisor password and clicks on the 'OK' button. The system displays the error message and the user can now choose to either retry typing in the password or quit by pressing the 'Quit' button. The supervisor types in the correct supervisor password and clicks on the 'OK' button. The window closes and control is returned to the calling module proceeds. |
|
| Data Flow Diagrams |
| These are clickable image maps. |
| Level 1 |
| Level 2 |
| Borrowing a Book |
| Inputs |
|
| Outputs |
| Upon accepting the input, a message will be displayed to inform the Librarian that the command was successful. This brings up another window on the screen, prompting the Librarian to either print a report of the transaction and exit, or to simply |
| Error Handling |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from a field (both inputs must be completed). |
| Invalid input: the User ID Number doesn't exist in the database. The Librarian will have the option of automatically adding the Customer to the database, by pressing the ADD NEW button. |
| Invalid input: the Call Number doesn't exist in the database. The Librarian will be prompted to re-enter the Call Number into the text box. |
| The Customer is not allowed to borrow a book. A message will appear informing the Librarian of this action, and the transaction will be exited. |
| Description |
|
| Walkthrough |
| The Librarian inputs the Customer's ID and the Call Number, then selects the 'OK' button to process the inputs.
If the Customer is not a member of the Library System, the Librarian simply presses the ADD NEW button, and the Customer
is automatically added to the database without leaving this process.
If the transaction fails to complete to due the Customer having too many fines, or is not allowed to borrow books for any other reason, a message is displayed to the Librarian, explaining this, and the process will be canceled, returning the Librarian to the "Transaction Administration" window. If the transaction was a success, the Librarian will be prompted to print a report of the transaction by pressing the PRINT button, or to exit by pressing the CANCEL button. By pressing the PRINT button, a report containing the following information will be printed:
Pressing the CANCEL button will return the Librarian to the "Transaction Administration" window. Pressing the CANCEL button at any time will end the current operation, and exit the module. |
| Returning A Book |
| Input |
|
| Outputs |
| This module updates book copy's circulation status on the database. Then the Book Holder's information is displayed on the screen, via a new pop-up window, or sent to a printer. |
| Error Handling |
| Syntax error on inputs to the call number field |
| Invalid Input: call number does not exist in database or does not match the borrowed book |
| Description |
|
| Walkthrough |
| When the user enters the Call Number in the text-box and presses the OK button, and the database is updated by setting
the object as available for loan. The customer's information is then retrieved from the database, and displayed to the Librarian.
The Librarian then has the option to print out this information, in case there is anything pertinent that the customer should
know.
Pressing the CANCEL button will return the Librarian to the "Transaction Administration" window. Pressing the CANCEL button at any time will end the current operation, and exit the module. As well, pressing the HELP button at anytime during the current module, will display appropriate information designed to aid the user. |
| Renewing A Book |
| Inputs |
|
| Outputs |
| This module updates book copy's circulation status and due date on the database. Then the Book Holder's information is displayed on the screen, via a new pop-up window, or sent to a printer. A Report of Borrower information, and book information |
| Error handling |
| Syntax error on inputs to the call number field |
| Invalid Input: call number does not exist in database or does not match the borrowed book |
| Description |
|
| Walkthrough |
| When the user enters Call Number in the text-box and presses the OK button then this module accesses the database and checks
if the given book is on hold. If it is not on hold, then the due date for the Book Copyis updated in the database, and a message
is displayed saying that the book copy has been successfully renewed. As well, the Librarian can print out a report of the
book copy's information once the book has been renewed by pressing PRINT REPORT.
If it is on hold, then the Book Copy's status is changed to available for loan, and a message is displayed, saying the Book Copy cannot be renewed. Pressing the CANCEL button will return the Librarian to the "Transaction Administration" window. Pressing the CANCEL button at any time will end the current operation, and exit the module. As well, pressing the HELP button at anytime during the current module, will display appropriate information designed to aid the user. |
| Putting A Book On Hold |
| Inputs |
|
| Outputs |
Upon accepting the two inputs, a message will be displayed to inform the Librarian that either the hold on the book is successful or has failed because of the following reasons (only one of them will be displayed):
|
| Errors Conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field (both inputs must be completed). |
| Invalid inputs: the Call Number or the User's ID Number doesn't exist in the database. |
| Description |
|
| Walkthrough |
| The Librarian inputs the Customer's ID and the Call Number of the book; then selects the 'OK' button to process the inputs. If the message box says that the hold cannot be placed, the Librarian can select the CANCEL button to cancel the operation and quit, or the CLEAR button to clear the contents in the text entry field and start the process over again. If the messages box tells that the operation is successful, the Librarian can either select the PRINT button to print a report on the held book, or CANCEL button to quit, or CLEAR button to start over from step 1 for another hold. |
| Canceling Books On Hold |
| Inputs |
|
| Outputs |
| Upon accepting the two inputs, a message will be displayed to confirm that the canceling of the book is successful or has failed because of invalid inputs. |
| Errors Conditions |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from field (both inputs must be completed) |
| Invalid inputs: the given Call Number or the User's ID Number doesn't exist in the data base. |
| Description |
|
| Walkthrough |
| The Librarian inputs the Customer's ID and then the Call Number of the book, which is provided by the Customer or obtained from the list generated after the List button is clicked.
The Librarian clicks on 'OK' button to process the cancel request. If the message box says that the request has failed, the Librarian can select the CANCEL button to cancel the operation and quit, or the CLEAR button to clear the contents in the text entry field and start the process from step 1 over again. If the messages box says that the operation is successful, the Librarian can either select the PRINT button to print a report on the held book, or the CANCEL button to quit, or CLEAR button to start over from step 1 for another hold cancel. |
| Paying A Fine |
| Inputs |
|
| Outputs |
| Upon accepting the two inputs, a message will be displayed to inform the Librarian that the command was successful, and the Fine amount will be decreased on the Customer's account. |
| Error Handling |
| Syntax errors on inputs to the fields with required formats. |
| Input missing from a field (both inputs must be completed). |
| Invalid inputs: the User ID Number doesn't exist in the database. |
| Description |
|
| Walkthrough |
| The Librarian inputs the Customer's ID and the Fine Amount to be Paid, then selects the 'OK' button to process the inputs.
If a message says that the operation could not be performed, the Librarian can select the CANCEL button to cancel the operation and quit this process, or the CLEAR button to clear the contents in the text entry fields and start the process over. If a message states that the operation was a success, the Librarian can either select the PRINT button to print a report on the Fine Amount to be Paid, or the CANCEL button to quit this process. |
|
| Entity Relationship Diagram |
|
| Top Level Data Flow Diagram |
|
| Data Dictionary |
** Books Database **
Book = @ISBN Number + Title + Author + Publisher + Subject + Book Category
+ Media Type + Cost of Book + Version + Edition + Number of Copies
* Entity; represents a book residing in the library. *
ISBN Number = String
* Key attribute for Book. Consists of a 10 digit number in the form *
* D-DD-DDDDDD-D where D is a number from 0-9. Each ISBN number is *
* is unique to an instance of Book. *
Title = String
* Non-key attribute for Book. Represents the title of the book, with *
* a maximum of 150 characters. *
Author = String
* Non-key attribute for Book. Contains the author of the book, in the form *
* Last Name, First Name *
* If there are multiple authors, they are separated by semicolons. Maximum *
* length is 120 characters. *
Publisher = String
* Non-key attribute for Book. Contains the publisher of the book, with a *
* maximum length of 150 characters. *
Subject = String
* Non-key attribute for Book. This is a description of the subject *
* book, to be used as a search term in the database. Maximum length *
* is 100 characters. *
Book Category = ["Overnight" | "Two Week Loan" | "Reserved" ]
* Non-key attribute for Book. Used for determining the length of time a book *
* can be borrowed, or if it can be taken out at all. *
Media Type = ["Book" | "CD" | "CD-ROM" | " Film" | "Laser-disk" | "Journal" | "Cassette" ]
* Non-key attribute for Book. Describes the format of the item. *
Cost of Book = currency
* Non-key attribute of Book. Contains a dollars and cents value of the Book, *
* representing the price one would be charged for replacement of the item. *
Version = real
* Non-key attribute of Book. This is not a required attribute for book, but is *
* only used if the item in question has a version number. It is in the form
* DDD.DD where D ranges from 0 - 9. Version thus ranges from 0 - 999.99
Edition = real
* Non-key attribute of Book. Similar to Version, in that it is not a required *
* attribute, and only applies if the item has an edition number. It is in the *
* form DDD.DD where D ranges from 0 - 9. Edition thus ranges from 0 - 999.99. *
Number of Copies = integer
* Non-key attribute of Book. Represents the number of copies that of the *
* item in question. Used in creating instances of the Book Copy weak entity, *
* whose definition follows. Ranges from 0 - 999. *
Book Copy = @Call Number + ISBN Number + Location + Floor + Circulation Status
* Weak Entity associated with Book. Each instance of Book can have zero or more *
* instances of Book Copy. Represents a copy of an item in the library. *
Call Number = integer
* Key attribute of Book Copy. Represents the unique number to identify *
* each copy of an item in the library. Each time an instance of Book Copy *
* is created, the next available number is assigned to Call Number. *
* Call Number can range from 0 - 999999999. *
ISBN Number = string
* Non-key attribute of Book Copy. This is the same as the ISBN Number for the *
* instance of Book associated with this instance of Book Copy. *
Location = string
* Non-key attribute of Book Copy. Represents the name of the library location *
* where this particular copy is residing. Maximum 20 characters. *
Floor = integer
* Non-key attribute of Book Copy. Represents the floor number of Location at *
* which the copy is located. This number ranges from 0 - 99. *
Circulation Status = [ "On Loan" | "Overdue" | "On Hold" | "Available" |
"Out of Circulation" ]
* Non-key attribute of Book Copy. Represents the current status of the copy in *
* question, and used for decisions on some functions acting on a Book Copy. *
** Customer Database **
Customer = @User ID + Last Name + First Name + Phone + Address + City
+ Province + Country + Postal Code + Category + Fine
+ Max Books + Max Fine + Restricted
* Entity; represents customers that have membership in the library. *
User ID = integer
* Key attribute for Customer. It is created when the customer is *
* registered for a membership. It is unique. *
Last Name = String
* Non-Key attribut for Customer. Represent the customer's last name. *
* Length should be between 1 and 60. *
First Name = String
* Non-Key attribut fro Customer. Represent the customer's first name. *
* Length should be between 1 and 40. *
Phone = String
* Non-key attribute for Customer; represent the customer's phone number. *
* Standard North American phone number. (3 digit area code) 3 digit local *
* exchange-4 digit number. The 3 digit area code is optional. The length *
* should be between 8 to 14. *
Address = String
* Non-key attribute for Customer; represent the customer's address include *
* Apartment number, street, P.O.Box. Length should be between 1 to 80. *
City = String
* Non-Key attribute for Customer; represent the city of the Customer's *
* mailing address. Length should be between 1 to 20. *
Province = String
* Non-Key attribute for the Customer; represent the province/state of the *
* Customer's mailing address. It should be exactly 2 characters. *
Country = String
* Non-Key attribute for the Customer; represent the country of the *
* customer's mailing address. The maximum length is 10 characters. *
Postal Code = String
* Non-Key attribute for the Customer; represent the postal code of the area *
* the customer's mailing address. The Maximum Length is 11 characters. *
Category = ["regular" | "librarian" | "supervisor"]
* Non-Key attribute for the Customer; represent the customer type. Extra *
* category can not be added. *
Fine = currency
* Non-Key attribute for the Customer; represent the current fine that the *
* customer has. Two digits following decimal point should be stored (to *
* represent dollars and cents). *
Max Fine = currency
* Non-Key attribute for the Customer; represent the maximum fine that the *
* customer can have . This can only be modified by a user with supervisor *
* category. *
Max Books = integer
* Non-Key attribute for the Customer; represent the maximum number of books *
* that the customer can borrow. This can only be modified by a user with *
* supervisor category. *
Restricted = ["yes" | "no"]
* Non-Key attribute for the Customer; represent whether or not the customer *
* can borrow. It becomes "yes" when the customer's fines exceed the *
* maximum amount allowed. *
** Holds Database **
Hold = @User ID + @Call Number + Hold Date
* Entity; represent the book that is on hold by the customer with the *
* User ID. *
Call Number = real
* Key attribute for the Hold entity and Bookcopy entity; represent the call *
* number of the book that is on hold. This is a unique number that is *
* created after the book is added to the Book's database. *
Hold Date = integer
* Non-Key attribute for the Hold entity; represent the date that the book *
* is put on hold. *
** Loans Database **
Loans = @User ID + @Call Number + Loan Date
* Entity; represent the books that are borrowed by the customer with the *
* specified User ID. *
Loan Date = integer
* Non-Key attribute for the Loans entity; represent the date that the book *
* is borrowed. *
*********************
User ID and Call Number has been defined.
*********************
** Fines Database **
Fines = @User ID + Fine + Date
* Entity; represent the Fine situation of the Customer with the specified *
* User ID. *
Date = integer
* Non-Key attribute for the Fines entity; represent the date that the fine *
* has been added or subtracted. *
************************
User ID and Fine has been defined above.
************************
** Circtype Database **
Circtype = @Kind
* Entity; represent the enumerated Circulation that the user can enter. *
Kind = String
* Key attribute for Circtype entity; stores the new circulation value when *
* user entering a Bookcopy. *
** Custtype Database **
Custtype = @Kind
* Entity; represent the enumerated Category that the user can enter. *
Kind = String
* Key attribute for Custtype entity; stores the new category value when *
* user entering a Customer. *
** Loctype Database **
Loctype = @Kind
* Entity; represent the enumerated Location that the user can enter. *
Kind = String
* Key attribute for Loctype entity; stores the new location value when *
* user entering a Book. *
** Medtype Database **
Medtype = @Kind
* Entity; represent the enumerated Media Type that the user can enter. *
Kind = String
* Key attribute for Custtype entity; stores the new media type when *
* user entering a Book. *
** Subjtype Database **
Subjtype = @Kind
* Entity; represent the enumerated Subject that the user can enter. *
Kind = String
* Key attribute for Medtype entity; stores the new subject value when *
* user entering a Book. *
Send mail to the Group Leader
or the Webmaster
Back to the Main Page