Reference no: EM132350698

Relational Database Systems

Objective: This is an individual assignment aimed to give the student exposure in understanding, designing, building and analyzing database systems for a given real-time based scenario and be able to conduct optimal strategies for efficient management of databases.

Intended Learning Outcomes covered:

1. Design the logical structure of a database using Entity-Relationship diagram.

2. Apply normalization techniques to reduce redundancy in a database.

Task 1:

Complete the work proposal in Microsoft Word file format (may include possible answers based on your initial understanding). Work proposal for the assignment must be submitted before 23:59 hrs on 6/8/2019 and must include:

a) Understanding of deliverables - a detail description of deliverables.

b) General overview of proposed plan - initial understanding of solution to task 2 which includes, the name of entities, associative entities and relationships and a brief write up on the concept of referential integrity. Initial understanding of solution to task 3 which includes the process to be followed for normalization and a brief write up on the concept of data integrity.

c) Timeline and references for completion of task 2 and task 3.

Task 2:

Scenario:

Consider the following scenario of a car dealership. The owner wants to maintain a database for easy access to records related to the customers, cars both new and used, service details and other things. The requirements are as follows:

The details of the customer include the customer identity number, name, mobile number, address, e-mail.

A salesperson may sell one or many cars or may not sell any car. Each car is sold by one and only one salesperson.

The attributes of the salesperson include the unique identification number, the name, mobile number, address, e-mail, gender, age and date of joining.

The attributes of the car include the chassis number, the model number, color, brand and year of sale.

A salesperson writes an invoice whenever a car is bought by the customer. The details of the invoice include the invoice id, the date, day, time of the sale and car chassis number, the customer identity number, salesperson identification number as a reference. Each customer can be associated with multiple invoices or may not be associated with any invoice at all if he/she does not buy a car. But one invoice is related to only one customer.

A customer may also come in only to get his/her car serviced. The details of the service includes the service id, the date, day, time of the service and car chassis number, the customer identity number, mechanic identification number as a reference. A customer can give one or many cars for service or may not give car for any service. One service belongs to only one customer.

A service can be done by only one mechanic but each mechanic may work on one or many services or no service at all. The details about the mechanic include the id, name, mobile number, address, date of joining.

A car can have one or many service details associated, but one detail will be associated to only one car.

a) Construct the Entity Relationship Diagram (ERD) for the above given scenario. Identify all the entities, associative entities, attributes of each entity including primary key, relationship between the entities and cardinality constraints. State any assumptions necessary to support your design.

b) Analyze the above given scenario and discuss about the possible structure of any two relations by giving the details on the datatype and the size of each attribute. State any assumptions necessary to support your design.

c) Discuss the possible constraints to be implemented in the design given in (b) part to make the design better. State any assumptions necessary to support your design.

Task 3:

a) Normalize the below given Form to First Normal Form, Second Normal Form and Third Normal Form. Make assumptions for the identification of the primary key wherever necessary.

ABC SHOE SHOP INVOICE

INVOICE NO: 1233                                                                                       SALESMAN ID: S23

INVOICE DATE: 21/5/2019                                                                           SALESMAN NAME:BUDOOR TIME: 6:15 PM

CUSTOMERID:CA1156 CUSTOMER NAME: Aparna

CUSTOMER MOBILE NO: 86977080

SHOE NUMBER	SHOE DESCRIPTION	CATEGORY	COLOR	SIZE	QUANTITY	UNIT PRICE	SUB-TOTAL
S12	JAHANARA	FORMAL	BLACK	42	1	12.000 OMR	10.000 OMR
S67	SHENAZ	CASUAL	BROWN	42	2	1.100 OMR	2.200 OMR
S89	TIPTOPS	SPORTS	WHITE	42	1	22.500 OMR	22.500 OMR
							INVOICE AMOUNT	34.700 OMR

b) Give a reflection of how normalization will help in achieving a better database design.
Support your answer with reference to the above Question. (At least 100 words)

c) Discuss the implementation of referential integrity in the above scenario. (At least 200 words)

Task 4

Be ready for a written viva to demonstrate your knowledge with the different concepts used in preparing the assignment. Schedule for the written viva will be announced in the class and on Moodle/MEC mail. Marks for task 2 and task 3 will depend on the satisfactory pass for the demonstration in task 4.