ooo T-Mobile Wi-Fi 8:22 PM 2%) learn.vccs.edu Project Scenario Management of a local public library is interested in updating their technology systems. As part of this nitiative, they wish to redesign their database system into one that is more usable and that better reflects the things they are interested in tracking. The library's management has asked you to design a relational database to support their efforts The management of the library wants to keep track of the following things in their database: TITLES: Management wants to track each tle available to be loaned, along with the author or authors, and the original year the title was published. BOOKS: Each physical book that is available to be loaned must also be tracked. The difference between a title and a book is that each book cormesponds to a single title. However, the lbrary may have several books of the same title that may be loaned to customers. For example, the Iibrary would track The Hunger Games as an available title, and they would also track the 5 physical copies of the book that can be loaned. Data we must track for each book includes the corresponding title, the name of the publishing company, the edition number of the book, and the year it was published AUTHORS: Each author of a title must be tracked. We must keep track of the name of the author, the date the author was born, and the date the author deceased, if applicable CUSTOMERS: Each customer is identified by his or her library card number. We must also track the customer's name, address, gender, birthday, phone number, and email address. LOANS: Every time a book is loaned to a customer, we track the day and time it was loaned, along with the day the book is due. FINES: Customers who do not retun a book before the due date may be fined. Each fine is associated with a particular loan, along with the amount of the fine. When a fine is paid, we also include the day and time the fine was paid. Project Components Part 1: Data Model-30% of project total Students will create a data model for the project scenario. The data model will be an Entity Relationship Diagram, showing all entities and relationships. The relationships must also include maximum and minimum cardinalties. This must be submitted as a Microsoft Word document or as a PDF Part 2: Database Design-30% of project total Using the Entity Relationship Diagram created in Part 1, students will create a Database Design. The design must include al primary keys, surrogate kbeys, loreign keys, and alternate keys. Also, data types must be defined for each column, and any columns that cannot have blank values must be identified with a "NOT NULL constraint. Additional data constraints may also be noted