Consider a conference review system database (exercise problem from your textbook) in which researchers submit their res

[answerhappygod]

Consider a conference review system database (exercise problem
from your textbook) in which researchers submit their research
papers for consideration. The database system also caters to
reviewers of papers who make recommendations on whether to accept
or reject the paper. The data requirements are summarized as
follows:
Authors of papers are uniquely identified by their email id.
Their first and last names are also recorded.
Papers are assigned unique identifiers by the system and are
described by a title, an abstract, and a file name containing the
actual paper.
Papers may have multiple authors, but one of the authors is
designated as the contact author.
Reviewers of papers are uniquely identified by their email id.
Their first and last names are also recorded.
Each paper is assigned between two and four reviewers. The
reviewers rate the paper assigned to them on a scale of 1 to
10.
Each review contains two types of written comments: one to be
seen by the review committee only and the other by the author(s) as
well.
Include:
Design Entity-Relationship diagrams for the conference review
database and enter the design using any data modeling tool. Be sure
to identify entities, key attributes, mapping cardinalities,
participation constraints, and so on. You are free to make any
reasonable additional assumptions (as long as they do not conflict
with any stated requirements.), and if you do, you need to list
them in your document.
Identify any constraints that were given in the specifications
but you were unable to capture using ER modeling constructs. State
them in natural language (plain English). Also, for each
constraint, give a brief explanation of why you need the constraint
and why you cannot express it in the ER schema.