PSP Class Practice 1 MARCIA begins work her program [10:00] by reviewing the requirements in the assignment package, including the test requirements, to be sure she understands them. She copies the requirements to her note pad. Then, based on the data presented on past student performance and MARCIA’s feeling about her own performance, she estimates that this assignment will take three hours. She writes this estimate on her Project Plan Summary [10:26].

PSP Class Practice 2 MARCIA starts to design the program [11:10]. She studies the requirements and sketches out a diagram of the data structure. She is done at [12:10] and decides to go to lunch. MARCIA starts coding [1:30]. While working on coding, MARCIA is interrupted by a classmate who doesn’t understand how to get started. MARCIA spends 30 minutes explaining how to use the PSP0 process forms and then gets back to coding. MARCIA finishes coding all the routines, checks to make sure she hasn’t missed anything [3:40] and fetches a fresh cup of coffee before compiling.

PSP Class Practice 3 MARCIA compiles the program [4:00] and gets and error message, unbalanced parenthesis. Looking at the compiler output, MARCIA sees where the missing parenthesis belongs and fixes the source code [4:07]. MARCIA recompiles the program and gets another error message, undeclared identifier [4:08]. Surprised, since she thought she declared this identifier, MARCIA searches through the source code and discovers that the identifier she declared had and ‘-‘ in it [4:11]. MARCIA again recompiles the program and gets an error message at the end of the program, unmatched lines [4:12]. After reviewing the program logic for a few minutes, MARCIA spots where the missing end belongs and fixes the source code [4:18]. MARCIA recompiles the program and this time, there are no compile errors [4:19]. MARCIA is done for the day.

PSP Class Practice 4 The next day MARCIA loads the program and begins executing the first test case [10:10]. The program prompts MARCIA for the input data file name and MARCIA types it in, but nothing happens [10:11]. MARCIA invokes the debugger, traces the program execution, and discovers it is in infinite loop. she studies the source code for the loop and spots the problem - a pointer was not incremented within the loop[10:43].

PSP Class Practice 5 MARCIA corrects the source code, recompiles the program and begins executing the first test case again. This time, the program outputs some results, but the print format is wrong, so MARCIA can't tell if they're correct[10:45]. MARCIA fixes the print format [10:55] and retries the first test case [10:56]. The format is OK now, but the answers are wrong. MARCIA reviews the program logic and looks at some variables with the debugger. After studying the code and the results, MARCIA realizes her initial design was flawed and it needs to be written [10:59].

PSP Class Practice 6 MARCIA rewrites the routine and recompiles it[1:51]. This time there is no errors. MARCIA re-executes the first test case and this time, the results are good [1:54]. MARCIA executes the next two test cases and both give the correct results [1:57]. MARCIA finds her Plan Summary form and begins filling it in [1:58]. It takes her 13 minutes to complete the Plan Summary. Filling out the Plan Summary and doing any other cleanup is called the Postmortem Phase.