Reference no: EM132238639

Please build an Entity Relationship Diagram that includes cardinality, foreign keys, specialization and any attributes. Use the following information:

• A local school needs your help designing a database to keep track of books and the students that check the books out. Each book has a unique ISBN, as well as a title and year that the school would like to track. The school keeps track of each student name and email address. In addition, the school keeps track of book publishers and authors, and the name and address of each.
• The school also tracks the two types of publishers: academic and fiction. If a publisher is academic, they cannot be fiction and vice versa. The school adds a student to the database after they check out a book, and they can check out multiple books at a time. A book can be checked out by multiple students but might never have been checked out. When a book is added to the database, its author and publisher are added as well. A book must have at least one author and if an author is in the database, he or she must be associated with a book. Each book may be written by multiple authors and each author may have written many books. A single publisher may have published many books, but each book has only one publisher. If a publisher is in the database, they must be associated with a book.