Please submit the report for the GROUP DB DEVELOPMENT EXERCISES.
PART 1: Create and normalize the ERD diagram created in Week 5 using a database platform of choice. Evidence of the database output must be submitted as a hard copy screenshot AS WELL AS access to the system your group is completing the activities in. Preference is to access the system via Azure or AWS. There are education accounts available for free. (16 Points)
PART 2: Provide evidence of how you can insert, update, and select data in the system by providing SQL queries on how to complete the following activities: (4 Points)
Insert a Record into the Database
Select one record using attributes including author name, ISBN, and book title.
Select multiple records using attributes including author, publisher, and date of publication.
Update a record (or series of records) including the author’s name, description of the text, rating of user, and rating comments.
PART 3: In your assigned groups. all groups will work on the same overall project, but each group will have its own instance of the project data and will build a separate and unique interface to its instance. Please answer the following questions:
(.5 points) Please write the name of the project group and identification of all users.
(.5 points) The domain/website access location of your database application. (Note: Just write a one- two-sentence description of the overall context or situation that your application is a part of).
(1 points) Write a couple of other “value-added” facilities your system could support if you had the ability to grow the ERD Diagram and technology in the future.
(3 Points): Group Member responsibilities/activities in the overall project development
E-R Diagram is drawn based on the below requirements:
ou will work with book information, user information, ratings of books, and users’ social network.
Each book has an id, title, publication date, publisher, ISBN, functional category, page count, price (publisher), and product description
There are 3 categories of book: fiction, non-fiction, and specialty.
An author can write one or more books.
An author can also be associated with one or more publishers.
An author’s book can have one or more editions.
A publisher can have many authors and many books.
Many ISBNs can also be associated with a given publisher but only one ISBN per book.
An author can write many books.
The book can have one or more editions.
There can be one or more formats to a given book series.
A book can be associated with many authors.
UCBooks needs to keep track of user ratings for each book and author (e.g., 1-5 and 1 for ‘Dislike’, to 5, for ‘Awesome!’).
A particular user rates a particular book at a given time.
A user CANNOT rate the same multiple times unless there are multiple editions of the book.
Each edition can be rated separately. Each user who submits a rating will be identified by a unique id and has a name, gender, age, and location. Nothing is anonymous.
There is also the social network between users. Users can send communication requests (i.e. instant messages/emails) to other users. Such requests can be accepted or ignored.
Once accepted, the two users are considered ‘book buddies.’ If ignored, the user can send the request again.
We want to add a store when the requests were sent (timestamp), the result of the requests and when the request was answered (timestamp).