Please work on the laptop please , i want to know how to work..

SmartProjects Company is planning to design a data model to hold information relating to their projects, employees working on company projects, and their customers. SmartProjects IT Manager provided the following business rules to the software developer:

Complete the information-level design for the database that satisfies the above constraints and user view requirements. In order to complete this information-level design you are required to answer the questions given below A and B.

User view 1 requirement: Each employee has a unique ID number, and their first name, last name, date of birth, address, contactNo user name and password must be recorded. There is a need to keep track of the dependents of each employee for insurance purposes.

User view 2 requirements: Each customer has a unique customer_number and their first name, last name, address, PNum, project tile and payment must be recorded.

User view 3 requirements: Each project has a project number that uniquely identifies the project (PNum) and project title, StartDate, managerID, managerName,managerContactNo must be recorded.

User view 4 requirements: An employee can work on only one project. A project can have one or more employees associated with it.

User view 5 requirements: Each department has a unique ID number and name. A department can have many employees. An employee can only work in one department. A department controls a number of projects.

User view 6 requirements: One project may belong to several departments. One customer can submit only one project at one time .

A. Represent the structure of your database visually by using the entity-relationship (E-R) diagram. If you make any assumptions about data that doesnt show from the problem, they must be described.

You can use Visio or any other software tool to create the ER diagram.

B. Build this model using MS Access by creating these tables and relationships. Populate these tables with appropriate data, at least 3 records in each table.

I CREATE TABLE BLOW

a. Add attributes to these entities and represent these entities (or tables) and attributes as a collection of tables and attributes. You are required to arrange them as given in the example below.

Entities and attributes -

Employee ( int ID_number, string first_name, string last_name, date date_birth, string address, double phoneno, string user_name, string password, int PNum, int dept_num) ; //one PNum for one employee

Depandents ( int ID_number, string name,double phoneno ); // ID_number belongs to Employee and name , phoneno for depandents.

Customer ( int cust_number, string first_name, string last_name, string address, int PNum, int payment) ;

Project ( int PNum, string project_title, date start_date, int manager_id) ;

Manager (int manager_id, string manager_name, double phoneno);

Department ( int dept_num, string dept_name );

department_project (int dept_num, int PNum);

b. Outline all relationships between entities.

E.g., One project may belong to several departments - One-to-many,

Outline all relationships between entities.

many depandants may belong to one employee - many to one

many employee may work on one project - many to one

one department can have many employees - one to many

one employee can only belong to one department - one to one

A department controls a number of projects and One project may belong to several departments. - many to many

One customer can submit only one project at one time - one to one