Overview common mistakes

Common mistakes

• Focusing mainly on the report

  Treating lengthy supporting documentation as more important than creating the programmed solution.

  Fix itPrioritise the programmed technical solution, which receives 42 of the 75 available marks, while keeping the required documentation concise.

• Assuming a student must already know the field

  Concluding that a student cannot choose a topic because they do not already have knowledge of it.

  Fix itThe student may choose the topic if they are in a position to find out about the field. They must also consider whether the topic provides enough opportunity to demonstrate the necessary technical skill.

• Confusing presentation order with development order

  Assuming that the project must be completed in the exact order of analysis, documented design, technical solution, testing and evaluation.

  Fix itPresent the final documentation in that order for marking, but develop the project iteratively and revisit earlier parts when necessary.