This project requires you to create a database design. Your design will be documented in a set of Entity$-$Relationship diagrams using the representation as shown in the lecture materials. Draw a set of Entity$-$Relationship diagrams to model the following scenario.You are the database administrator for Working Bytes Inc., a software development corporation that writes and sells a suite of business programs and solutions. The company has grown to the point that the manager for Customer Relations has requested a customer contact program $($CRM$)$ be created to track all interactions with customers. Most of these interactions will be customer reports of difficulties or deficits in one or more of your products. Some of the interactions will be queries regarding products that will be either forwarded to the sales staff or to the support staff based on the nature of the contact. Most contacts will be through phone conversations, but some will be email contacts.After reviewing the requirements from the manager for Customer Relations, you have broken down the database into specific entities.note: this ER Diagram represents only the one part of your business that deals with operations. As such you will not be including any details or data regarding employees or data on the actuai suppliers.This is an overview and as such not all data points will be included. For example, the EMPLOYEE entity will contain just basic details and not full information like address, age, etc. You will need to track these data entities..A COMPANY is any organization that has purchased one or more software solutions fromWorking Bytes Inc.$*$ A CUSTOMER is a person from the COMPANY who is assigned to represent the COMPANY during any contacts with Working Bytes Inc.$*$ A CONTACT is any interaction with a CUSTOMER from an outside company.$*$ A PRODUCT is any of the software solutions created by Working Bytes Inc..A TICKET is the notation for any actionable item based on the contact. This could be notation of a software bug, or a notation of an addition required. A TICKET represents any action required. An EMPLOYEE is any person currently or previously employed by Working Bytes Inc. For the CONTACT, your design must be able to store:$*$ the Incident Type $($i$.$e$.$ requesting help, reporting a bug$/$error$,$ general comment, etc.$).$the Contact Date$*$ the relevant foreign keys $($if any$)$For the COMPANY, your design must be able to store: the company's name $($i$.$e$.$ Boeing Aerospace, GM Cami Industrial, etc.$)*$ not guaranteed to be unique $($i$.$e$.$ two companies could have the same name, etc.$).$the relevant foreign keys $($if any$)$For the CUSTOMER, your design must be able to store:the customer's last name $($i$.$e$.$ Smith, Jones, Huang, Nasser, etc.$)$ the customer's first name $($i$.$e$.$ John, Jane, Anisha, Yunfei, etc.$)$ the relevant foreign keys $($if any$)$For the PRODUCT, your design must be able to store:the product's name $($le$.$ WSIB Manager, OMERS Calculator, etc.$)$not guaranteed to be unique $($i$.$e$.$ two products could have the same name, etc.$).$the relevant foreign keys $($if any$)$For the TICKET, your design must be able to store: the creation date $($date the ticket was opened: January $12,2024,$ etc.$)$the completion date: optional $($date the ticket was closed as completed: February $7,2024,$ etc.$)$ the notes associated with this specific ticket $($i$.$e$.$ details of what and how of the complaint$).$the relevant foreign keys $($if any$)$For the EMPLOYEE, your design must be able to store:the employee's last name $($i$.$e$.$ Smith, Jones. Huang. Nasser, etc.$)$ the employee's first name $($I$.$e$.$ John, Jane, Anisha, Yunfei, etc.$)$ the relevant foreign keys $($if any$)$