Logical and Physical Data Model Development for Music Data

Task 1 – Logical Data Model (ERD)

Task 1 – Logical Data Model (ERD)

Develop a logical data model for the music data in the form of an entity-relationship diagram (ERD). This should detail the cardinality of relationships, attributes of each entity, be normalised to 3NF and keys for each entity should be defined with the type of key appropriately identified.

Document this in your report.

Task 2 – Physical Data Model (ERD)

Develop your logical design into a more detailed ERD in the form of a physical data model. This should include appropriately named tables and columns, indicating types and constraints. Keys for each table should be defined with the type of key appropriately identified. Document this in your report.

Task 3 – Database Implementation

Create and run a set of SQL statements to turn the physical design into an actual database. This should consist of several CREATE TABLE statements that accurately reflect the physical data model, including data types, constraints, and keys.

Document these in your report and run the statements on your Student Server SQL installation to create an empty copy of the database.

Then:

Create and run a set of SQL SELECT queries to export appropriate data-sets from the raw data for migration into your planned new structure. Use these queries along  import functions in an SQL administration tool, or another appropriate method, to populate your empty database on the Student Server.

Document this process in your report explaining, under each query, its function in plain English. Record and analyse any challenges you encounter in transposing the data and what steps you have taken to resolve them.

Task 4 – Example queries

To demonstrate that your final database is useful, write a minimum of five realistic sample SQL queries (use your imagination and the notes from the scenario to come up with sensible suggestions).

They should include the following techniques:

• Joins (using two or more tables)
• Ordering output (ORDER BY)

Document these in your report, under each explaining the function of the query in plain English and the expected results in terms of the columns that should be returned, number of rows/records expected and some example data (copy and paste tabular data, or a screenshot). These queries will be tested against the copy of your database held on the student server, to ensure that they function as expected.