

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Study normalized lecture notes now
Typology: Lecture notes
1 / 3
This page cannot be seen from the preview
Don't miss anything!


The following normalization question refers to the simplified database activities of a construction company that manages several building projects. Each project has its own project number, name, employees assigned to it and so on. Each employee has an employee number, name, and job classification such as engineer or computer technician. The company charges its clients by billing the hours spent on each contract. The hourly billing rate is dependent on the employee’s position. Periodically, a report is generated that contains the information displayed in Table 5.1. The Total Charge in Table 5.1 is a derived attribute and, at this point is not stored in this table. The easiest short-term to generate the required report might seem to be a table whose contents correspond to the reporting requirements. (See Figure 5.1.)
The structure of the data set in Figure 5.1 does not handle data very well for the following reasons:
Update anomalies. Modifying the JOB_CLASS for employee number 105 requires (potentially many alterations, one for each EMP_NUM =105) Insertion anomalies. Just to complete a row definition, a new employee must be assigned to a project. If the employee is not yet assigned, a phantom project must be created to complete the employee data entry. Deletion anomalies. If employee 103 quits, deletions must be made for every entry in which EMP_NUM =103. Such deletions will result in loosing other vital data of project assignments from the database. In spite of these structural deficiencies, the table structure appears to work; the report is generated with ease. Unfortunately, the report may yield different results, depending on what data anomaly has occurred.
Required: Referring on the same scenario of a construction company; normalize the following table to 3NF.
Nomalize the following table to 3NF
project_no manager address p1 Black,B 32 High Street p2 Smith,J 11 New Street p3 Black,B 32 High Street p4 Black,B 32 High Street
Nomalize the following table to 3NF