PLZ help with the following: using Oracle sql or Oracle SQL live

Problem Statement

We will assume that the Computer Science Department at a University has an agreement with the publishers to allow faculty and students to have free exclusive access to the e-books online through the Vanier website. They need you to design a database for them using the following business rules:

The faculty and students (we refer to them in our system as clients) can electronically check out any book at any time. A book must have at least one author but can have more authors. An author must have written at least one book or more to be included in the system. A book may have never

been checked out, but can be checked out many times by the same client or different clients over time. A client may have never checked out a book or they may have checked out many books over time. To simplify determining which client currently has a given book checked out, a M:N relationship between BOOK and CLIENT should be maintained. The information recorded for each book is book number, book title, book subject, and year of publication. For each author, the library records the author ID, first and last name and year of birth. Because all faculty and

students in the department are given accounts at the online library, the client ID, first and last name and client type need to be stored. Finally, checkout out date, checkout due date and checkout in date for each book must be tracked.

Starting from this general description, do the following initial steps in your database design process. However, you are free to make any reasonable assumptions that will help you to develop your ERD diagram.

1. Create a Crows Foot ERD. Draw YOUR entity relationship diagram (ERD) to indicate entities, relationships, connectives, and resolve M:N relationships.

2. Translate your ER diagram into a relational schema in the form of SQL DDLs. Choose appropriate data types for each attribute and include primary key and foreign key constraints, Check and Not Null constraints.

3. Populate every relation with sufficient representative rows (at least 4 for each table).