Reference no: EM131311743 , Length: word count:200

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 and must include:
- What you will do with the given tasks: task 2, task 3 and the dates (timeline) by when they will be completed
- General overview of initial understanding of solutions to task 2 and task 3
- Identification of Literature Resources

Task 2: Scenario:

Apollo Hospitals (AH) is a popular medical service provider in Oman. AH wants to automate its business functions into an information system. The proposed information system must be developed keeping in mind the following business rules. As part of this, you need to analyse and develop an Entity Relationship model depicting the following various business requirements and functionalities for the proposed Pharmacy Information System of AH.

Dr. Prathap Reddy, Chairman, is aware that other multi-specialty hospitals are coming up in a big way and AH will face fierce competition from new healthcare systems. So, he has decided to take all measures to always be ahead of others in the market. It is increasingly important to AH that Reddy be able to analyse services rendered by AH and perception of patients more thoroughly.

The Pharmacy places requests to the Purchase Department whenever it is in need of drugs. Pharmacy is identified by unique id, name and telephone number. Purchase Department is identified by a unique number. The other elements are phone number, manager. The Purchase Department submits many orders or may not submit an order. An order is uniquely identified by an id. The other elements of order are placement date, fulfillment date, received date, order amount. An order consists of one or more drugs or items. A drug is supplied by one or more supplier. A supplier supplies many drugs or may not supply a drug. Whenever a supplier supplies a drug, AH wants to record the shipment details such as date of supply. The elements of drug are unique id, name, type, manufacturer id, manufacture date, expiry date, batch number, unit cost. A supplier is uniquely identified by id. The other elements of supplier are name, address, phone number, email, location and track record.

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

b) For the task 2a, analyse and recommend how the proposed ER model could accommodate the shipment and payments.

Task 3:

a) Normalize the below given Patient Prescription Bill to First Normal Form, Second Normal Form and Third Normal Form.

b) For the finally arrived normalized form in task 3a above, discuss how the redundancy has been minimized.

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 written viva.

Note: Task 4 is compulsory. No marks will be awarded to tasks 2 & 3 if written viva is not taken by a student.