System and Problem for a Library Management System 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 he wants to be able to do more for our community than just keep track of books, so he wants to be able to mail out notices of special events and the like. Therefore, he has made note of the items he thinks need to be included in this system. Keep in mind that he knows very little about computers, so he has probably left some things 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 that are needed: a. Add a new library patron and be able to edit their basic information b. Remove a patron. Ensure that the patron has no books borrowed and no unpaid fines before deleting them. Provide notice appropriately. c. Print a list of all patrons (in some sensible order). d. Print a list of all patrons with outstanding fines. e. Add a new book to the catalog. Be able to edit basic book info. f. Remove a book from the catalog. Ensure no one has it borrowed. Notify appropriately and do not delete if out. g. Record a book as lost. h. Record that a particular patron is borrowing a particular book. i. Record that someone has returned a particular book. Report any fines owing and update patron account. j. Record that a patron has paid some money toward his or her outstanding fines. k. Print all overdue books, and who has them. l. Print address mailing labels Do not attempt to provide card catalog services for allowing patrons to search for books, although we may want to expand the system later to include this capability with multiple stations. 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: 1. A patron can have 5 books and 2 AV items checked out at any given time 2. Book check outs are for 2 weeks maximum with 1 renewal 3. AV items can be checked out for a maximum of 2 days with no renewal 4. Reference books like Encyclopeidias, etc cannot be checked out form the library 5. A patron with an overdue item is not allowed to check out any additiona litems until the overdue item is either returned or renewed 6. All outstanding fines must be paid before a patron can check out additional items 7. The library is not open on Sunday 8. The cost for any lost books must be paid before a patron can check out additional items 9. 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) 10. This library does not implement any sort of reserve or holding policy for items

Design for Smallsville Library Management System For this homework assignment you will create a design for the Smallsville Library Management System. The user-provided specifications are provided in a separate document. You must use the Transaction Pattern discussed in class and used in the in-class example as the basis for your design and future implementation. Your design should include the following. 1. Description of all data elements used in a table form as shown in example 2. A class diagram of the entities in the system This will be broken into two parts. 1) a class diagram showing just the relationships and multiplicities, and 2) blocks showing the attributes and methods for each class in the first part. Examples will be provided in class 3. State diagrams for any relevant state variables. There will be at least one for the Book class and one for the Patron class for a minimum of 2 diagrams. Examples in class 4. A discussion of the approach you will take to implement the system. How will you implement collections? (no STL allowed at this time) How will you handle limitless expansion? 5. Any outstanding questions or issues you may have about the system 6. A discussion of how you can design now to incorporate future plans and expansion. You will turn in a PDF file with the above discussions and diagrams to the Homework 3 dropbox in BB Learn. Everything should be included into A SINGLE PDF. You may want to explore online UML Tools to build your diagrams Some suggestions are: ArgoUML The UML templates in Microsoft Visio LucidChart SmartDraw UMLet Be sure that whatever tool you use, you save your diagrams as JPG or PDF so that you can import them into your single PDF to turn in. For this first design, and the subsequent implementation in HW 4, you can ignore the presence of the AV items and any rules pertaining to those. Your design should remain flexible so that these can be incorpated in future designs and implementations (i.e HW 5 and 6) Sample Data Elements table Item Name Type Used by Description STName String Student class Holds the name of a student CrsNum Integer Course class Holds the course number for a particular course