Question: 85 Web Security Conference: You Are Setting Up The Database For A Web Secu- Rity Conference. A “participant Is Defined To Be A Person Who Is Involved In The Conference In Any Way. You Have Decided To Identify Each Partici- Pant By His Or Her E-mail Address. For Each Participant, You Also Want To Store The Following Contact Information: Last/family Name, …

85 Web security conference: You are setting up the database for a web secu- rity conference. A “participant is defined to be a person who is involved in the conference in any way. You have decided to identify each partici- pant by his or her e-mail address. For each participant, you also want to store the following contact information: last/family name, first given name, additional/middle name, work affiliation, address information, and phone number awy Each presentation at the conference has a single speaker, who must be a participant. A participant is sometimes permitted to be the speaker for more than one presentation. Each presentation may also have an indefi, nite number of co-authors, who should also be participants. It is possible to be a co-author for more than one presentation, and the speaker for one presentation might be a co-author for another presentation. Each presen- station may be given only once and has a title and an abstract. Presentations are grouped into sessions; a session typically contains three presentations, but the number may vary. Each session has a title and also a chairperson, who must be a participant. Most sessions also have an organizer, who is also a participant. Typically, the organizer and the chair- person are the same person, but that is not always the case. A person may organize or chair more than one session. Other data pertinent to a session are its time slot and room. Time slots are identified by a two-letter code for example, “MB” indicates the second session on Monday. For each time slot, you want to store a description; the description for “MB” might be “Monday 10:30 AM-12:00 PM”. Rooms have a unique room code like “B203”, a room name, a description, and a seating capacity. Several sessions may happen at the same time (in different rooms). Design a normalized database that will store all this information. Draw an ER diagram, and write a database design outline. You may add “ID” fields where necessary.