Featured Columns document driven approach is to have documentation produced in-line, or as a natural by-product of the project rather than as an after thought hurriedly pieced together at the end. It also provides a context in which configuration management has purpose, and the issues arising from inconsistent versions become apparent. In this way documentation is not an all-encompassing 'other' category, but a natural deliverable of each stage in the process. In supporting the thinking processes and providing checkpoints for review and reference, the value of the documentation is meant to become self-evident. However, from observing some student behaviour this is probably an over-optimistic view. In our projects I try to have the students take some responsibility for their projects and exercise judgement over their planning and execution. So they are required to develop their own plans outlining the methodology they will adopt, and identifying their key milestones and deliverables. It appears that many of them although theoretically adopting an iterative lifecycle, appear to become bogged down with completing their requirements specification. This may be partly a domain comprehension problem and indicate weakness in their analytical skills, but it seems to be more than this. In the project
/lp/association-for-computing-machinery/information-technology-accreditation-criteria-vqjWrjhwTt