Problem Description: The Colorado Tool and Dye Corporation, Inc. (CTDC) sells construction equipment in Colorado, New Mexico, Arizona, and Utah. CTDC needs a business report of the sales for each day, and your job is to write program that will take sales data from a computer user, aggregate it, and produce a report. The report should begin by asking the user to input the state (CO, AZ, NM, or UT), sale date, and sales tax rate for the given state- this data should be input by the user ONCE at the start of the report and then be displayed back to the user only once - this is the report header. The user should then input the sale ID and the pre-tax sale amount for a sale. Next, the report will display an output line showing the sale ID, the pre-tax sale amount, and the post-tax sale amount paid by the customer (this output will be shown after the data is input for each sale). After all sales records are entered and displayed, the user should enter exit as the sale ID to indicate they are done entering sales information, and then a report summary should display the total pre-tax sale amount, the total post-tax sale amount and the average post-tax sale amount. The summary must also report the "sale with the highest post-tax sale amount" by displaying the highest post-tax sale amount and associated sale ID. In the event that there are multiple instances of the largest post-tax sale amount only the first instance should be reported. Note that the pre-tax sale amount is the listed price- similar to a MSRP- Manufacturers Suggested Retail Price. The post-tax sale amount is the actual amount of the sale after taxes have been applied- (see the formulas below). The sales tax rate will vary by state, so it is an input field. The state sales tax rate should be INPUT as a decimal. For example, if the sales tax is 11%, the user should input 0.11. All monetary inputs should be displayed with two decimal positions and should be expressed in dollars and cents (using the $ sign when appropriate).* All monetary outputs should be displayed with the decimal positions and should be expressed in dollars and cents (using the $ sign when appropriate).* Just to be clear, the sales data for each state is entered as a batch process at the end of the day. Users of the program at CTDC will enter the data which consists of the state, sale date and sales tax rate (these three fields are input once) followed by each sale record containing the sale ID and pre-tax sale amount. Users will enter exit (just the letters e x i t, they will not enter double quotes) as the sale ID when they want to exit the program and prompt the output of the final report (which consists of the total pre-tax sale amount, the total post-tax sale amount, the average post-tax sale amount, the highest post-tax sale amount and the associated sale ID.

Page 2 of 4 The average post-tax sale amount is determined by dividing the total post-tax sale amount by the number of sales that day. *Formatting considerations such as using dollar signs ($), percentage signs (%), and decimal places only need to be considered when you are actually programming. You do not need to consider these requirements when writing the human-level or program-level walk-throughs, the hierarchy chart, the flow-chart, or the pseudocode. Each time the program is used, the program only needs to deal with a single state (like CO), but you need to let the user specify which state they want to input the data for. Each store has a $35,000 pre-tax sale amount limit for any one sale. This means that if a sale has a pre-tax sale amount of more than $35,000, then the program should prompt the user for a sale subtotal amount less than $35,000. A subset of data for a typical day is given for you to test your models. CIS 2110 Project #1 Test Data CTDC Daily Sales State: CO Date: June 1, 2023 State tax rate: 6.5% sale ID Pre-tax sale amount 111 12345.67 222 24387.65 333 9876.54 444 7865.43 555 5555.55 exit

Page 3 of 4 Deliverables for Project 1 Develop the Implementation Model using Pseudocode and make certain you: Have a minimum of five modules in your pseudocode (a deduction will occur if there are fewer than five modules). It is recommended that you look at the Essential Model for this problem to help divide the logic into modules. Your project should be in Microsoft Word format. Notes: 1. If you have previous experience with programming concepts such as arrays and lists, please avoid using them in this problem. Stick with the concepts discussed SO FAR in this course. (There will be plenty of opportunity later in the course to demonstrate your sophistication). Tips for understanding project 1 The "order of operations" of what is supposed to happen for the problem is as follows... 1) A user enters the state, the date, and the state sales tax rate. The sales tax rate would be different for each state, so you need to let the user enter it- you dont want it hard coded. 2) The program will output the state, date, and sales tax rate. 3) The user will input the sale ID. 4) The program should output the sale ID. 5) IF the sale ID is entered as exit, the program should output the summary numbers (the final report). 6) IF the sale ID is NOT exit (the kill flag), the program should prompt the user to input the pre-tax sale amount for that sale. 7) The program should output the pre-tax sale amount for that sale.

Page 4 of 4 8) The program should check to see if the $35,000 limit for the pre-tax sale amount has been exceeded. If it has- the program should return to step 6 and ask the user for a valid sale amount. 9) The after-tax sale amount should be calculated for the sale. The after-tax sale amount is equal to the pre-tax sale amount multiplied by (1 + tax rate). So, if the pre-tax sale amount is $1000 and the tax rate is 5%, the post-tax sale amount is equal to: 1000 * (1 + 0.05) Which evaluates as: 1000 * 1.05 Which evaluates as: $1050 10) The program should update the count of the number of sales that have been entered. 11) The program should calculate relevant values (total pre-tax sale amount, total after-tax sale amount, etc.) 12) The program should then return to step 3, which asks the user for the next sale ID.