ER Diagram for Bookstore

The assignment for this week is to produce a database design for a bookstore.  

Think about four main activities that your database should support:

1. Searching books by authors, or authors by books.
2. Tracking the current stock of books (hint: needs only one additional attribute).
3. Ordering books from suppliers (by phone or mail).
4. Keep a catalogue of customers, including delivery addresses. 

No need to map books to customers. That means that the customer info doesn't connect with the book/supplier tables, we'll add those connections in class next week.

Your submission should be a single PDF showing a diagram that includes:

1. An ER diagram
2. Relational Vocabulary
3. Sketch of relational tables

Follow the diagramming that we have used in class.  The handout is here:  ERDiagramNotation.pdf

If you have a design question about something not covered above just go ahead and make an assumption, note it on your document and design to that assumption.  e.g., whether more than one supplier can provide a book?  Either is fine, just note which assumption you went with and design to that.  Of course feel free to write to me if that solution doesn't work for your question :)

Please work to minimize the boxes and relationships.  You don't have to (and shouldn't) track orders of books, either from customers or from the store to suppliers.  Don't use an Entity when an attribute will do and don't add relationships that can be found indirectly (e.g., Author to supplier, since suppliers might provide only some of an Author's books, so we'd get there via the Book/Title entity).

FWIW, my solution (not the only correct way of doing it) has only four Entities (but five could also make sense, if one had made another assumption).