You have to create a Library Borrowing System based on the following requirements:
When new books arrive, these books must be cataloged into the system by a librarian (i.e., entered in the system). Information on a book should include book ID, title, author ID, ISBN, and edition. The system should capture author names so that users can search for an author. The library may carry multiple books by the same author, and an author can have multiple books in the library system.
The library may acquire multiple copies of the same book and these copies should be recorded in the system along with their status (i.e., whether or not a copy is checked out). When someone (called a patron in library terms) borrows/returns a book, the system needs to record who has borrowed/returned what books, including the date when a copy is borrowed, the date when it is due, and the date when it is returned. Sometimes a patron reports a lost book or returns a book in a damaged condition. A librarian will then update the library catalog by removing these copies from the system and impose a fine (i.e., late fee or damage fee) on the borrower.
When someone borrows a book, the system checks the user ID printed on his or her library card to ensure that it is still valid and records the book under his or her account. It is a valid patron account if the user ID can be found in the system. Information on a borrower includes user ID, name, mailing address, phone number, and email address. There are three types of patrons: faculty/staff, student, and guest. They are all allowed to borrow multiple books at a time. Faculty and staff have an additional attribute of textbook on reserve, which captures the number of textbooks they place on reserve for their students to use within the library. Students have an additional attribute of privileges, which capture their library privileges. Guests have an additional attribute of membership fee as only the other two types of patrons can use library resources and services at no cost.
If you discover that the narrative is incomplete, make reasonable assumptions to complete the story. Supply these extra assumptions/explanations along with the solution using the space provided.
Question 29
Develop a Domain Model Class Diagram for the system. Only include the attributes that are directly relevant to this system. Do not worry about attribute types. Just include the attribute names along with class names, relationships, and multiplicities.
Domain Class Model for given requirement:
No of classes :
Multiplicitiy :
Diagram :
Get Answers For Free
Most questions answered within 1 hours.