Complete database management system to address a practical database need and implement a relational database based on that design. Your database system should be designed to perform general information management tasks such as systematic collection, update, and retrieval of information for a small organization.

The objective of Project #1 is to develop a normalized relational data model describing the primary business processes of Spring Company. Spring company has several departments. Each department has a supervisor and at least one employee. Employees must be assigned to at least one project, but possibly more departments. At least one employee is assigned to a project, but an employee may be on vacation and not assigned to any projects. The important data fields are the names of the departments, projects, supervisors, and employees, as well as the supervisor and employee number and a unique project number. The initial entities for your model are Department, Employee, Supervisor and Project. In addition to these initial entities, you are provided with several business rules.

Deliverable 1

Begin with the initial entities for Department, Employee, Supervisor, and Project provided above, transform them into RELATIONS. Realize that the four entities (or the four converted relations) are not in the 3rd Normal Form. This is obvious by the many-to-many relationship that would need to exist between DEPARTMENT and EMPLOYEE and the relationship between EMPLOYEE and PROJECT. Make sure to show the referential integrity constraints diagram

You are to do the steps necessary to obtain the 3rd Normal Form. You do not have to show how you got there, but you are to provide a document that shows the final relations you come with (and their relationships) once you have achieved the 3rd Normal Form. Hint: Your answer will be within the Word document you submit as your Project 1 Assignment response along with the other deliverables for this assignment. Be sure to format this showing the logical schema (Rectangle boxes for relations in alphabetical order and lines between the relations to indicate the relationships). This format is NOT an ERD. Make sure it includes proper formatting and capitalization, as well as the appropriate relationships.

Deliverable 2

In Deliverable 2, you will start with a copy of your Deliverable 1, and build upon it by adding the necessary functionality to support the following business rules:

Business Rules: In addition to the following business rules, make sure to add any other business rules based on your assumptions:

1. Each DEPARTMENT has exactly one SUPERVISOR.
2. A SUPERVISOR is in charge of one and only one DEPARTMENT.
3. Each DEPARTMENT is assigned at least one EMPLOYEE.
4. Each EMPLOYEE works for at least one DEPARTMENT.
5. Each PROJECT has at least one EMPLOYEE working on it.
6. An EMPLOYEE is assigned to 0 or more Projects.
7. Add any additional business rules

In Deliverable 2, You will add the additional relations and relationships to the relational schema you created in Deliverable 1. You must maintain 1st, 2nd, & 3rd Normal Form in this enhanced model. Be sure to list your relations in alphabetical order and be sure to include the relationships between the relations (all these lines may look a little messy). Also, keep in mind that all the relations must be shown flush left against the left margin of the page and in alphabetical order. Be sure to use the correct capitalization formatting with RELATION names being singular and, in ALL CAPS, while attributes are presented using Proper Camel notation. Remember that this logical schema is a listing of the relations and relationships, and it is not in the same format as an ERD. Also, make sure to show the Functional Dependencies(Full, Partial, Transitive)

Deliverable 3

Contains the same information as Deliverable 2, except in a different format. Deliverable 3 is an Entity Relationship Diagram (ERD) that you develop in ERwin. All of the functionality indicated in the business rules must be present. Also, this exercise is an excellent opportunity to show your understanding of Enhanced Entity Relationship Diagrams (EERD),as you will have the opportunity to demonstrate Supertype/Subtypes. A helpful hint here is to take a screenshot of your ERwin ERD instead of printing it. ERwin places a big watermark description across the page when you print using the free Community Edition of the software; however, if you simply take a screenshot, then the watermark does not appear. All entities, attributes, and relationships must be properly labeled. Although they are presented in different visual formats, the information contained on this Deliverable 3 ERwin logical data model (ERD) must exactly correspond to the information contained on the Logical Schema of the deliverable.