Kindly donot forget to design the ER diagram before mapping it to relational model. You are asked

Kindly donot forget to design the ER diagram before mapping it to relational model.  

 

Transcribed Image Text:

You are asked to design the E-R diagram of a conference management system. The system manages computer science conferences including all the submissions and their details. In case of some aspects not being explicitly state, please state any assumptions that you make. Make sure that your design captures the following aspects: 1. Information about the venues (e.g., VLDB, SIGMOD). Each venue has a starting year (e.g., VLDB first conference was in 1975), and a lengthy textual description. 2. Information about the conference instances (e.g., SIGMOD'23, SIGMOD22). Each conference instance holds the conference year, location, dates and a single general chair (you can assume that a general chair can also be an author). 3. Each conference instance has one or more research areas (e.g., Query processing, Indexing, Data integra- tion). 4. Information about the authors. Each author is affiliated to an institution and has an email. 5. Information about the submissions. Each submission has one or more authors, one of them is the primary contact. The authors of a single submission are ordered (i.e., first author, second author, etc). 6. Each submission is attached to a single conference instance and has one main primary research area and one or more secondary research areas. Notice that primary/secondary research areas are drawn from the same set. You are asked to design the E-R diagram of a conference management system. The system manages computer science conferences including all the submissions and their details. In case of some aspects not being explicitly state, please state any assumptions that you make. Make sure that your design captures the following aspects: 1. Information about the venues (e.g., VLDB, SIGMOD). Each venue has a starting year (e.g., VLDB first conference was in 1975), and a lengthy textual description. 2. Information about the conference instances (e.g., SIGMOD'23, SIGMOD22). Each conference instance holds the conference year, location, dates and a single general chair (you can assume that a general chair can also be an author). 3. Each conference instance has one or more research areas (e.g., Query processing, Indexing, Data integra- tion). 4. Information about the authors. Each author is affiliated to an institution and has an email. 5. Information about the submissions. Each submission has one or more authors, one of them is the primary contact. The authors of a single submission are ordered (i.e., first author, second author, etc). 6. Each submission is attached to a single conference instance and has one main primary research area and one or more secondary research areas. Notice that primary/secondary research areas are drawn from the same set.