REPUBLIC OF RWANDA

KIGALI INDEPENDENT UNIVERSITY ULK

P.O. Box 2280, KIGALI
Website://www.ulk.ac.rw
E-mail: ulk@rwandatel.com

On 08th July 2017

Advanced Database Design and Implementation

Project
Topic: A Music Shop Management System

LECTURER:

 NIYIGENA PAPIAS Ph D

COMPILED BY:

 BALIBANGI KILOLO Prosper: 201611779

Academic Year 2016-2018

 1

TABLE OF CONTENTS

I. INTRODUCTION……………………………………………………………..2
II. SYSTEM REQUIREMENTS………………………………………….………2
IN GENERAL……………………………………………………………………………..……………..2

DATA REQUIREMENTS………………………………………………………………..…………..3

III. USE CASE DIAGRAM…………………………………...…………………..5

IV. CLASS DIAGRAM……………………………………..…………………….6
 2

I. INTRODUCTION
A music shop is a warehouse where people can come and buy music in digital or
physical format.
The selling is done either in a building/room or in a virtual space or even both.

The basic aim of this system is to computerize the way employees keep all transactions, and
to facilitate customers to do their commands. All of this must be recorded in the system so
employees can store all music details, and customer’s details and commands.

The advantage of the implementation of this system is that the subscribers can get the music
even very far they are.

Objective:

In any time, we can easily find all information about subscribers, music, and its
details. The employee will find it easy in the automated system rather than using the manual
writing system. The subscriber can download any content he need even if he is very far from
the shop buildings/rooms. The system contains a database where all the information will be
safely stored.

N.B: This system is designed to facilitate customers to download music, and doesn’t include
the management of employees, or many details about artists, the country of publishing, etc...

II. SYSTEM REQUIREMENTS

IN GENERAL:

- The system must allow employees to enter data in the system in anytime.
- The system must allow visitors to subscribe to the shop, and subscribers to
download any content they want. All payments will be done at a bank, and
costumers shall have to present bank slips to confirm the subscription.
- The system must do all calculations and provide updated reports every time.
 3

- Employees must log in the system before recording anything, and once
recorded data can’t be modified. Subscribers shall also login before
downloading anything.
- All things must be done safety, that is why there are some constraints in data
types:
1. Integer: must have one optional sign character (+ or -) followed
by at least one digit (0-9). Leading and trailing blanks are
ignored. No other character is allowed here.
2. Varchar: it will be used to store alphanumeric characters. In this
data type we can set the maximum number of characters up to
8000 ranges by defaults our DBMS SQL Server will set the size
to 50 characters range.
3. Date: here no parameters are required when declaring the date
data type. Date values should be specified in the form YYYY-
MM-DD.
4. Time: Time values should be specified in the form: HH:MM:SS.

DATA REQUIREMENTS:

A. Entities:
- EMPLOYEE
- CUSTOMER
- DOWNLOAD
- MUSIC

B. Attributes:
- EMPLOYEE:
 employee_id
 function
 names
 gender
 contact_number
 email
 username
 4

 password
- CUSTOMER:
 customer_id
 names
 registration_date
 last_subscription_date
 subscription_category
 username
 password
- DOWNLOAD:
 download_id
 download_date
 music_id
 customer_id
- MUSIC:
 music_id
 category
 title
 artist
 publisher
 other_details

RELATIONSHIPS AND CARDINALITY:

EMPLOYEE registers CUSTOMER (1-N)

CUSTOMER commands/download MUSIC (N-1)

CUSTOMER makes a DOWNLOAD (1-1)

 5

III. USE CASE DIAGRAM

 6

IV. DATA DICTIONARY

A data dictionary is an integral part of entity-attribute tables of the whole system

(database). It holds information about the whole system, tables and the data that it
stores.
Table Attributes Data Types Constraints
Employee employee_id Int(11) Primary key
This table will store function Varchar(10) Null
informations about employees names Varchar(30) Not null
gender Char(1) Null

contact_number Varchar(12) Not null

email Varchar(40) Not null
username Varchar(8) Not null
password Varchar(8) Not null
Customer customer_id Int(11) Primary key
This table will store names Varchar(30) Not null
informations about customers/ registration_date datetime Not null
subscribers last_subscription_date datetime Not null
subscription_category Varchar(10) Not null
username Varchar(8) Not null
password Varchar(8) Not null
Download download_id Int(11) Primary key
This table will store download_date Datetime Not null
informations about downloads music_id Int(11) Primary key
made by customers customer_id Int(11) Primary key
Music music_id Int(11) Primary key
This table will store category Varchar(10) Not null
informations about music to title Varchar(10) Not null
download artist text Not null
publisher text Null
other_details text null
 7

V. ENTITY-RELATIONSHIP DIAGRAM
 8

VI. THE WEB APPLICATION

The main page:

When you choose a song you are asked to log in or to create an account:
 9

Registration page:

Once you are logged in and you want to download, you have to right-click on the
song and choose “save as”:
 10

If you have left-clicked, you will start playing the music: