Cash Receipt
Back to the Case Studies homepage
ProblemWrite a complete Java program that can be used by a cashier to generate customer receipts for an imaginary store which sells only three items. Make up the items and their costs. Use constants to store the cost of each of the three items and the tax rate.
Cashier: Sarah 2 brush sets at $ 8.0 3 paint sets at $ 40.0 4 primer at $ 18.75 Product Total: $211.0 Tax: $ 14.77 Total = 225.77 Expand the program to prompt the user to input the amount of payment given by the customer. Then calculate and output 1) the change (rounded to the nearest penny) and 2) the change rounded to the next highest nickel, and 2) the cashier’s name (again). To begin, add a comment as shown below so the marker can easily find this part of your program. //2B****************************************************** Variables: Add any new variables to the top of the program (with the variables from 2a). Input: Use JOptionPane to input payment given. Calculate: When finding the change, use Math.ceil to round up so the customer gets the full change, and possibly more. For example, if the change due is 4.637, round to 4.64 using pennies and 4.65 using nickels.
|
Funky Books | |
---|---|---|
SolutionThere are nine steps to improve this messy code so it complies with the company (and coincidentally, comp 1010) coding standards:
Organize the CodeFirst, organized code is vital to the readability of the code. The COMP 1010 Coding Standards give the foundation required to complete the code organization task for this case study. Each of the headings below describe a specific task that helps organize the code. Separate the StatementsThe code file contains more than one statements on each line. int digit1 = (isbn % 10);int total = digit1 * 9;isbn = isbn / 10; int digit2 = (isbn % 10);total = total + digit2 * 8;isbn = isbn / 10; Each of the above lines of code performs a similar function. Each line can be interpretted as a block of code. By placing each statements on a separate line and grouping the statements into appropriate code blocks, the result should look something like the following: int digit1 = (isbn % 10); int total = digit1 * 9; isbn = isbn / 10; int digit2 = (isbn % 10); total = total + digit2 * 8; isbn = isbn / 10; By placing each of the statements on a separate line, the readability of the code increases dramatically. Separate Statements into Code BlocksOnce the statements are readable, the next step would be to organize them into code blocks as stated in COMP 1010 Coding Standards. Continuing with our previous example, the functionality of the code can be broken into two distinct code blocks. int digit1 = (isbn % 10); int total = digit1 * 9; isbn = isbn / 10; int digit2 = (isbn % 10); total = total + digit2 * 8; isbn = isbn / 10; Almost each line of code in the messy code file can be considered a separate code block. Take the time to read the code and understand how everything works together before deciding which statements should be grouped together. One of the code blocks that should be added is a variable declaration code block at the beginning of the main method. Throughout the messy code, integers are declared. All of the declaration statements should be placed at the beginning of the main method to ensure the code stays organized. Going to the previous example, two declaration statements can be moved to the top as depicted below. int digit1; int digit2; digit1 = (isbn % 10); int total = digit1 * 9; isbn = isbn / 10; digit2 = (isbn % 10); total = total + digit2 * 8; isbn = isbn / 10; Add Comments to Explain the CodeThe COMP 1010 coding standards, or the Funky Books Inc. coding standards, make numerous points concerning comments in code. To be specific, statements 1, 2, 4, and 7 can be applied to the code file for this case study. All major code blocks should be identified by now. Look over each code block and briefly explain what it does in a comment. Since all declaration statements have been moved to the top of the the main method , make sure to apply coding standard 7 from the COMP 1010 Coding Standards. Optimize the Code by Removing Unnecessary VariablesAt the top of the main method, there should now be a number of variables declared. Notice that there are nine different "digit" variables which are only used once to store the same calculation. int digit1; int digit2; digit1 = (isbn % 10); int total = digit1 * 9; isbn = isbn / 10; digit2 = (isbn % 10); total = total + digit2 * 8; isbn = isbn / 10; The code sample from above shows two of the nine digit variables. These two variables can be replaced with a single one as follows: int digit; digit = (isbn % 10); int total = digit * 9; isbn = isbn / 10; digit = (isbn % 10); total = total + digit * 8; isbn = isbn / 10; Fix the Errors in the CodeThe messy code contained a total of eight different coding errors. Each error presented in this section is ordered as it appears in the code from the case study. Error OneString temp = JOptionPane.showInputDialog("") Technically, the above code does not break the functionality of the application as the method call still makes the input dialog appear to take input from the user. Although, from a usability standpoint the code does cause an error. The user who is running the application needs to know what to enter as input into the input dialog. Without a proper message, the user cannot be expected to know what the application is expecting as input. An example of a proper message is as follows: temp = JOptionPane.showInputDialog("Enter the first 9 digits of a 10-digit ISBN number."); Error Twoint isbn = Temp; There are two problems with the above code sample. The first problem being that the variable "Temp" is of type string and not of the primitive type int. The second problem is the name of the variable "Temp". The variable was originally declared as "temp" and Java is a case sensitive language. Both programs are repaired by replacing the code with the line below. isbn = Integer.parseInt(temp); Error Threeisbn = isbn // 10; An extra front slash changes the division operation into a comment which also comments out the semi-colon required at the end of every statement. Remove the extra front slash to correct the error. isbn = isbn / 10; Error Fourdigit = (isbn % 10) The statement above is missing the semi-colon at the end of the line. Add the semi-colon to fix the error. digit = (isbn % 10); Error Fivetotal = total + digit + 6; This error is known as a run time error. A run time error does not cause a compilation error, but it causes the program to produce incorrect results. In the explaination of the ISBN check digit, the sixth ISBN number should be multiplied by six, not added. This error is fixed by changing the second addition operation to a multiplication operation. total = total + digit * 6; Error Sixdigit = (isbn / 10); Just like error five, the above statement causes a run time error. To isolate the last digit in the ISBN number, the ISBN must have the modulus operator applied, not the division operator. The above statement is fixed by replacing the division operator with the modulus operator. digit = (isbn % 10); Error Sevendigit = (isbn * 10); The above statement is almost identical to #Error Six. The multiplication operator should be replaced with the modulus operator. digit = (isbn % 10); Error Eighttotal = total + digit - 1; The error in the code above is error five almost identical to #Error Five. Replace the subtraction operator with the multiplication operator to remedy this error. total = total + digit * 1; Add Code to Output Progress Reports as the Program ExecutesTo add progress reports to the program, three things need to be addressed:
By adding code to report on the status of the application, the user and yourself know what is happening behind the scenes when the program is executing. For a small application like this case study it may seem trivial. It is a good practice to get into as in larger programs consisting of many files each with many methods, it can be difficult to locate a run-time error in your code if the program does not explicitly say what it is currently doing. LocationBy now the code file should be broken up into multiple code blocks, as done earlier in this solution. Each code block should represent a major code segment in the program. Each code block can be considered a potential point for a progress report. Read over the code and decide which are vital points in the execution of the program. Report ContentThe next step is to decide what should be outputted to describe the progress of the program. This output can be the current value of a variable, an output statement saying that the program has reached a certain point in the code, or potentially a combination of both. A progress report should output data on the program that is relevant to its execution. For this case study, each calculation performed on the ISBN is vital to determining the check digit, therefore a progress report should output the value of each calculation. Adding Output CodeThe best way to add output to the program is by adding System.out statements to the appropriate code blocks. When adding the code, make sure the message that will be outputted is unique in comparison to the other progress report statements. Each statement should be unique as they are meant to identify the section of code being executed. If the statements are not unique, then there will be no way of telling which progress report has been outputted. Here is an example of the code before adding a System.out statement. //isolate last digit and multiply by 9 digit = (isbn % 10); total = digit * 9; isbn = isbn / 10; After the output statement is added, the code will look like the following: //isolate last digit and multiply by 9 digit = (isbn % 10); total = digit * 9; isbn = isbn / 10; System.out.println (digit + " * " + 9 + " for a running total of " + total); When the program is executing, the following output will appear in the progress window. The ISBN number used as input for the example below is 1-2345-6789. 9 * 9 for a running total of 81 Now the you will know what part of the code is being executed along with the status of the current calculation. Remember that this is not the only "correct" progress report. There can be many different progress reports based on how the vital points of the program were interpreted. Although, in this case study the calculations are exceptionally important points to the correct execution of the program. | ||
Code |