Part I - Modeling You are building a database for a comic book store customer management system. Given the database specification below, your job is to turn the specification into an ER diagram. Your notation must be consistent with the notation used in our lecture notes. You can use all constructs and notations discussed in our lecture notes and nothing else (i.e.. oven notations used in the textbooks but not in our lectures cannot be used). Your ER diagram should capture all the information and constraints in the specification but, at the same time, be minimal. It means that redundant entities, relationships, attributes and constraints should be avoided. You may use any drawing tool of your choice (for example, Dia, diagrams.net, Lucidchart, etc.) to draw your ER diagram. Hand drawings will not be accepted. Database Specification The database keeps information about comic books, customers, orders, inventory and reviews. First, the database should include information about all comic books available at the store. In addition to a unique id, each book has a title, publisher, issue number, cover price and one or more authors who authored the comic. You can assume the ids of books and authors are unique. Each series of books has a name and consists of one or more comic books (also referred to as issues). The comics in a series are ordered. The database must keep track of the store's inventory of comics, including the number of copies of each book in stock and the location of those copies in the store. It is always possible to find all copies of the same book on a single shelf. Each customer has a customer id and a full name. Customers can make orders, and each order has a date and includes one or more comic books. Each order belongs to a single customer. Orders must be kept on file even when a customer's data is not available anymore. Customers can review comic books. Each review can be made public or private. Each review has a date, number of stars (1 to 5), title and detailed description. The system must ensure that the customer really bought the comic book they reviewed, so each review must have a corresponding order. After a new review is added, an average rating for the reviewed comic book is recalculated and stored in the database