Diary

  Individuals should acquire and keep up to date a small, bound, laboratory-style notebook to serve as a diary of activities carried out and time spent for the software development work. The entries must provide brief information for at least the following:

a.

time spent, date, agenda, and decisions for meetings held;

b.

time spent obtaining and learning technical information;

c.

time spent learning, formulating, or clarifying requirements;

d.

time spent in software/data-structure design;

e.

time spent in unit/integration/verification test design;

f.

time spent in management/project planning;

g.

time spent coding;

h.

time spent debugging;

i.

time spent testing;

j.

time spent learning/reviewing code to be maintained;

k.

time spent in maintenance coding/debugging/testing;

l.

time spent preparing documentation;