--Enterprise Systems Architecture and Design--

Requirements Specification for a Library Management System for Smallsville, USA

Our public library in Smallsville is in need of a computer system to help keep track of who checks books in and out, as well as to keep track of fines and print reports for us. We have been making out fine for years recording the information by hand, but Sally and Mary just dont have the handwriting they used to, especially at 72 and 81, respectively. Our new librarian, Marcus, is young and energetic, and just doesnt have the patience to keep handwritten records. As head librarian I want to be able to do more for our community than just keep track of books, so I want to be able to mail out notices of special events and the like.

Therefore, I have made note of the items I think need to be included in this system. Keep in mind that I know very little about computers, so I have probably left something out. Please feel free to make any additions or corrections that you feel are absolutely necessary. Also bear in mind that we are a small town, and do not have an unlimited budget for such a system or the training required to use it. A single PC should suffice for our needs right now, but we might want to grow to two or three, connected together, in a couple of years.

Here are the main items I feel are needed:

-Add a new library patron

-Remove a patron. Ensure that the patron has no books borrowed and no unpaid fines.

-Print a list of all patrons (in some sensible order).

-Print a list of all patrons with outstanding fines.

-Add a new book to the catalog.

-Remove a book from the catalog. Ensure no one has it borrowed.

-Record a book as lost.

-Record that a particular patron is borrowing a particular book.

-Record that someone has returned a particular book. Report any fines owing.

-Record that a patron has paid some money toward his or her outstanding fines.

-Print all overdue books, and who has them.

-Set today's date.

-Print address mailing labels

Do not attempt to provide card catalog services for allowing patrons to search for books. You may assume each book has a unique acquisition number, and you may use these numbers to refer to books borrowed and returned. For each book, record acquisition number, title, author and any other information you need to process the above commands.

For patrons include name, complete address, a unique ID number, phone number, email and any other info you need to complete the tasks

In the future we may also engage in inter-library loans with neighboring cities, and would like to consider self-check stations in the future since we have a rather small staff. Please feel free to suggest other useful and innovative technologies for future expansion.

Some Business Rules:

-patron can have 5 books and 2 AV items checked out at any given time

-Book check outs are for 2 weeks maximum with 1 renewal

-AV items can be checked out for a maximum of 2 days with no renewal

-Reference books like Encyclopedias, etc cannot be checked out from the library

-A patron with an overdue item is not allowed to check out any additional items until the overdue item is either returned or renewed

-All outstanding fines must be paid before a patron can check out additional items

-The library is not open on Sunday

-The cost for any lost books must be paid before a patron can check out additional items

-Multiple copies of the same item will have a copy number appended to the bookID (e.g. 311.02c2 would be copy 2 of the book with id 311.02)

-This library does not implement any sort of reserve or holding policy for items

Assignment

(Completed with your partner)

1-Create a UML context diagram (Level 0 Use Case Diagram) for the system

2-Create a requirements specification using the outline below for the Library Management System

Requirements Document Outline

1. Cover Page

-Problem Title, Class, Team Members

2. Introduction

-Problem Description

-Purpose of Document

-Client overview

3. Constraints

-Time Constraints

-Solution Constraints

-Environmental constraints

-Resource constraints

-Other constraints

4. Functional Requirements

-Description

-Measurement

-Acceptance criterion

5. Non-Functional Requirements

-Look and Feel

-Usability

-Performance

-Operational

-Maintainability and Portability

-Security

-Cultural and Political

-Legal