Reference no: EM133594028

Scenario: The Metropolitan Piano Association (MPA) is an organization of piano teachers in the Global Springfield area. Their purpose is to promote the education and performance of piano students of all ages through hosting a variety of live student performances and competitions. These competitions result in awards for the top performers, those who improved the most, etc. The association president Nick Rayapur has been keeping track of everything in Excel, but he knows it is time to build a real database. It will be hosted in the cloud so that member teachers can input information from home and check event schedules. While the cloud service will be responsible for quite a few things, you are tasked with organizing the database.

Your action here is to do some diagramming and organizing of data. Note that the Music entity will be important in the ERD because competitions may rely heavily on the style and difficulty of the music being played.

Part 1: Level 0 DFD

Task: Develop a Level 0 data flow diagram in Gane Sarson style for the MPA database.
Diagram: Using Visio:
• Begin with the "Data Flow Model Diagram" Visio template.
• Include entities, data flow arrows (with explanations), processes, and data stores.
• Teacher, Performer, and Event must be included.
• Use only the shapes shown in Figure 7.1, and model your DFD like the example, Figure 7.6.
• Use numbering standards as explained in the Reading PDF.

Part 2: ERD
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:
o Student
o Teacher
o Event
o Award
o 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.

Part 3: 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).

Formatting:
• This assignment is a working document for your client and your tech team; use a business-style template, not APA formatting. Your professor may provide links to suitable free templates.
• On the cover page, include your client's name and business name, your name, and a descriptive title for the project.
• Use the following subheadings:
o Level 0 Data Flow Diagram
o Entity Relationship Diagram
o Sample Entity Table
• Make sure you properly embed your Visio diagrams into your Word document.