Completing the Time Recording Log Form
Objective
Rob is assigned to write a simple Address Book application. Rob begins work [7:30] by gathering all the resources he needs to begin. He reviews the assignment directions to be sure he understand how the Address Book is supposed to operate. [7:40] Rob creates a conceptual class diagram of the main components in his solution. He notes next to each class what its responsibilities are. On a different page he sketches a conceptual picture of the data structure he plans to use. Then he writes a couple of sentences describing what each method will do. He mentally walks through each of the requirements to be sure it can be carried out with his planned design. [8:12] Rob thinks that inserting a new person will be the toughest task, so he writes some pseudocode for the logic of that operation. [8:33] Rob gets up to stretch and goes to grab a soda. While he's in the kitchen he cleans up his dinner dishes.
Returning with a soda, [8:49] Rob opens a text editor and types "public class AddressBookApp". He studies his design notes and starts creating Java statements for the solution and simultaneously typing them into the editor. The first three methods go smoothly, but he gets confused when working on the delete method [9:14]. He realizes his design didn't take into account two people with the same name living at different addresses. So he adds some notes to his design papers to clarify that issue. He then corrects something in a previous method and continues coding the delete method [9:20]. While coding the remainder of the solution he is interrupted by a 3 minute phone call from Janet who wants to confirm they are meeting in the library the next morning. He completes coding without incident, finishing at 9:43. Rob takes a bathroom and stretch break.
At 10:01 Rob compiles his class
and gets several error messages. One by one, he looks at the
error message, finds the line of code, identifies the mistake, changes
the code and recompiles it. He fixes seven errors this way. The
program compiles without error at 10:23. It's late, so Rob calls
it a night.
Now for the tedious task of adding comments. Rob spends fifteen minutes adding comments to his program. He then compiles the program once more to be sure he didn’t introduce a syntax error and the program compiles cleanly [3:01].