How do you turn this into a relational database schema?

A private book collector is designing a database to keep track of her purchases and book holdings. Consider the entity set Book with attributes title, author, publisher, pubDate, numberPages, condition, cost,and datePurchased.

a. Show how the entity set and its attributes would be represented on an E-R diagram.

b. Describe the domain of the cost attribute, making assumptions as needed

c. Identify a superkey for the Book entity set.

d. Identify all candidate keys for the entity set.

e. Identify a primary key for the entity set and underline it on the E-R diagram

a. Assume that in the same scenario as in Exercise 3.2, there is an entity set called Purchase with attributes purchaseDate, totalAmount, and any others you wish to add to describe book purchases. A purchase may include several books. Show how this entity set and its relationship to Book would be represented on the E-R diagram.

b. Stating any necessary assumptions, make a decision about the cardinality and participation constraints of the relationship, and as appropriate symbols to the E-R diagram.

c. Assume there is another entity called Seller to be added to the diagram. The book collector makes purchases from many sellers, but each purchase is made from one seller. Making up attributes as needed, add this entity and appropriate relationship(s) to the diagram.

Book: Database Illuminated Chapter 4