Introduction
The concept of the project log is simple.
This means you have the incentive to find the time to maintain it.
It is powerful enough to be of real value.
So what is a project log ?
Basically it is a set of five overlapping structured documents called logs.
The logs contain similiar types of information but for different reasons.
The information redundancy helps to ensure that you avoid missing anything important.
Design Log
The Design Log provides you with a method of recording design decisions and all the supporting arguments for and against each decision.
Whenever you have one of those eureka moments, a quick browse through the Design Log will remind you that you tried to implement the
idea six months ago and that you found it was not feasible.
The Design Log should contain:
Descriptions of each design issue to be resolved.
All design issues should be documented
including the simple ones which do not appear to have any alternative solution.
A list of alternative designs.
Arguments for and against each design.
A detailed description of the chosen design.
It is often the case with Rapid Application Development that this stage is not documented
and if it is, it does not always keep pace with the RAD changes.
|
Design;Contents
Introduction
Contents Anchor2
Contents Anchor3
Conclusion
[HTML raw TABLE, TR, TD]
[HTML TABLE, TR, TD, P]
[HTML TABLE, TR, TD, P]
[HTML TABLE, TR, TD, P]