An EERM modelling exercise. Draw EERM Diagram

Scenario: a university wants to set up a database to store information about a conference it is hosting. Participants will be authors and reviewers of academic papers. Some participants will only be authors, some will only be reviewers, and some will be both. For all participants, their name and email address will be stored. In addition, the system will store the name of the organisation to which authors are affiliated, and a field of specialisation for each reviewer. A paper can have more than one author. There will be exactly one contact author for each paper (this is the author the conference will contact wrt a specific paper). Every paper has a unique id, a title and a set of keywords. Papers are reviewed by reviewers. Each paper will be reviewed by more than one reviewer, and each reviewer might review several papers. A reviewer gives every paper reviewed a rating. Reviewers have a status property that is based on the number of papers they review. This should use standard modelling constructs This should use standard modelling constructs to represent the information from the scenario, making sure that the model is complete, succinct and accurate, and does not introduce any information into the model that is not present in the scenario. Extended modelling constructs should be used where possible, and the model should show cardinalities of relationships. add constructs, where appropriate, from the EERM: these might include enhanced cardinalities, inheritance relationships, etc. Implementation Choose any two entities from your model that are connected via a many to many (m:n) relationship and show how these two entities and the relationship between them would be implemented as SQL tables. Your answer should be in the form of create table statements: you should include as many tables as you need to implement your chosen entities and their relationship. Do NOT give SQL statements to implement any other parts of your model. You should HAND DRAW the EERM diagram: