Output: Printing Messages For The User To See

Note:  Please keep the programs that you create today, in case you have a dispute about your grades for the ICEs at the end of the quarter. When you're working with a partner, each person should save their own, individual copy

 

Part 1: Basic Output

           

            For this exercise, you should trace through the file named Basic_Output_Trace.java, and trace through it using the OUTPUT Trace Table. As you can see from the Output Trace Table file, you will still be tracing the execution of the program, but you will be doing so in much less detail. 

The idea is two-fold: first, you should work towards being able to correct, quickly trace a program without having to through with a full and complete trace. Second, when the activity of tracing a program becomes less tedius & laborious, it becomes easier to use, and so you should also be working towards using this less formal approach to tracing more often (where applicable).  The Output tracing (as described in class) only requires you to list the output of the program, and represents a good compromise between tracing stuff informally on your own, and providing enough detail that the instructor can both see that you're doing things right (and therefore grade them).