Please describe the database design and assumptions. Develop a corresponding ER diagram

for the requirements of the database, including entities, attributes, relationships, and structural

constraints.

Books. A book should at least contain the following information: name, ISBN, author(s), subject (e.g., art, computer science, electrical engineering, history, mathematics), brief summary/description, language, publisher, date published, price, and quantity in stock Book keywords A book may have multiple keywords (e.g., health, space, drone, robot, astronaut, relational database, and NoSQL database). Users The user information should at least contain first name, middle name (if any), last name, email address, password, age, and gender. There should be at least two types of users: Managers, who can manage books, e.g., add, update, and delete books; Standard customers, who can search/explore, buy, rate, and comment books. User Ratings/Reviews. Users can provide scored ratings and descriptive reviews or comments for books. Orders. An order should at least contain the following information: book ordered, buyer, date of the order, quantity ordered, cost, order status (e.g., in process, shipped, delivered, cancelled), credit card number, billing address, and shipping address)