Consider the below business rules of a consultancy company that has many departments. * Each employee belongs to only one department. Each employee has a unique email address. * Each department has one manager and many employees. * Each project is owned by one department. * An employee can work on many projects with different roles but has one role for each project. * A project can have many employees and they can be from different departments. * The progress of projects is evaluated once a week by department managers. The evaluation of a project on a particular date has a rating, which is an integer between 0 (very bad) to 5 (excellent). Consider the below relational database schema of five relations for managing projects of the company. Possibly due to an ER model not well designed or incorrect mapping from the ER to relational model, the database schema is not fully in 3NF and contains data redundancy. Some example tuple is given to explain the meaning of attributes The Project Management Database Department(deptiD, deptName, manager, empID) Employee(empID, empName, deptiD, email) Project(projID, startYear, deptID) EmpProj(empID, projID, role) Evaluation (projID, manager, evalDate, rating)