Need help with writing ERD's from the business rules in the document.

UR Published U R Published is a printing house that helps produce and market books of fiction for unknown authors. It uses a review process to select manuscripts for publication. Only about 20 percent of the manuscripts submitted are accepted for publication. Accepted manuscript summaries are included in an issue of the newsletter, printed each quarter. Ruby Danbury, owner and head editor since 2007, has become overwhelmed with tracking the authors, manuscripts, and dates; there are many steps to track a manuscript from the date it is first submitted, to the acceptance date, to the publish date. The Excel spreadsheet that was initially created has gotten out of control; reviewers are modifying data they should not have access to, dates are not entered in a timely manner resulting in many forgotten dates, and authors are not notified immediately when their submission is rejected - many authors end up calling to receive the status of their manuscript, sometimes months after it has reached the "dead manuscript" pile. Ruby has hired your team to build a database. The first step is to create a complete ERD to support the business needs and people involved as described below Unsolicited manuscripts are submitted by authors. When a manuscript is received, Ruby will assign the manuscript a number, and record some basic information about it in the system. The title of the manuscript, the date it was received, genre (code) and a manuscript status of "received" are entered. Information about the author(s) is also recorded. For each author, an identification number, the author's name, mailing address, city, state, zip, e-mail address, and phone are recorded. Every manuscript must have an author. Only authors that have submitted manuscripts are kept in the system. It is typical for a manuscript to have several authors. A single author may have submitted many different manuscripts to the journal. Additionally, when a manuscript has multiple authors, it is important to record the order in which the authors are listed in the manuscript credits. At her earliest convenience, Ruby will briefly review the topic of the manuscript to ensure that the manuscript's contents fall within the scope of the company. If the content is not within the scope, the manuscript's status is changed to "rejected", the date is recorded, and the author is notified via e-mail; the date the email is sent is also recorded. If the content is within the scope of the company, then Ruby selects three or more reviewers to review the manuscript. Reviewers will read manuscripts to ensure the validity of the topics and the edit potential of the content. For each reviewer, the system records a reviewer number, OUTPUT The following are some outputs that Ruby will want you to develop. Use them to guide your design for this milestone. These must be included in your final deliverables. Create your own samples based on your client's business to thoroughly test your database design. reviewer name, reviewer e-mail address, office phone, and areas of interest (genre code). Areas of interest are pre-defined areas of expertise that the reviewer has specified. An area of interest is identified by a genre code and includes a description (e.e. G2103 is the code for "mystery", G2125 is the code for "Thriller" and so on). Genres appropriate for VR Published include thriller, mystery, crime, horror, fantasy, sci-fi, political, action, and western. A reviewer can have many areas of Interest, and an area of interest can be associated with many reviewers. All reviewers must specify at least one area of interest. It is unusual, but it is possible to have an area of interest for which the company has no reviewers. Ruby will change the status of the manuscript to under review and record which reviewers the manuscript was sent to and the date on which it was sent to all reviewers. A reviewer will typically receive several manuscripts to review each year, although new reviewers may not have received any manuscripts yet. The reviewers will read the manuscript at their earliest convenience and provide feedback to the editor regarding the manuscript. The feedback from each reviewer includes rating the manuscript on a 10-point scale for character development, plot, structure, and style, as well as a recommendation for publication (accept or reject). The editor will record all of this information in the system for each review received from each reviewer and the date that the feedback was received. Once all of the reviewers have provided their evaluation of the manuscript, the editor will decide whether or not to publish the manuscript. If the editor decides to publish the manuscript, the manuscript's status is changed to accepted" and the date of acceptance for the manuscript is recorded. If the manuscript is not to be published, the status is changed to "rejected" following the same process stated above. Once a manuscript has been accepted for publication, it must be scheduled for an announcement in the next newsletter. For each issue of the newsletter, the publication period (Fall, Winter, Spring, or Summerl, publication year, volume, and issue number are recorded. An issue will contain many manuscript summaries, although the issue may be created in the system before it is known which summaries will go in that issue. An accepted manuscript summary appears in only one issue of the newsletter. Each summary goes through a typesetting process that formats the summary content font, font size, line spacing, justification, etc.). Once the manuscript summary has been typeset, the number of pages that the summary will occupy is recorded in the system. The editor will then make decisions about which issue each accepted manuscript summary will appear in and the order of manuscript summaries within each issue. The order of appearance and the beginning page number for each summary must be stored in the system. Once the manuscript summary has been scheduled for an issue, the status of the manuscript is changed to scheduled. Once an issue is published, the print date for the issue is recorded, and the statuses of all of the manuscripts in that issue are changed to "newsletter." 1. All manuscripts titles and genre descriptions that have been accepted for publication. 2. Names of all reviewers and the manuscript titles that they rejected. 3. Names of reviewers accepting the most manuscripts for each genre. Include the genre description in the output. 4. Authors who have submitted more than one manuscript. 5. Authors who have had more than one manuscript rejected, 6. Titles of all manuscripts that are currently under review. 7. Titles of summaries that have been published in a newsletter. Include the newsletter period, year, and volume. List in the order the summary appeared in the newsletter 8. For cach interest area, list first and last names of all authors and all reviewers who have the same interest area. 9. First author names, genre, and number of submissions for each genre. 10. What is the number of summaries printed for each issue? Include the date. 11. How many manuscripts are under review for each genre that have not been accepted yet? 12. Which genre has had the most rejections? UR Published U R Published is a printing house that helps produce and market books of fiction for unknown authors. It uses a review process to select manuscripts for publication. Only about 20 percent of the manuscripts submitted are accepted for publication. Accepted manuscript summaries are included in an issue of the newsletter, printed each quarter. Ruby Danbury, owner and head editor since 2007, has become overwhelmed with tracking the authors, manuscripts, and dates; there are many steps to track a manuscript from the date it is first submitted, to the acceptance date, to the publish date. The Excel spreadsheet that was initially created has gotten out of control; reviewers are modifying data they should not have access to, dates are not entered in a timely manner resulting in many forgotten dates, and authors are not notified immediately when their submission is rejected - many authors end up calling to receive the status of their manuscript, sometimes months after it has reached the "dead manuscript" pile. Ruby has hired your team to build a database. The first step is to create a complete ERD to support the business needs and people involved as described below Unsolicited manuscripts are submitted by authors. When a manuscript is received, Ruby will assign the manuscript a number, and record some basic information about it in the system. The title of the manuscript, the date it was received, genre (code) and a manuscript status of "received" are entered. Information about the author(s) is also recorded. For each author, an identification number, the author's name, mailing address, city, state, zip, e-mail address, and phone are recorded. Every manuscript must have an author. Only authors that have submitted manuscripts are kept in the system. It is typical for a manuscript to have several authors. A single author may have submitted many different manuscripts to the journal. Additionally, when a manuscript has multiple authors, it is important to record the order in which the authors are listed in the manuscript credits. At her earliest convenience, Ruby will briefly review the topic of the manuscript to ensure that the manuscript's contents fall within the scope of the company. If the content is not within the scope, the manuscript's status is changed to "rejected", the date is recorded, and the author is notified via e-mail; the date the email is sent is also recorded. If the content is within the scope of the company, then Ruby selects three or more reviewers to review the manuscript. Reviewers will read manuscripts to ensure the validity of the topics and the edit potential of the content. For each reviewer, the system records a reviewer number, OUTPUT The following are some outputs that Ruby will want you to develop. Use them to guide your design for this milestone. These must be included in your final deliverables. Create your own samples based on your client's business to thoroughly test your database design. reviewer name, reviewer e-mail address, office phone, and areas of interest (genre code). Areas of interest are pre-defined areas of expertise that the reviewer has specified. An area of interest is identified by a genre code and includes a description (e.e. G2103 is the code for "mystery", G2125 is the code for "Thriller" and so on). Genres appropriate for VR Published include thriller, mystery, crime, horror, fantasy, sci-fi, political, action, and western. A reviewer can have many areas of Interest, and an area of interest can be associated with many reviewers. All reviewers must specify at least one area of interest. It is unusual, but it is possible to have an area of interest for which the company has no reviewers. Ruby will change the status of the manuscript to under review and record which reviewers the manuscript was sent to and the date on which it was sent to all reviewers. A reviewer will typically receive several manuscripts to review each year, although new reviewers may not have received any manuscripts yet. The reviewers will read the manuscript at their earliest convenience and provide feedback to the editor regarding the manuscript. The feedback from each reviewer includes rating the manuscript on a 10-point scale for character development, plot, structure, and style, as well as a recommendation for publication (accept or reject). The editor will record all of this information in the system for each review received from each reviewer and the date that the feedback was received. Once all of the reviewers have provided their evaluation of the manuscript, the editor will decide whether or not to publish the manuscript. If the editor decides to publish the manuscript, the manuscript's status is changed to accepted" and the date of acceptance for the manuscript is recorded. If the manuscript is not to be published, the status is changed to "rejected" following the same process stated above. Once a manuscript has been accepted for publication, it must be scheduled for an announcement in the next newsletter. For each issue of the newsletter, the publication period (Fall, Winter, Spring, or Summerl, publication year, volume, and issue number are recorded. An issue will contain many manuscript summaries, although the issue may be created in the system before it is known which summaries will go in that issue. An accepted manuscript summary appears in only one issue of the newsletter. Each summary goes through a typesetting process that formats the summary content font, font size, line spacing, justification, etc.). Once the manuscript summary has been typeset, the number of pages that the summary will occupy is recorded in the system. The editor will then make decisions about which issue each accepted manuscript summary will appear in and the order of manuscript summaries within each issue. The order of appearance and the beginning page number for each summary must be stored in the system. Once the manuscript summary has been scheduled for an issue, the status of the manuscript is changed to scheduled. Once an issue is published, the print date for the issue is recorded, and the statuses of all of the manuscripts in that issue are changed to "newsletter." 1. All manuscripts titles and genre descriptions that have been accepted for publication. 2. Names of all reviewers and the manuscript titles that they rejected. 3. Names of reviewers accepting the most manuscripts for each genre. Include the genre description in the output. 4. Authors who have submitted more than one manuscript. 5. Authors who have had more than one manuscript rejected, 6. Titles of all manuscripts that are currently under review. 7. Titles of summaries that have been published in a newsletter. Include the newsletter period, year, and volume. List in the order the summary appeared in the newsletter 8. For cach interest area, list first and last names of all authors and all reviewers who have the same interest area. 9. First author names, genre, and number of submissions for each genre. 10. What is the number of summaries printed for each issue? Include the date. 11. How many manuscripts are under review for each genre that have not been accepted yet? 12. Which genre has had the most rejections