. . Instructions: Individual effort only - you cannot give or receive help from anyone but Dr. Morris Must be drawn in LucidChart - other solutions will not be accepted for any credit Must be drawn using crow's foot notation as demonstrated in class and in the textbook Must be neat and professional in appearance Submit in D2L before the due date Remove the description box to the right of the diagram in LuddChart so that only your data model remains before you save to an image. Set LucidChart to "Crop to Content when saving as an image to improve the readability of your image. Do NOT take a screen shot of the diagram in Lucid Chart -save it as an image, then insert it into the Word document Submit as a MS Word document containing the LucidChart diagram. The diagram should be "Crop to Content" in LucidChart and saved as an image, then inserted into the Word document. The Business Research Organization supports the dissemination of new research in various business disciplines. One of its annual conferences, Business Rescarch Academic Conference (BRAC), focuses on academic issues in business. The organization needs a database to track the presentations that will be given during a meeting of the conference. Researchers submit presentations for consideration for being included in the conference. While the proposals go through an extensive review process, that is not part of this system and no data related to the review and decision process needs to be tracked in this database. Only submissions that are accepted for presentation will be included in this system. Only the following data and activities need to be supported: For each accepted presentation, the name of the presentation, length (in minutes), and the date it is submitted for consideration must be stored in this system. Additionally, the date that the researchers were notified that it was accepted for presentation at the conference should also be stored in this system. For each researcher, their name, affiliation, and email address should be recorded in the system. Researchers often try to make the most of their investment in attending the conference by participating in many different ways. For example, a researcher can have multiple presentations at the conference. Many presentations are co-authored by multiple researchers. Every presentation must be associated with at least one researcher. For presentations with multiple authors, it is important to track the order in which the authors are listed in the presentation authorship (eg., first author, second author, etc.). BRAC divides the presentations into different tracks based on having a similar topic. There are nearly two dozen tracks offered during the conference, such as Accounting Professional, Marketing, and Class Techniques tracks. Each track has a name and starts on a particular date. Most tracks have presentations spread over three days, but not all of them. Therefore, in addition to the starting date, the ending date of the track should also be recorded. Within each track, the presentations Ire organized into different presentation sessions. A session is a named collection of presentations that will occur together in the same location. Every presentation will belong in only one session. The session names are just a way for conference participants to distinguish the different sessions. Sessions are always scheduled for 90 minutes. The session start date and time need to be recorded, as well as the session location. The location is just the name of the hotel conference room that the session will be held in BRAC divides the presentations into different tracks based on having a similar topic. two dozen tracks offered during the conference, such as Accounting Professional, Marketing, and Class Techniques tracks. Each track has a name and starts on a particular date. Most tracks have presentations spread over three days, but not all of them. Therefore, in addition to the starting date, the ending date of the track should also be recorded. Within each track, the presentations are organized into different presentation sessions. A session is a named collection of presentations that will occur together in the same location. Every presentation will belong in only one session. The session names are just a way for conference participants to distinguish the different sessions. Sessions are always scheduled for 90 minutes. The session start date and time need to be recorded, as well as the session location. The location is just the name of the hotel conference room that the session will be held in. For example, the Classroom Techniques track has six sessions scheduled. One of those sessions is the "Online Classroom Techniques Morning Session 1" and is going to be held in the hotel's "Presidential Conference Room" on June 12 starting at 10am. There are five presentations scheduled to be given during that session. Also on June 12, the Information Systems Technologies track is having the "Big Data Innovation" session starting at 10am in "Ballroom B" of the hotel. This session has six presentations scheduled for it. Recall that this system does not track the original submission and review process for presentations. A presentation is added to this system and assigned a session at the same time so there is never a situation in which a presentation will be in the system without being associated with a session. Similarly, a session must always be a part of a track. It is possible, however, for the users to specify the tracks in the system before they specify the sessions that will be a part of that tract. It is also possible for the data about a session to be entered before specifying the presentations that will be a part of that session. In some instances, if the organizers of the event find that they are assigning too many presentations to a specific session, they may create a new session and move some of the presentations from the old session to the new session. It is not necessary to track the history of such movements, only the current assignment of presentations to sessions, but this is another reason why it is possible for a session to exist before specifying which presentations will belong to it. For each track, there is one researcher that is designated as the track chairperson. Every track must have a chairperson, and the track can only have one chairperson. The track chairperson is responsible for organizing the presentations into different sessions and dealing with any conflicts or questions that For example, the Classroom Techniques track has six sessions scheduled. One of those sessions is the "Online Classroom Techniques Morning Session 1" and is going to be held in the hotel's "Presidential Conference Room" on June 12th starting at 10am. There are five presentations scheduled to be given during that session. Also on June 12th, the Information Systems Technologies track is having the Big Data Innovation" session starting at 10am in "Ballroom B" of the hotel. This session has six presentations scheduled for it. Recall that this system does not track the original submission and review process for presentations. A presentation is added to this system and assigned a session at the same time so there is never a situation in which a presentation will be in the system without being associated with a session. Similarly, a session must always be a part of a track. It is possible, however, for the users to specify the tracks in the system before they specify the sessions that will be a part of that track. It is also possible for the data about a session to be entered before specifying the presentations that will be a part of that session. In some instances, if the organizers of the event find that they are assigning too many presentations to a specific session, they may create a new session and move some of the presentations from the old session to the new session. It is not necessary to track the history of such movements, only the current assignment of presentations to sessions, but this is another reason why it is possible for a session to exist before specifying which presentations will belong to it. For each track, there is one researcher that is designated as the track chairperson. Every track must have a chairperson, and the track can only have one chairperson. The track chairperson is responsible for organizing the presentations into different sessions and dealing with any conflicts or questions that come up with scheduling the sessions. Each session also has a researcher that is the session chairperson. Every session must have a chairperson, and the session can only have one chairperson. The sessions chairperson acts as the host during the session by calling the session to start, introducing each presentation, and providing some concluding remarks at the end of the session. A researcher may be attending the conference just to make one or more presentations. A researcher may be attending the conference as a track chairperson and/or session chairperson. As such, a researcher may be a chairperson of a track or session and not be making any presentations, or they could be a chairperson and make many presentations. A researcher is not required to chair either a session or a track. If a person chairs a track, they can chair only one track. A person can chair multiple sessions. For example, Samantha Tickle chairs the Information Systems Tehnologies track. Samantha also chairs the "Big Data Innovations" session. However, Samantha is not doing any presentation at the conference. Roland Tumble is chair of the "Online Classroom Techniques Morning 1" session and chair of the "Online Classroom Techniques Afternoon 2" session. In addition, Roland is presenting research during the "Flipped Classroom Strategies" session on a different day. . . Instructions: Individual effort only - you cannot give or receive help from anyone but Dr. Morris Must be drawn in LucidChart - other solutions will not be accepted for any credit Must be drawn using crow's foot notation as demonstrated in class and in the textbook Must be neat and professional in appearance Submit in D2L before the due date Remove the description box to the right of the diagram in LuddChart so that only your data model remains before you save to an image. Set LucidChart to "Crop to Content when saving as an image to improve the readability of your image. Do NOT take a screen shot of the diagram in Lucid Chart -save it as an image, then insert it into the Word document Submit as a MS Word document containing the LucidChart diagram. The diagram should be "Crop to Content" in LucidChart and saved as an image, then inserted into the Word document. The Business Research Organization supports the dissemination of new research in various business disciplines. One of its annual conferences, Business Rescarch Academic Conference (BRAC), focuses on academic issues in business. The organization needs a database to track the presentations that will be given during a meeting of the conference. Researchers submit presentations for consideration for being included in the conference. While the proposals go through an extensive review process, that is not part of this system and no data related to the review and decision process needs to be tracked in this database. Only submissions that are accepted for presentation will be included in this system. Only the following data and activities need to be supported: For each accepted presentation, the name of the presentation, length (in minutes), and the date it is submitted for consideration must be stored in this system. Additionally, the date that the researchers were notified that it was accepted for presentation at the conference should also be stored in this system. For each researcher, their name, affiliation, and email address should be recorded in the system. Researchers often try to make the most of their investment in attending the conference by participating in many different ways. For example, a researcher can have multiple presentations at the conference. Many presentations are co-authored by multiple researchers. Every presentation must be associated with at least one researcher. For presentations with multiple authors, it is important to track the order in which the authors are listed in the presentation authorship (eg., first author, second author, etc.). BRAC divides the presentations into different tracks based on having a similar topic. There are nearly two dozen tracks offered during the conference, such as Accounting Professional, Marketing, and Class Techniques tracks. Each track has a name and starts on a particular date. Most tracks have presentations spread over three days, but not all of them. Therefore, in addition to the starting date, the ending date of the track should also be recorded. Within each track, the presentations Ire organized into different presentation sessions. A session is a named collection of presentations that will occur together in the same location. Every presentation will belong in only one session. The session names are just a way for conference participants to distinguish the different sessions. Sessions are always scheduled for 90 minutes. The session start date and time need to be recorded, as well as the session location. The location is just the name of the hotel conference room that the session will be held in BRAC divides the presentations into different tracks based on having a similar topic. two dozen tracks offered during the conference, such as Accounting Professional, Marketing, and Class Techniques tracks. Each track has a name and starts on a particular date. Most tracks have presentations spread over three days, but not all of them. Therefore, in addition to the starting date, the ending date of the track should also be recorded. Within each track, the presentations are organized into different presentation sessions. A session is a named collection of presentations that will occur together in the same location. Every presentation will belong in only one session. The session names are just a way for conference participants to distinguish the different sessions. Sessions are always scheduled for 90 minutes. The session start date and time need to be recorded, as well as the session location. The location is just the name of the hotel conference room that the session will be held in. For example, the Classroom Techniques track has six sessions scheduled. One of those sessions is the "Online Classroom Techniques Morning Session 1" and is going to be held in the hotel's "Presidential Conference Room" on June 12 starting at 10am. There are five presentations scheduled to be given during that session. Also on June 12, the Information Systems Technologies track is having the "Big Data Innovation" session starting at 10am in "Ballroom B" of the hotel. This session has six presentations scheduled for it. Recall that this system does not track the original submission and review process for presentations. A presentation is added to this system and assigned a session at the same time so there is never a situation in which a presentation will be in the system without being associated with a session. Similarly, a session must always be a part of a track. It is possible, however, for the users to specify the tracks in the system before they specify the sessions that will be a part of that tract. It is also possible for the data about a session to be entered before specifying the presentations that will be a part of that session. In some instances, if the organizers of the event find that they are assigning too many presentations to a specific session, they may create a new session and move some of the presentations from the old session to the new session. It is not necessary to track the history of such movements, only the current assignment of presentations to sessions, but this is another reason why it is possible for a session to exist before specifying which presentations will belong to it. For each track, there is one researcher that is designated as the track chairperson. Every track must have a chairperson, and the track can only have one chairperson. The track chairperson is responsible for organizing the presentations into different sessions and dealing with any conflicts or questions that For example, the Classroom Techniques track has six sessions scheduled. One of those sessions is the "Online Classroom Techniques Morning Session 1" and is going to be held in the hotel's "Presidential Conference Room" on June 12th starting at 10am. There are five presentations scheduled to be given during that session. Also on June 12th, the Information Systems Technologies track is having the Big Data Innovation" session starting at 10am in "Ballroom B" of the hotel. This session has six presentations scheduled for it. Recall that this system does not track the original submission and review process for presentations. A presentation is added to this system and assigned a session at the same time so there is never a situation in which a presentation will be in the system without being associated with a session. Similarly, a session must always be a part of a track. It is possible, however, for the users to specify the tracks in the system before they specify the sessions that will be a part of that track. It is also possible for the data about a session to be entered before specifying the presentations that will be a part of that session. In some instances, if the organizers of the event find that they are assigning too many presentations to a specific session, they may create a new session and move some of the presentations from the old session to the new session. It is not necessary to track the history of such movements, only the current assignment of presentations to sessions, but this is another reason why it is possible for a session to exist before specifying which presentations will belong to it. For each track, there is one researcher that is designated as the track chairperson. Every track must have a chairperson, and the track can only have one chairperson. The track chairperson is responsible for organizing the presentations into different sessions and dealing with any conflicts or questions that come up with scheduling the sessions. Each session also has a researcher that is the session chairperson. Every session must have a chairperson, and the session can only have one chairperson. The sessions chairperson acts as the host during the session by calling the session to start, introducing each presentation, and providing some concluding remarks at the end of the session. A researcher may be attending the conference just to make one or more presentations. A researcher may be attending the conference as a track chairperson and/or session chairperson. As such, a researcher may be a chairperson of a track or session and not be making any presentations, or they could be a chairperson and make many presentations. A researcher is not required to chair either a session or a track. If a person chairs a track, they can chair only one track. A person can chair multiple sessions. For example, Samantha Tickle chairs the Information Systems Tehnologies track. Samantha also chairs the "Big Data Innovations" session. However, Samantha is not doing any presentation at the conference. Roland Tumble is chair of the "Online Classroom Techniques Morning 1" session and chair of the "Online Classroom Techniques Afternoon 2" session. In addition, Roland is presenting research during the "Flipped Classroom Strategies" session on a different day