Project Requirements and Description(The Mini world or UOD): The Computer Science Lab (CS Lab) wants to build a database for maintaining its records. You are invited as a database architect to develop a database schema for keeping track of their data. The database requirements are summarized as follows: - The CS Lab has employees, each employee has an emplid, first name, last name, sex, date of birth, date of hire, email, phone number, address, hourly rate, total amount of weekly working hours, and title. Each employee is uniquely identified by an emplid. - There are two categories of employees: coordinator, or tutor. This category is based on the title. Each employee can belong to one and one category only. - Tutors have different courses they tutor. Each tutor can tutor one or more courses. - A course is identified by course name such as CMP 420. A course also has a title, description, credit, hours. - The CS Lab also maintains students visit to the lab for tutoring services. Each (student) tutee has emplid, first name, last name, phone, email and address. Each student is uniquely identified by an emplid. - The database keeps track of each tutee's visit including the date of visit, time in and time out, the course the tutee is visiting for, and the reason of the visit such as homework help, code review etc. Each tutee is assigned a tutor. A tutor can tutor up to 5 students at a time. - The CS Lab also loans books to students for their use in the lab. A book contains book id, title and authors. A book can have multiple authors. A book is uniquely identified by its book id. - The CS Lab also loans out laptops to students for their use in the lab to complete their assignments and course work. Laptops have serial number, name, manufacturer. A laptop is uniquely identified by a serial number. Iou are allowed to make assumptions to complete the requirements provided above and those ssumptions should be stated and discussed in your project write up. (30 points) Conceptual Modeling: Create a conceptual model for the above requirements using the ER Model. Make sure to indicate primary keys, cardinality constraints, weak entities (if any), and participation constraints. There might be extra constraints which cannot be captured by the E/R diagram, make sure you mention them below the diagram if there is any. List any assumptions you make in the process. You can use drawing tools to create your ER models