Psuedocode

Background 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 II course to solve Trish \& Shaun's problem. Design a pseudocode or flowchart 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 first 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) Display Day's Sales Report e) Exit Program System Constraints: - Vehicle license plate number must be four (4) digits ending with no more than two (2) capital letters - Only unique license plate numbers permitted for each wash - Card payments attract 3% fees of the total service cost - Only three vehicles allowed for washing at the wash bay at a time - The car wash can accommodate twenty (20) cars at a time, excluding those at the wash bay - Prevent repeating selected services - Item a is only valid if car capacity is not reached - Items c and d are only valid if there is any vehicle at the car wash System Behaviour: Accept Customer's Information \& Payment (randomly tip 2% of cost) This functionality tracks the number of customers and stores their details in a file (binary or text). Prevent accepting further customers if the car wash is full. The customer's details include (but is not limited to) the system requirements above. Ask each customer whether he/she wishes to give a tip. Generate a random response (e.g.: y) and store the result. Display the customer's receipt. This includes the system requirements above. It also includes the total service cost, the tip percentage and amount (if any), and the grand total. Wash Car This functionality should keep track of the total number of vehicles at the wash bay. Once the wash bay is full - prevent further washing. Incorporate a method of clearing washed cars from the wash bay. Ensure this service is available only after payment. Display Returning Customers This functionality searches the file for all customers that appear more than once. It then displays their names, the total amount spent at the car wash, and the frequency of visits. Ensure this feature is available only if a vehicle is at the car wash. Display Day's Sales Report This functionality determines the total amount earned for each service, the total number of customers that visited, and the grand total earned (show tips separately) for a given day. Ensure this feature is available whether a vehicle is at the car wash or wash bay. Search for the most frequent returning customer. Once found, gift that customer a 20% discount voucher. Display the total that customer would pay after the discount