Exam-style question
Try this first
Explain why the order used to present project documentation for marking does not require the project itself to follow a fixed traditional systems life cycle.
Model answer
What a good answer should say
- The documentation is presented in the specified order so that it can be marked consistently: analysis, documented design, technical solution, testing and evaluation.
- This order does not mean that development must proceed through those stages once, in that exact sequence.
- Project development is likely to be iterative, so discoveries made during later work may require earlier parts to be revisited.
- Students should also begin prototyping and writing code early rather than waiting for every earlier section to be completed.
Explanation
Why this works
The specification separates the required presentation order from the way the project is developed. The presentation order supports marking, while an iterative process allows the work to respond to discoveries during development.
Common mistake
No common mistake is linked to this question yet.