Record (revised)

Why record?

Keep recording is important during the design process, not just record the correct result,
but also the mistakes; as it might help to get the develop process smoother and prevent the same mistake happen again.

According to Budd (1996), it is important to keep recording the procedure during the development process;
even though it might not be the final result, yet it may help to inspire the new or better ideas.
“Important to produce this (record) while the ideas are fresh, not in hindsight when many details will have been forgotten.” Said Budd (1996)

Record is not only being valuable during the design process,
as well as benefit for maintenance stage,
as Potts and Bruns mentioned,
“Without such a record a maintainer may repeat mistakes that were made by the original designer…” (p418,1987)


Reference

Budd T.A. 1996, p37, “Responsibility Driven Design”, Introduction To Object Oriented Programming, accessed 28.4.2009 from cs.kun.nl

Potts C and G Bruns, 1987, p418, “Recording the Reasons for Design Decisions”, accessed 28.4.2009 The ACM Digital Library


The meaning of Records within our course

- may refer to keep the evidence and progress of our work.
Some courses require us to write or draw on the journal; some may need us to show works to tutor regularly.
Collaboration Studio is a computer based course,
so we are required to update our individual blog and team blog in order to show the efforts we put in this course,
not only for tutors, but also colleague.

Moreover, we also share our knowledge on the class wiki,
which another way to record our contribution to this course.