17 Apr we have been building our Database using concepts of design and Structured Query Language (SQL). Now, your database should be ready to be deploye

1

4

Artist

PK Artist_ID (varchar)

Name (char)NOT NULL

Event

PK Event_ID(varchar)

Date(datetime)

Organizers

PK Organizer_ID(varchar)

Name(char) NOT NULL

Manager

PK Manager_ID(varchar)

Name(char) NOT NULL

Album

PK Album_ID(varchar)

Title(char) NOT NULL

FK Artist_ID(varchar)

Year(year)

FK Label_ID(varchar)

Label

PK Label_ID(varchar)

Name(char) not null

(

Producer

PK Producer_ID(varchar)

Name(char) NOT NULL

Release

PK Release_ID(varchar)

Date(datetime)

1 1

*

*

1

The following Is the DDL SQL statement that is used to create the Musician database:

mysql> CREATE DATABASE Musician;

mysql> use musician

mysql> create table Artist

-> (Artist_ID varchar (255) PRIMARY KEY,

-> Name char (255) NOT NULL);

mysql> CREATE TABLE Label

-> (Label_ID varchar (255) PRIMARY KEY,

-> Name char (255) NOT NULL);

mysql> CREATE TABLE Event

-> (Event_ID varchar (255) PRIMARY KEY,

-> Date datetime);

mysql> CREATE TABLE Organizers

-> (Organizer_ID varchar (255) PRIMARY KEY,

-> Name char (255) NOT NULL);

mysql> CREATE TABLE Producer

-> (Producer_ID varchar (255) PRIMARY KEY,

-> Name char (255) NOT NULL);

mysql> CREATE TABLE Manager

-> (Manager_ID varchar (255) PRIMARY KEY,

-> Name char (255) NOT NULL);

mysql> CREATE TABLE Album

-> (Album_ID varchar (255) PRIMARY KEY,

-> Title char (255) NOT NULL,

-> FOREIGN KEY (Label_ID) REFERENCES Label(Label_ID),

-> Year year,

-> FOREIGN KEY (Artist_ID) REFERENCES Artist(Artist_ID);

Reference

Captain, F. A. (2018). Six-step relational database design: A step by step approach to relational database design and development. Fidel A Captain.

Embley, D. W., & Thalheim, B. (2012). Handbook of conceptual modeling: Theory,

Schmidt & Brodie, M. L. (2018). Relational database systems: Analysis and comparison. Springer Science & Business Media.

Safety Engineering and Risk Analysis. https://doi.org/10.1115/imece2016-66791

,

Running Head: Conceptual Modeling Design 1

Conceptual Modeling Design 4

Conceptual Modeling Design

Student’s Name:

Tutor’s name:

Date:

The entities to be used include the following:

· Artist.

· Manager

· Producer

· Event

· Album

· Organizers

· Label

· Release

Relationships

The manager manages all the activities that the artist should take part in including signing the artist, managing the artist’s resources, advising the artist etc. The producer deals with the music production part, together with the organizers, they organize events that the artist will perform at. The producer together with the manager oversea the recording and the release of albums.

Each of the entities will have various attributes as follows:

· Under the manager the primary key will be the manager’s ID, other attributes will include the manager’s name, address, and the phone number.

· Under the artist the PK will be the artist’s ID while the other attributes will be the name, address, genre of music, and the phone number.

· The producer’s section will include the name, address, phone number, the salary, and the producer’s ID.

· The event will have attributes such as the type of event, the amount to be charged per person, and the reference number of the event.

· The label will include the record label’s name, the amount they charge, the serial number of the record label.

· The release entity will attribute such as the release date, and the venue of the release.

ERD Blueprint.

The ERD shows the relationship between the various entities involved in the music production.

Organizers

Event

Producer

Artist

Album

Label

Release

Manager

Reference.

D’Angelo, A. (2016). Development of the reliability-risk modeling framework for ranking conceptual designs. Volume 14: Emerging Technologies; Materials: Genetics to Structures; Safety Engineering and Risk Analysis. https://doi.org/10.1115/imece2016-66791

Embley, D. W., & Thalheim, B. (2012). Handbook of conceptual modeling: Theory, practice, and research challenges. Springer Science & Business Media.

Mok, W. Y., & Embley, D. W. (1996). Transforming conceptual models to object-oriented database designs: Practicalities, properties, and peculiarities. Conceptual Modeling — ER '96, 309-324. https://doi.org/10.1007/bfb001993