Summary and Goals

My final project aims to develop a comprehensive database system to efficiently manage and organize a library$$s book collection. The system I am proposing will also allow patrons to view available books and check their rental status through a website or kiosk interface. It will also track customer information, such as names, emails, and unique IDs, to manage book checkouts and returns. Those are my expected goals that I will try to fulfill by the end of this course.

I hope this is a good proposal idea for my final project. I thought it could be good because I have a large personal physical library at my apartment that I could use to fill out the database.

The primary objective of the proposed library database system is to organize and track all books in the library, making it easier for patrons to browse available titles and manage rentals. This system will enable users to check book availability through a website or kiosk, enhancing the library experience and also helping to take stress off of the employees checking out books. Walking through a library that's filled wall to wall with books and trying to find the right one can be very intimidating, this system can help ease some of that burden as well. Additionally, by tracking customer information $($name$,$ email, and unique ID$),$ the system will provide insights into the borrowing patterns and preferences of people using our library, helping the library to understand and cater to the community's reading interests. The system is meant to be user$-$friendly for both library staff and patrons, facilitating efficient management and usage of the library's resources, which will help the library function more smoothly.

Class $1$ Name

Book

Attribute $1$

bookID$($Primary Key$)$

Attribute $2$

Title

Attribute $3$

Author

Attribute $4$

Genre

Attribute $5$

availabilityStatus

Primary Key Attribute

bookID

Class $2$ Name

Customer

Attribute $1$

customerID

Attribute $2$

firstName

Attribute $3$

lastName

Attribute $4$

email

Attribute $5$

phone

Primary Key Attribute customerID

Class $3$ Name

Rental

Attribute $1$

rentalID

Attribute $2$

bookID$($Foreign Key referencing book$)$

Attribute $3$

customerID $($Foreign Key referencing customer$)$

Attribute $4$

rentalDate

Attribute $5$

dueDate

Attribute $6$

dateReturned

Primary Key Attribute

Relationship $1$

Customer rents Book. $(1..$n$)$

Relationship $2$

Book is included in rental. $(1..$n$)$

Relationship $3$

Rental links customer and book. $(1.\mathrm{.}1)$

$1)$ For the proposed database problem, create a high$-$level use case diagram using Lucidchart.com and paste a screenshot of the finalized use case diagram here. The use case diagram should clearly depict the Actors and the identified use cases. At a minimum, three use cases need to be identified.

Paste a screenshot of your proposed use case diagram

$2)$ For each of the identified use cases from the above Use Case Diagram, write a brief description.

$3)$For the proposed database problem, create a detailed class diagram using Lucidchart.com.

At a minimum, each class diagram should have the following:

$4$ attributes clearly defined

Identify the primary candidate key

If the class is related to another class, identify the candidate foreign key

Cardinality relationship to another class

Relationships should be named.

Relationships should be identified from one of the following

$1..$n $[1-$to$-$Many$]$

$0..$n $[0-$to$-$Many$]$

$1.\mathrm{.}1[1-$to$-1]$