To be able to use the Time Recording Log to track your
development
time.
Instructions
Review the Instructions for the Time Recording Log.
Obtain
blank copies of the form you need.
Read the attached Scenario that describes the work of Rob, a
student
completing a class programming assignment. As you read and
interpret
the scenario, record the data in the appropriate places in the Time
Log. If you are uncertain how to fill in the forms, refer
to the form instructions or consult the instructor.
Unit Development Scenario
Programmer Mike arrives to work at 8:50am. He starts his computer and
talks to his colleagues until 9:15am about the football game this past
weekend. At 9:16 am his boss tells him to implement the flight control
stability module for their third-party partner. He gets started right
away. First, he finds all the PSP data forms he needs. Second, he pulls
up the requirements from the joint avionics database. Finally, he reads
them and decides he knows enough to make an estimate of 240 minutes. At
9:31 am he pulls out his notepad and starts writing down some UML
diagrams and pseudocode. At 9:34 am his good buddy John sends him an
e-mail with a really funny video and pesters him until he watches it.
The finally stop laughing at 9:45 am when he goes back to his notepad.
At 10:12 am he decides that he is ready for code but wants to take a
break and talk to the receptionist. At 10:32 am he opens his favorite
text editor and starts typing in Java statements. All goes well until
10:43 am when he realizes he was completely missing an algorithm to
handle low speed situations. He designs this algorithm and continues
coding. At 11:00am he decides to stop and go to lunch. At 11:44 am he
returns to work and finishes coding at 12:22 pm. He then proceeds to
hit the compile button. He receives a syntax error stating a missing
semi-colon. He then receives an error "undefined identifier" and
realizes he mistyped the identifier name.
Finally at 12:30 pm he compiles clean. He then proceeds to
write unit tests. One of his unit tests fails at 12:44 pm he realizes
his design was wrong for the low speed handling algorithm he put in
during the coding phase. He fixes this error and then fails another
test noticing he forgot to add a loop increment while coding. After
repairing the loop, the program compiles cleanly. Now the first unit
test is failing again. Puzzled, he studies his solution. After a while
he realizes when he added the loop increment it was put in the wrong
place. Finally all of his tests pass at 1:22pm. He then proceeds to
fill out the project summary forms. His total line of code count was 88
without comments.