Please I want you to write to me the same but about Clinical Appointment System

COMPANY DATABSE (SAMPLE) In this section we describe a sample database application, called COMPANY, which serves to illustrate the basic ER model concepts and their use in schema design. We list the data requirements for the database here, and then create its conceptual schema step-by-step as we introduce the modeling concepts of the ER model. The COMPANY database keeps track of a company's employees, departments, and projects. Phase I: Requirements collection and Analysis (3 marks) Guidelines: After consultation, the following requirements for a company database have been determined: 1. The company is organized into departments. Each department has a unique name, a unique number, and a particular employee who manages the department. Keep track of the start data when that employee began managing the department. A department may have several locations. 2. A department controls a number of projects, each of which has a unique name, a unique number, and a single location. 3. 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, which are not necessarily controlled by the same department. Keep track of the number of hours per week that an employee works on each project. Also, keep track of the direct supervisor of each employee 4. Keep track of the dependents of each employee for insurance purposes. Keep each dependent's first name, sex, birth date, and relationship to the employee. Phase II: Conceptual design: E-R Diagram (3 marks) Phase III: Logical schema design mapping (3 marks) Phase IV: Physical schema design - Internal Schema (3 marks) QUERY FOR CREATING COMPANY DATABSE (10 MARKS FOR LAB) -- Generated by Oracle SQL Developer Data Modeler 4.1.5.907 -- at: 2017-02-15 23:40:16 AST -- site: Oracle Database 11g -- type: Oracle Database 11g CREATE TABLE Department ( Dname CHAR(20), Dnumber INTEGER NOT NULL, MGRSSN INTEGER MGRSTARTDATE DATE Employee_SSN INTEGER NOT NULL, Project_PNUMBER INTEGER NOT NULL ) ALTER TABLE Department ADD CONSTRAINT Department_PK PRIMARY KEY ( Dnumber ); CREATE TABLE Dependent ( ESSN INTEGER NOT NULL, Dependent_Name CHAR(20), NOT NULL, Sex CHAR(6), Bdate DATE , Relationship CHAR(10), Employee_SSN INTEGER NOT NULL ); ALTER TABLE Dependent ADD CONSTRAINT Dependent_PK PRIMARY KEY ( ESSN, Dependent_Name, Employee_SSN ) ; CREATE TABLE Employee ( Fname CHAR(10), Minit CHAR(10), Lname CHAR(10), SSN INTEGER NOT NULL, Bdate DATE, Address CHAR(100), Sex CHAR(6), Salary INTEGER, Project_PNUMBER INTEGER ); ALTER TABLE Employee ADD CONSTRAINT Employee_PK PRIMARY KEY ( SSN ) ; CREATE TABLE Project ( Pname CHAR(10), PNUMBER INTEGER NOT NULL , Plocation CHAR(10), Dnumber INTEGER NOT NULL ); ALTER TABLE Project ADD CONSTRAINT Project_PK PRIMARY KEY ( PNUMBER ) ; ALTER TABLE Department ADD CONSTRAINT Department_Employee_FK =OREIGN KEY ( Employee_SSN ) REFERENCES Employee ( SSN ) ; ALTER TABLE Department ADD CONSTRAINT Department_Project_FK FOREIGN KEY ( Project_PNUMBER ) REFERENCES Project ( PNUMBER ) ; ALTER TABLE Dependent ADD CONSTRAINT Dependent_Employee_FK =OREIGN KEY ( Employee_SSN ) REFERENCES Employee ( SSN ) ; ALTER TABLE Employee ADD CONSTRAINT Employee_Project_FK FOREIGN KEY ( Project_PNUMBER) REFERENCES Project ( PNUMBER)