Introduction

Bookster is a new online bookstore wants to create a database to help with their business. The requirements for the database are:

The database should store information about the books, authors, publishers, customers, and orders.

Each book has a unique ISBN, a title, a price, a category, and a rating. A book can have one or more authors, and belongs to one publisher.

Each author has a unique ID$,$ a name, a bio, and a photo. An author can write one or more books.

Each publisher has a unique ID$,$ a name, a contact person, a phone number, and an address. A publisher can publish one or more books.

Each customer has a unique ID$,$ a name, an email, a password, a phone number, and an address. A customer can place one or more orders.

Each order has a unique ID$,$ a date, the book ordered, and a shipping method. If you like, you can design a database that supports multiple books per order but it is not necessary $($one book per order is okay$).$

The database should follow our guidelines around normalization, data integrity, and referential integrity.

Complete the following database design document. This part of the exercise is worth $60\%$ of the marks.

Entity Relationship Diagram

Insert an ERD showing the database entities and their relationships. You may wish to use Miro to draw your diagram or PowerPoint or any other drawing software of your choice.

Table Map

Expand your ERD diagram into a full table map that also shows the fields $($including key fields$).$ Update your relationships to connect at the right fields.

Data Dictionary

Create a data dictionary for each table. The first one is started for you. Add additional rows to it for the remaining fields. Then, add a data dictionary for each of the remaining entities.

Customer Table

Field Name

Field Type

Size

Properties

Customer$\_$ID

Autonumber

Primary key.

Last$\_$name

Text

$20$

First$\_$name

Text

$20$