Task: Design an ER diagram for that problem. Specify key attributes of each entity type.

Transcription

1 Q1. Consider the following set of requirements for a university database that is used to keep track of students transcripts. (10 marks) 1. The university keeps track of each student s name, student number, social security number, permanent address and several contact numbers, birth date, age, sex, and major, and degree program (B.A., B.S.,..., Ph.D.). Some user applications need to refer to the city, state, and zip code of the student s permanent address and to the student s last name. Both social security number and student number have unique values for each student. 2. Each department is described by a name, department code, office number, office phone, and college. Both name and code have unique values for each department. 3. A department can train other departments. 4. Each student must enroll in one department. 5. Each course has a course name, description, and course number, number of credit hours, level. The value of course number is unique for each course. 6. Course may generate many sections, each has a semester, year, section number, and references a single course. The section number distinguishes sections of the same course that are taught during the same semester/year. 7. Each section may contain many students Task: Design an ER diagram for that problem. Specify key attributes of each entity type.

2 Q2. Draw an Entity Relationship Diagram for the following scenario: A movie has a title, year and length. A movie is identified by its name and the year it was released A star has a unique name, birth date, age, and address; you should be able to search about the city, state, and zip code of the star's address. A studio has a name and address, and it's uniquely identified by a name. 1. A star can appear in any number of movies. 2. Stars must be supervised by one star. 3. Some movies have many stars and some have none. 4. A star can belong to at most one studio. 5. A studio can own any number of movies. 6. A movie is always owned by at most one studio, but some are not owned by any studio.

3 Q3. Draw an Entity Relationship Diagram for the following scenario: The Prescriptions-R-X chain of pharmacies has offered to give you a free lifetime supply of medicines if you design its database. Given the rising cost of health care, you agree. Here is the information that you gather. 1. Patients are identified by SSN, and their names, addresses, and also ages. 2. Doctors are identified by an SSN, for each doctor, the name, specialty and years of experience must be recorded. 3. Each pharmaceutical company is identified by name and has a phone number. 4. For each drug, the trade name and formula must be reordered. Each drug is sold by a given pharmaceutical company, and the trade name identified 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. 5. Each pharmacy has a name, address, and phone number. 6. Every patient has a primary physician. Every doctor has at least one patient. 7. 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. 8. 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.

4 9. Pharmaceutical companies have long-term contracts with pharmacies. A pharmaceutical company can contract with several pharmaceutical companies. For each contract, you have to store a start date, and end date, and the text of the contract. 10. Pharmacies appoint a supervisor for each contract. There must always a supervisor for each contract

5 Q4. Create an Entity Relationship Diagram for the following scenario: Rail transport managers wish to hold details of train services, stations and drivers in a database. The details they want to hold include the following: 1. A train has a unique code, type and capacity. 2. Each train may have a number of drivers that can drive it, and a driver can only drive one train. 3. The driver has a unique ID and a name. 4. A station has a unique name, type and location. 5. A station must have many trains passing through it, and a train may visits many stations.

6 Q5. Create an Entity Relationship Diagram for the following scenario: The COMPANY database keeps track of a company s employees, departments, and projects. Suppose that, after the requirements collection and analysis phase, the database designers stated the following description of the "miniworld" the part of the company to be represented in the database: 1. The company is organized into departments. Each department has name, a unique number, and a particular employee who manages the department. A department may have several locations. 2. A department controls a number of projects, each of which has a name, a unique number, and a single location. 3. We store each employee s name, social security number, address, salary, sex, and birth date. An employee is assigned to one department but may work on several projects. 4. We want to keep track of the dependents of each employee for insurance purposes. We keep each dependent s unique first name, sex, birth date, and relationship to the employee.