2) (30 points) Consider a CONFERENCE REVIEW database in which researchers submit their research ection process. The papers for consideration. Reviews by reviewers are recorded for use in the paper sel database system database system caters primarily to reviewers who record answers to evaluation uestions for each paper they review and make recommendations regarding whether to accept or reject the paper. The data requirements are summarized as follows: Authors of papers are uniquely identified by email is. First and last names are also recorded. Each paper is assigned a unique identifier by the system and is described by a title, abstract, and the name of the electronic file containing the paper. .A paper may have multiple authors, but one of the authors is designated as the contact author. Reviews of papers are uniquely identified by email address. Each Reviewer's first name, last name, phone number, affiliation, and topics of interest are also recorded. Each paper is assigned between two and four reviewers. A reviewer rates each paper assigned to him or her on a scale of 1 to 10 in four categories: technical merit, readability, originality, and relevance to the conference. Finally, each reviewer provides an overall recommendation regarding each paper. Each review contains two types of written comments: one to be seen by the review committee only and the other as feedback to the author(s). Design an Entity-Relationship diagram for the CONFERENCE-REVIEW database, and draw an ER diagram for that schema. Specify key attributes of each entity type and structural constraints on each relationship type. Note any unspecified requirements, and make appropriate assumptions to make the specification complete