Backoround This project is designed to test your ability to implement the concepts learnt in this course. Specifically, you will have to demonstrate the proper use of arrays, modularity, structures, pointers and files. The grading scheme at the end of this document is designed to measure how well you have implemented each of the above concepts. Scenario Trish and Shaun own a car wash called "Trish \& Shaun's Auto Wash Services." Business is booming, as customers are flocking to their establishment by the dozens. However, they have a situation, The car wash is small and can only accommodate washing three (3) vehicles at the wash bay at a time. On top of that, the car wash total vehicle capacity is twenty (20). However, this does not include those in the wash bay. Meanwhile, they use a paper-based system to document their daily activities. This results in a slow, tedious reporting process. Finally, they want a way to better track their returning customers. This will allow them to gift those customers. Use the concepts you learned in the Programming Il course to solve Trish \& Shaun's problem. Design a pseudocode or llowchart prior to your program implementation. See the services offered and their cost associated with each below: System Requirements: - Transaction date [dd/mm/yyyy] - Customer's frst name and last name - Customer's vehicle license plate number - Payment method - cash or card - Service(s) required System Functionalities: a) Accept Customer's Information \& Payment (randomly tip 2\% of cost) b) Wash Car c) Display Returning Customers d) Displry Day's Sules Reroirt ej Exil Proseram System Constrints: - Vehicle license plate number must be lisur (4) digits endinge with nes mare than two (2) capital letters - Only unique license plate numbers permitted for cach wash - Card paymens attract 3% fees of the total serrice cost - Only three vehicles allowed for washing at the wash bay at a time - The car wash can accommodabe twenty (20) ears at a time, exeluding those at the wash bay - Prevent repeatirur selested services - Item n is amly valid if car capacity is not reached - Ilerns c and d are only valid il there is any vehicle at the car wash Syslem Behaviour: Lccept Cistomer's lifformation \& layment (randomly tip 2% of cost) This fumctionality tracks the number of cuscomers and stores their details in a file (binary or text). Prevent accepting further customers il the car wash is luld. The customer's details include ibut is not limited tol the system requirements above. Ask cach customer whether he'she wishes to give a tip. Generate a random response (e.g.: yin) and store the result. Display the customer's receipt. Ihis imeludes the systern neyuirements above. It alsa includes the total service cost, lhe lip percentage and amount (if anyy), and the grand total. Wiash Sar This funcionality should keep track of the total number of vehicles at the wash bay. Once the wash hay is full - prevent further washing. Ineirporate a method of clearine washed cars from the wash bay. Eusure this service is arailable only after payment. Display Returning Customers This fumctionality searches the file for all customers that sppear more than onee. It then displays their names. the total amoun spen at the car wash. and the frequency of visits. Ensure this feacure is available vrily il a vehic]e is al the car wash. Display Duy's Sales Report This lunctionality determines the total amount eatned tor each service, the total number of custoness Search fior the most frequent returning customer. Onee found, gitt that custamer n20% discount voucher. Display the cotal that customer would pay after the discount. Project Objectives Project Management Modularity through Problem Division and Dissemination Teamwork through division of Solutions Menu-Driven System Pouthers Files Dara Structures. Lnions, Enumerated Types, Random Numbers and Macros. Please note iha the sy:fem shotd be user-friendly and use error-messaziny b dbplay all validaion and wher erors. The systen nay aloo store dain oher ifan thuse explicity staied ubve. Snbmission You are required to submit 1) Submit a cover sheet indicating the names and identification numbers of all group memhers, along with a detailed report outlining each component (for example, function, struct, et cetera) of the projecr implemenred by each group member. 2) Submit a signed copy (one by each group membery of the "Declaration of Authorship" form. 3) Subrril the source and execulable code. 4) Be present and on time lor an irlerview to delend your project solution. Login ingrmanon shoidd te clenty irwicated jor ife furor to access the system. Documentation .25% V Agoribm (Pscudooodc or Flow Chan) 20% V Source code contains appropriate documentation and indention 5% Implementation of l1 soures code finm Psendncode or Flow Chart. 50m v Use of struetures 5% Use of amays 5% V Use of pointers 10% V Use ol functions 10% V Usc oliles 10% Correct functionality. 10% Interview: ability to explain ecde logie proficiently .15%/ Tulil: 100% 1. Unauthorizod late submission - 10% per day. After three day's the assignment will not be accepted. 2. Identical assignments. Please read your Student Handsook for the University's Policy on Academic Misconduci. 3. Lack of neatness and orcanization. 4. The inability of a group member to explaiin the wode and lugie approach laken. Nule thal any member of the eroup may bo ealled upon to explain any area of the system regardless of the tasks performed in the project. 5. Unauthorizad lareness or absenee fiom the interriew will result in the project NOT being graded. NOTE: 1. Marks are indiqidually assigned based on an interyiew and member contribution to the development of the project in the group. 2. Groups erceeding 4 members ill be penalized