Problem statement. Your consulting company has been asked to develop a relational database design for a growing drug store chain. You gather the following information: Each patient has an identifying SSN, plus a name, age, and address.
Doctors also have an identifying SSN. Additionally, each doctor has a name, a specialty, and a number of years of experience.
Each pharmaceutical company is identified by name and has a phone number. Each drug has a trade name and a formula.
Each drug is sold by a given pharmaceutical company, and the trade name identifies a drug uniquely from among the products of that company. If a pharmaceutical company is deleted, you need not keep track of its products any longer.
Each pharmacy has a name, address, and phone number.
Every patient has a primary physician. Every doctor has at least one patient.
Each pharmacy sells several drugs and has a price for each. A drug could be sold at several pharmacies, and the price could vary from one pharmacy to another.
Doctors prescribe drugs for patients. A doctor could prescribe one or more drugs for several patients, and a patient could obtain prescriptions from several doctors.
Each prescription has a date and a quantity associated with it. You can assume that, if a doctor prescribes the same drug for the same patient more than once, only the last such prescription needs to be stored.
When a prescription is filled, we want to track the pharmacy that filled it and the date that it was filled.
Pharmaceutical companies have long-term contracts with pharmacies. A pharmaceutical company can contract with several pharmacies, and a pharmacy can contract with several pharmaceutical companies. For each contract, you have to store a start date, an end date, and the text of the contract.
Pharmacies appoint a supervisor for each contract. There must always be a supervisor for each contract, but the contract supervisor can change over the lifetime of the contract.
1. Develop an ER diagram that captures the conceptual model. Show all detail in the ER diagram, such as the mapping cardinalities. Identify any constraints not captured in the ER diagram. I suggest you follow the method for developing an ER diagram we covered in class (start with entity sets, etc.)
2. Map the ER diagram to a relational database schema, using the procedure we have learned in class. Write down the database schema.
3. Normalize your relational schema using the procedure we learned in class. As a first step, document any functional dependencies that would indicate the need for normalization. Note that you are not required to normalize, but if your tables are not in BCNF or 3NF then you should explain why you did not normalize. The final relational schema must be documented in SQL using create table statements.
4. Think of at least 5 questions about the data that would be interesting to management of the drug store chain. Write each of them in SQL. Do not use only questions that are simple to express in SQL. The questions should use grouping, joins and/or subselects.