Task: Develop an entity relationship diagram for the MPA database.

Diagram: Using Visio:

• Begin with the ”Crow's Foot Database Notation" Visio template.
• Include these five entities: 
  • Student
  • Teacher
  • Event
  • Award
  • Music — see below for attribute ideas
• All reasonable attributes should be included for each entity.
• A logical primary key (a unique attribute) must be clearly identified for each entity.
• Foreign keys must be included to be able to connect the entities properly.
• Crow's feet must be used to show cardinalities. Crow's feet are  shown in the textbook, Figure 13.3, and the Reading PDF explains how to  create these from ordinary arrows/lines.
• Example ERDs are found in the Unit 3 Reading PDF.
• Use consistent case (Pascal, camel, small case, or underscore).

Also consider:

• Each teacher can have many students.
• No students have more than one piano teacher.
• Each student can play many pieces.
• Each student can participate in events, but they do not have to participate.
• Not all participants win awards.
• Teachers must have some credentials (usually a college degree).
• Attributes for the Music entity would include title, composer, publisher, difficulty, etc.
• Contact information is crucial for all people involved. Check the Reading PDF regarding addresses.
• To add an attribute to an entity, click the attribute shape and drag  it onto the stage and right under the entity. It should click into  place.

 Entity Table

Task: Develop one table for detailing either the  Student or the Event entity. (Create only one table, as this is an  example for your client, not details of the entire database.) Provide  this information in a Word table in the same format as the example found  in the Unit 3 Reading PDF.

Table: Include the following for your chosen entity in a Word table:

• A suitable entity name.
• Attributes: minimum 6 (take these from your ERD).
• Designate the primary key.
• Include the data type for each attribute: choose from those listed in the textbook Figure 8.7.
• Specify the logical length for each attribute.
• Include whether or not each attribute is required.
• Use consistent case (Pascal, camel, small case, or underscore).