This activity is similar to the discussion in this module, but it involves a different scenario and will be submitted directly to your instructor via the link above (4-2 Activity: Entities and Attribu

IT 235 Module Four Activity Guidelines and Rubric Entities and Attributes, Part 2 Overview: This activity is meant to support you as you analyze a scenario requiring a new database design. You will analyze the user re quirement in the scenario in order to determine the entities and attributes required to design the database. Prompt: For this activity, analyze the below scenario, which outlines the business requirements and needs for a new database. As part of the process, you should use a color -coding tec hnique to identify the various entities and related attributes required to process the scenario. For guidance on the color -coding process, watch this video before you begin your work: Entity Relationship Modeling (8:04). You will be required to submit two deliverables: 1. A color -coded Word document with each entity and its related attributes colored in a matching font. For instance, in the narrative, i f you have a custome r entity with name and address details, each of the words (attributes) related to this entity would all appear in the same co lor —perhaps blue. Another entity and its related attributes may all be colored red. Your first step will be to copy the scenario to a new Word document. Then you will adjust the font colors for each of the related words. Thus, for this part of the assignment, do the following: a. Copy and paste the scenario text into a Word document. b. Color -code the text of the narrative with each entity properly identified. c. For each entity in the narrative, identify and color -code each attribute with the appropriate color. d. For each entity, identify the primary key and any foreign keys. In a table beneath the scenario (see next step), note PK and FK after each primary key and foreign key, respectively. e. At the bottom of the color -coded narrative, create a table listing each entity by name, listing each entity’s attributes, and finally listing the color used to highlight that entity. Include a bridge table, a s described in the scenario. 2. A completed Visio entity -relationship diagram (ERD) in crow’s foot notation. (You may paste a screenshot of the diagram into the Word document created in step 1.) The ERD should use color coding and the entity/attribute list co mpleted in step 1 as the basis for drawing each entity and its related attributes, along with primary and foreign key and relationships. Thus, for this part of the assignment, submit an ERD in whi ch you do the following: a. Include each entity and its related attributes clearly listed on the ERD. b. For each entity, notate the primary key (PK) and any foreign keys (FK). Also identify and draw the relationships between each entity. Scenario The intramural department at SNHU would like to begin keeping an inventor y of students participating on an intramural sports team. Each student has a student ID number, which can be used to uniquely identify a student. For each student, the intramural department would also like to k now the student’s name, age, gender, and which team they joined. There are multiple teams playing various sports; each sport will be assigned a unique sport ID and will inc lude a short description of the sport, such as rugby, soccer, cricket, or basketball. Teams are reorganized and reformed every sem ester, and each team must come up with its own name. Semesters can be identified by their year and beginning month; thus, fall semester 2017 would be 201708, and winter 2016 would be 201601. Because a student can play on multiple teams, the student -to-team relationship is many -to-many. Please use a bridge table to link the relationship between these two tables. Rubric Guidelines for Submission: Submit assignment as a Word document with double spacing, 12 -point Times New Roman font, and one -inch margins. Critical Elements Proficient (100%) Needs Improvement (80%) Not Evident (0%) Value Entities All entities in the scenario are notated and color -coded Some entities in the scenario are notated and color -coded No entities in the scenario are notated or color -coded 20 Attributes All attributes are identified and are color - coded to their related entity Some attributes are identified, and some attributes are color -coded to their related entity No attributes are identified or color -coded to their related entity 20 Primary and Foreign Keys for Entities Primary and foreign keys are notated for all entities Primary and foreign keys are notated for some entities Primary and foreign keys are not notated for any entities 20 Entity and Attribute Names All entities and attributes are drawn and listed by name on the ERD Some entities and attributes are drawn and listed by name on the ERD No entities and attributes are drawn or listed by name on the ERD 15 Primary and Foreign Keys on ERD Primary and foreign k eys are drawn for all entities on the ERD Primary and foreign keys are drawn for some entities on the ERD Primary and foreign keys are not drawn for any entities on the ERD 15 Articulation of Response Submission has no major errors related to grammar, spelling, syntax, or organization Submission has major errors related to grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas Submission has critical errors related to grammar, spelling, syntax, or or ganization that prevent understanding of ideas 10 Total 100%