Implementation and design, Study Guides, Projects, Research of Software Engineering

Download Implementation and design and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Library Database Management System CINS

370 Project Phase II Implementation

Vicky Holcomb Nate Priddy Joseph Fitzpatrick Matthew Harris

Contents

• Problem Statement & Requirements Definition
• Conceptual Models:
  • Entity Relationship Model
  • Object Model Diagram
  • Use-Case Diagram
  • Use-Cases
• Logical Models:
  • Normalization Diagrams Relational Database Schema
  • Scenarios with Event Trace Diagrams
• Data Dictionary
• Physical Models:
  • Implementation Narrative
  • Features Summary Table
  • Menu Hierarchy
• Deployment
• Testing
• Final Remarks
• Appendices:
  • Table Definitions and Data Contents
  • User Views - Forms
  • User Views - Reports
  • SQL Statements
• Table Creation
• Stored Procedures
  • Installation Guide
  • User Manual

Responsibilities (Phase II - Implementation):

Vicky: Create tables in database, add data to database, update entity relationship model, update object model, update schema, update data dictionary, update use case diagram and statements, normalization diagrams, implementation narrative, features summary table, menu hierarchy, table definitions and data contents, testing, final remarks, some form design, and overall organization of final document.

Nate: Create tables in database, add data to database, update/add forms and reports, implementation narrative, features summary table, menu hierarchy, table definitions and data contents, screen-shots of web forms and reports, code for website and documentation for it, installation guide, testing, and final remarks.

Joseph: Create tables in database, add data to database, review problem statement/ requirements definition, update scenarios and event trace diagrams and add form/report/use case numbers to them, normalization diagrams, implementation narrative, features summary table, testing and testing narrative, and final remarks.

Matthew: Create tables in database, add data to database, PowerPoint presentation, general proofreading of entire document, implementation narrative, testing, and final remarks.

Problem Statement & Requirements Definition

We decided to create a database that can help organize a library. It is useful for any type of library, but would work best for an extensive lending library with various types of media including books, magazines, journals, videos, books on tape and more. It would be ideal for a library upgrading from a card or paper system where they have a card for each piece of media and for each customer or patron. It would also benefit a library where all employee records are still on a paper basis as well including all hire paperwork and payroll information such as salary. As you can imagine for a paper system, it makes figuring out how many books are overdue, or how many people owe fees, take quite a while to figure out for the employees. Patrons also have no control over the system. The only thing they can do is use the card catalog to find media.

The purpose of this database is to automate and replace the current card and paper system. All tasks previously recorded on paper or cards will be integrated into the new system. The most important change will be to the checkout process. Theoretically, computers with barcode scanners will be available to the librarians or employees (we use the term librarian and employee interchangeably). The librarians will be able to issue new library cards that come with a unique barcode and number for easy checkout to patrons. All media would be receiving a barcode with their individual unique identifying number as well. With the barcodes, the librarians will simply be able to scan a membership card and the media's barcode to check it out to the patron, thereby eliminating the need for cards. Since we do not have scanners to use, for this project, we will be hand entering library card numbers and barcode numbers. The database will be able to keep track of who has what checked out. The ability to keep track of that information will also provide a variety of new reporting capabilities. For example, based on due dates, librarians can run reports to see who has late books (checked out media report), who owes fees for late books or damaged books (cost report) and much more. It will only take a few seconds to run the report as opposed to going through all of the cards by hand, saving the librarians hours a week.

The library patrons will also have added usability. Potentially there could be computers in the library for their use to see what books they currently have checked out, and what they have checked out in the past. The information they could view would be limited, as in they would have a different set of permissions than the employees. They would need their unique identification number to use the system. They would also be able to search the library's media by author, title, and subject. Because the system is linked to the one that the librarians will be using, they will also be able to see if the media is currently available for checkout. The last main feature that would be new to patrons is that they would have web access to the library to

Conceptual Models:

Entity Relationship Model

Object Model Diagram

Use-Cases

Use case 1: Log in to system Actor(s): Patron, Librarian, Library Manager Description: First screen anyone sees is the logon screen. At this screen they will enter their username and password and click "Login". After the system has verified the user they will be taken to the main menu screen appropriate to their access level.

Use case 2: Add a Patron Actor(s): Librarian, Library Manager Description: Employee will be prompted with the menu screen. After choosing “Add a Patron”, they will enter in the first and last name, address, city, state, zip code, and phone number. When the user clicks Generate the patron will be given a login, password, and a Library Card Number. After clicking create they will be entered into the database

Use case 3: Update User Information Actor(s): Patron, Librarian, Library Manager Description: They will be prompted with the menu screen. After choosing “Administration/Patron”, they will search for the patron by the Patron's Library Card number or name. From here they can view patron details. In the popup they will then enter in the new changes for the customer. After clicking button “update”, the patron's information will be updated.

Use case 4: Reserve Media Actor(s): Patron, Librarian, Library Manager Description: In home the user will search for the book. When they click view details a popup window will open allowing them to view information about the book. From here the user clicks “reserve”. If the user is a patron it will insert the reservation into the database and close the popup window. Otherwise the user will select the library card number from a list and then click “reserve”.

Use case 5: Check out Media Actor(s): Librarian, Library Manager Description: Librarian or Library Manager on the home page will search for the media by title, author, or barcode. From here they click “view details” this will show relevant information about the media. At the bottom of the popup the user can click “check out”. This redirects the user to the checkout screen where they select the checkout date. To be returned date is automatically calculated based on the policies table at this point. The user then clicks checkout and the media is now checked out.

Use case 6: Check in Media Actor(s): Librarian, Library Manager Description: Employee at home searches for the media to be checked in, clicks “view details” and then “check in”.

Use case 7: Renew Media Actor(s): Librarian, Library Manager Description: Employee will search for media on the homepage. From here the employee can click “View Details” which will pop open details about the media. Then the user clicks “Check In”. On the next page the user will select a check-in date and select “yes” under the renewed radio box. When the user clicks “check in” the next to be returned date will be calculated and the book will be renewed.

Use case 8: Search for Media Actor(s): Patron, Librarian, Library Manager Description: Employees and Patron home allows for searching by title, author, ISBN, and media type. From here the user can click “View Details” and view the media information.

Use case 9: Remove Damaged Media Actor(s): Library Manager Description: Library Manager will select from the menu Administration/Media. Then the user will search for the media. Then the user can click delete which will remove the damaged media.

Use case 10: Make a Payment Actor(s): Librarian, Library Manager Description: Employee will search for media/view details and click “check in”. If there is a fee calculated the screen will display a drop down with payment type and payment amount and check-in date. After the employee enters the payment amount they can click “Pay Fine” and the media will be checked in and paid for.

Use case 11: Add Media Actor(s): Library Manager, Librarians Description: Librarian or Library Manager accesses the area from Administration/Media they then click “Add New Media”. The media details will popup allowing the user to enter Title, Barcode, Year, ISBN, Subject, Publisher, Initial Condition, Media Type, Order Cost, and the First Author. Once they click create the media will be entered into the database.

Use case 12: Run Overdue Media Report Actor(s): Librarian, Library Manager Description: User will access report by going to Reports/ Overdue Media Report. From here the User clicks “Export” and the report will be generated in a PDF form to the user.

Logical Models:

Relational Database Schema

Normalization Diagrams

0