logo

Learning objective

Project documentation structure: The project is assessed in five sections. The table below lists the maximum available mark for each section of the project: Section Max mark 1 Analysis 9 2 Documented design 12 3 Technical solution 42 4 Testing 8 5 Evaluation 4 Total 75 For marking purposes, the project documentation should be presented in the order indicated in the table above. The table does not imply that students are expected to follow a traditional systems life cycle approach when working on their projects, whereby a preceding stage must be completed before the next can be tackled. It is recognised that this approach is unsuited to the vast majority of project work, and that project development is likely to be an iterative process, with earlier parts of the project being revisited as a result of discoveries made in later parts. Students should be encouraged to start prototyping and writing code early on in the project process. A recommended strategy is to tackle the critical path early in the project development process. The critical path is the part of the project that everything else depends on for a working system or a complete investigation result to be achieved.

Read the explanation, check the common trap, then practise with flashcards and questions.

At a glance

0

Flashcards

0

Questions

Topic

Overview

Subtopic

Project documentation structure

Aqa A Level Computer ScienceNon-exam assessment - the computing practical

Study support

Understand this objective

Quick explanation

Project documentation structure: The project is assessed in five sections. The table below lists the maximum available mark for each section of the project: Section Max mark 1 Analysis 9 2 Documented design 12 3 Technical solution 42 4 Testing 8 5 Evaluation 4 Total 75 For marking purposes, the project documentation should be presented in the order indicated in the table above. The table does not imply that students are expected to follow a traditional systems life cycle approach when working on their projects, whereby a preceding stage must be completed before the next can be tackled. It is recognised that this approach is unsuited to the vast majority of project work, and that project development is likely to be an iterative process, with earlier parts of the project being revisited as a result of discoveries made in later parts. Students should be encouraged to start prototyping and writing code early on in the project process. A recommended strategy is to tackle the critical path early in the project development process. The critical path is the part of the project that everything else depends on for a working system or a complete investigation result to be achieved

  • This point belongs to Overview, especially Project documentation structure.
  • You need to be able to project documentation structure: The project is assessed in five sections. The table below lists the maximum available mark for each section of the project: Section Max mark 1 Analysis 9 2 Documented design 12 3 Technical solution 42 4 Testing 8 5 Evaluation 4 Total 75 For marking purposes, the project documentation should be presented in the order indicated in the table above. The table does not imply that students are expected to follow a traditional systems life cycle approach when working on their projects, whereby a preceding stage must be completed before the next can be tackled. It is recognised that this approach is unsuited to the vast majority of project work, and that project development is likely to be an iterative process, with earlier parts of the project being revisited as a result of discoveries made in later parts. Students should be encouraged to start prototyping and writing code early on in the project process. A recommended strategy is to tackle the critical path early in the project development process. The critical path is the part of the project that everything else depends on for a working system or a complete investigation result to be achieved.
  • Use the linked flashcards and practice questions to check recall, then practise applying the idea in an exam-style answer.

Why it matters

This objective helps connect Project documentation structure to exam-style questions, flashcards, and revision notes for Overview.

Quick student answer

Which section of the project has the highest maximum mark?

Direct answer

Technical solution

Key terms

  • Critical path: The part of a project that everything else depends on for a working system or a complete investigation result.
  • Iterative development: A development process in which earlier parts of a project can be revisited because of discoveries made during later work.

Common trap

Confusing presentation order with development order: Present the final documentation in that order for marking, but develop the project iteratively and revisit earlier parts when necessary.

Related questions

Try this as a practice card

4 linked

Question 1 of 4

Choose an answer, get feedback, then move sideways through the set.

0 of 4 attempted

Flashcard prompts

Flip through the key recall cards

4 cards

Flashcard 1 of 4

Press Space to flip, arrows to move

Revision tools

Choose how to practise

Back to topic hub
Flashcards0 linked cards
No objective-specific flashcards are cached for this page. Use the topic hub to revise the surrounding flashcards without triggering a frozen-subject DB fallback.Open topic hub
Practice Questions0 linked questions
No objective-specific practice questions are cached for this page. Use the topic question bank to practise nearby curriculum questions without weakening the egress guard.Open topic questions

Related learning objectives