Scribd
Upload
274 views2 pages

Assignment 1 Practice Example For The ERD and Entity Description

The document describes a scenario involving a music publishing company that stores data about artists they have signed and music they record. It notes that artists are featured on tracks, and tracks can feature multiple artists. Albums contain multiple tracks, though some tracks may not be on any albums. The company also commissions album covers, choosing one to publicize each album.

Uploaded by

Jayaram Gautam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
274 views2 pages

Assignment 1 Practice Example For The ERD and Entity Description

The document describes a scenario involving a music publishing company that stores data about artists they have signed and music they record. It notes that artists are featured on tracks, and tracks can feature multiple artists. Albums contain multiple tracks, though some tracks may not be on any albums. The company also commissions album covers, choosing one to publicize each album.

Uploaded by

Jayaram Gautam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Assignment 1 Practice example for the ERD and Entity Description Task

Scenario
A Music Publishing company stores data about its artists which it has signed up and Music
which it records. Each artist is featured on zero, one or more tracks. They assign an
Artist_Number to each artist and store personal data about them e.g. name, address, mobile
number, email and the date they were signed up. A tracks feature one or more artists. The
title and length of each track is recorded as well as a unique track number track and the date
the track was completed. Albums are made up of many tracks although there are some
tracks which do not feature on any album. The data required for albums is the unique album
name, the number of tracks and the length of the whole album. An album is publicised by a
cover, many potential covers may be commissioned by the record company but only one is
chosen to be used on each album. Each cover is given a unique commission number and
the cover name, price and description is recorded.

a) Draw an Entity Relational Diagram (ERD) in QSEE and copy into the box on the
template. NOTE Do not add attributes to the ERD and there is no need to resolve
any Many to Many relationships.

b) Complete the Entity description for each of the 4 entities identified on the ERD.

See solution on the template below.


Fundamentals of Databases - Entity Relational Model Template

Student Id:……………….Student Name:…………………………………Student Group:….

Entity Relational Diagram (ERD)

ARTIST is featured on TRACK

features

appears on

contains

COVER publicises ALBUM

is publicised by

Entity Type Definition


Entity Identifying Other Attributes Entity description
type Attribute
ARTIST Artist_Number name, address, mobile An artist who is signed up by
number, email, the recording company
date_signed
TRACK Track_number Title, track_length, A music track which is
completion_date recorded by the recording
company.
ALBUM Album_name Number_of_tracks, An Album which is the
length_of _album combination of a number of
tracks chosen to be put
together.
COVER Commission_number cover name, price, A commissioned cover
description which may be chosen to
publicise an album.

You might also like