Quicklube is in the quick oil and lube business. although customers bring in their cars for service described as quick oil changes, quicklube also replaces windshield wipers, oil filters, and air filters, subject to customer approval. the customer invoice lists the charges for the oil used, all parts used, and a standard labor charge. when quicklube presents the invoice, customers pay cash, use a credit card, or write a check. quicklube does not extend credit. quicklube needs a database designed to keep track of all components in all transactions. given the high parts usage of the business operations, quicklube must maintain careful control of its parts (oil, wipers, oil filters, air filters) inventory. therefore, if parts reach their minimum on hand quantity, they must reorder the part in question from an appropriate vendor. quicklube maintains a vendor list that contains both the vendors, actually used as well as potential vendors. quicklube also tracks each customer’s car mileage. periodically, quicklube mails updates/reminders to customers, based on the date of the car’s service and the mileage. based on the information provided: 1) draw the erd (entity relationship diagram) for quicklube: draw the erd using crow's feet notation. use ms visio and save your final drawing as a pdf. 2) on a separate page(s): clearly list all the entities with a list of the attributes below each entity. 3) make sure you clearly mark/label the primary/identifier key attribute(s) (pk) for each entity. 4) also, make sure you clearly mark/label any foreign key attributes (fk) for each entity. 5) provide a list of any business assumptions that you made while developing your erd.