really need these broken down like a 5 year old level.

Murachs java 6th edition.. please break down or highlight what belongs where. just needing a better visual understanding.

Test and dobug the Invoice wot and deboug an ipptic ation. Trot the Iavuice application with invatld data like 51000 (enter the dotlar algn seof This should caine the application to 2. SFudy the emue meirage. Then, aser the line nuabber of the atement in the InvoiceApp class that caused the crash. 3. Cock on the link to that line of pode This showibl open the linwoiceApp.java tile in the cocke edeicer and highliytit the line of conde that caused the emor Froen this infonination, deternine the case of the problem and fix if. Set a breakpoint and step through the application. 4. Set a breakpoint on thii line of code: double di poount lereent o melteht... Then, dick on the Deber burtoe in the loolbar. This nins the project with the debuger on. 5. Display the cansole and enter a value of 100 for the rubtotal when prompted by the application. When you do, the applicatien runs to the breakpoint and siops. 6. Click the Variables tab to dinplay the Variables window. Then, note that the choice, castomer Type, and sebectal variables have been assigned values. 7. Press the keyboand shortcut for the Step Into button (IF in Netikeans, F5 in Eclipse) repeatedly to step throegh the application one statement at a time. After each step, review the values in the Variables wiodow to see how they have changed. Note bow the applicative steps theoghh the switch statement based on the customer ilype value and the iffelse statements botied on the subtotal value. 8. As you continue stepping throegh the code, note that the IDE steps through the methods of the Java API as well. Step through this code as much as yoa'd like. Then, elick the Continae (NetBeans) or Resume (Eclipse) button in the toolbar to continue the execution of the application. 9. Display the console argain and enter ty" to continue. Then, enter a value of 50 for the subtotat. 10. Display the Variables window agatia and inspect the values of the variables. Exercise 6-2 Test and debug the Future. Value 1. Use NetBeues or Eelipe to apen the act the do6 en2, Futare value project in the getDoubleo method in this file enose fururevalueApp.java file. Nose that the acfuturevalue metsod, and add a statement within loop is executed. 4. Run the application to see bow the satement works. Then, review the values that are displayed in the console and note that there's an extra month in the calculation. 5. Comment out the satement that prinst the debusging data to the console. Step through the application 6. In the maine method, sef a breakpoint on the first of the three statements that calcolate the furtare value. 7. Run the application and enter values when prompted. The application should stop at the breakpoint. 8. Experiment with stepping into, stepping over, and stepping out of the code of the application. At each step, note the values that are displayed in the Variables window and use them to find the logic error. 9. When you're done experitienting, click on the Finish Debugger Session or Terminate button and remove the breakpoint. 10. Fix the logic error. Then, nun the application again to be sure it produces correct results Exercise 6-1 Test and debug the Invoice application This exercise guides you through the process of ming NerBeans or Eelipee to test and debug an application. Test the Invoice application with invalid data 1. Use NetBeans or Belipe to open the chorieti Imoice project that's in the. ex starts directory. Then, teat the Invoice application with an isvalid subtotal tike $1000 (enter the dollar sign too). This should came the application to crash with a ruatime error and to display in error message in the convole. 2. Sady the error message. Then, sole the line sumber of the statement in the Invoice App class that caused the crath. 3. Click on the link to that line of cosle. This should open the InvoieeApp. java file in the code editor and highlight the line of code that caused the erroe. From this information, deternine the cause of the problem and 6x it. Set a breakpoint and step through the application 4. Set a breakpoint on this line of code: double di woountPereent = mitelh... Then, click on the Debug bation in the soolhar. This rans the project with the debugger on. 5. Display the console and enter a value of 100 for the sabcotal when prompted by the application. When you do, the application runs to the breakpoint and stops. 6. Click the Variables tab to display the Variables winduw. Then, note that the choice, customerType, and sutuotal variables have been assigned values. 7. Press the keyboard shortcut for the Srep Into button (F7 in NetBeans, F5 in Eclipee) repeatedly to step through the application one statement at a time. After each step, review the values in the Variables window to see how they have changed. Note how the application steps through the switch statement based on the customerType value and the iflelse statements based on the subtotal value. 8. As you continue stepping through the code, note that the IDE steps through the methods of the Java API as well. Step through this code as much as you'd like. Then, click the Continue (NetBeans) or Resume (Eclipse) button in the toolbar to continue the execution of the application. 9. Display the console again and enter " y " to continue. Then, enter a value of 50 for the subtotal. 10. Display the Variables window agaia and inspect the values of the variables