1. (a) Explain what Third Normal Form is in the context of re- lational database design and why we want to normalise a relation to the Third Normal Form. (b) Company X has a number of departments. Each department has an identifying number, a budget and a manager. It also has a number of employees, projects and offices. Each em- ployee may work on several projects within the department and get a payment for each project that (s) he works on. Each office may be occupied by several employees, but one em- ployee should have only one office. Also, there is a phone in each office. Currently, the information about departments is held in a file using the following structure. Dept (Dept#, Budget, Mgr#, Employees (Emp#, Name, Proj#, Off#, Phone, Pay), Projects (Proj#, Proj_Budget), Offices (Off#, Area, Phone) That is, given a Dept#, there is a Budget, a Manager, a sot of Employees, a set of Projects and a set of Offices associated with it. For this structure, i. convert it into a First Normal Form relation (the primary key should be underlined); ii. identify the functional dependencies that you would expect to hold and express them in a functional dependency diagram (state any assumptions you make about the data): iii. normalise the relation obtained in part (i) into Third Normal Form (primary keys should be underlined). (c) How would you convince company X that your design is bet- ter than their original one? Suggest one possible reason that Company X may not be happy with your design. 2 [5 (5) [4