OntarioTech IT Sales & Services database: Your task is to design an Entity-Relationship diagram and its relational schema for the company's database, which includes computer sales and service tickets. Your ER diagram must reflect the requirements/specifications and business rules given below: . An IT sales representative may sell many computers, however a computer is sold by only one representative; . A representative writes an invoice for each computer sold; A customer may purchase any number of computers, but each computer is purchased by a single customer; A customer receives an invoice for each computer purchased; . A customer may not come to OntarioTech to purchase a computer, but to have a computer repaired instead; . If a customer brings one or more computers in for repair, a repair/service ticket is generated/written for each computer; . OntarioTech keeps a record or service history for each of the computers repaired. Repair tickets are referenced by the computer's serial number; . A computer brought in for repair can be serviced by many technicians, and each technician may work on multiple computers; A computer repair may require computer parts (e.g., memory, GPU, mainboard, harddrive, etc.) or just a software refresh or something that does not require any parts; . Computer parts should be kept in the database even if they are not used in a repair. . A service has an associated hourly rate. Question 1 Design an ER diagram to model OntarioTech IT Sales & Services' database. Make assumptions about what pieces of information each entity should carry (e.g., attributes, primary and foreign keys, etc.). Please rules that are not captured in your diagram. Hand draw your diagram, take a photo and submit it. Submit an image file (jpg, png, bmp, pdf) with your diagram. Upload Choose a File Question 2 Based on the ER diagram you designed in (1). create its corresponding Relational Model. It's just text, not a diagram.