Term 3 Week 8 - Week 5

Evaluate, Package and Submit

Finalise the product, complete the evaluation and submit a complete LMS evidence package.

Learning Goals

  • Finalise product features without breaking the working version.
  • Complete evaluation against requirements.
  • Organise evidence in rubric order.
  • Check filenames and LMS upload instructions.
  • Submit the final product and evidence package.

Five-Lesson Sequence

1

Final product stabilisation and feature freeze.

2

Complete evaluation against requirements and success criteria.

3

Assemble the evidence document in rubric order.

4

Complete final checklist and peer evidence check.

5

Submit through the LMS and confirm files open.

Current Stage: Iterate and Evaluate

Evaluate

Improve the product and judge the final solution against the requirements.

Checkpoint: The final evidence package tells the complete project story.

Iteration log
Final screenshots
Requirement evaluation
Limitations
Future improvements
LMS submission

Detailed Lesson Build Pathway

Lesson 1

Feature Freeze

Protect the working product before final evidence is prepared.

  1. Save a final working copy.
  2. Stop adding risky new features.
  3. Run the main test path again.
  4. Capture final product screenshots.

Evidence: Final product screenshots and final run check.

Lesson 2

Evaluation Against Requirements

Judge the product using the success criteria from Week 1.

  1. Copy each requirement into the evaluation table.
  2. State whether the product met, partly met or did not meet it.
  3. Use evidence from the product or test results.
  4. Explain one limitation honestly.

Evidence: Completed evaluation table.

Lesson 3

Evidence Document Assembly

Organise the submission so it can be marked efficiently.

  1. Place evidence in rubric order.
  2. Add captions explaining each screenshot.
  3. Check that algorithm, code, testing and evaluation evidence are all present.
  4. Remove duplicate or unclear screenshots.

Evidence: Draft evidence document.

Lesson 4

Final Checklist and Peer Review

Catch missing evidence before submission.

  1. Swap checklists with a peer.
  2. Confirm the product opens or runs.
  3. Confirm file names follow the required pattern.
  4. Fix missing evidence before the final lesson.

Evidence: Completed final checklist.

Lesson 5

LMS Submission

Submit a complete, accessible final product.

  1. Upload the final product file or paste the final product link.
  2. Upload the evidence document and any separate planning/testing files.
  3. Write a short LMS comment explaining how to open the product.
  4. Confirm the submission has saved.

Evidence: Submitted LMS package.

Key Build Steps

Finish evidence

  1. Evaluate requirements
  2. Add final screenshots
  3. Check rubric order

Submit

  1. Name files correctly
  2. Upload to LMS
  3. Confirm access

Student Checklist

  • My product opens
  • My evidence follows the rubric
  • My evaluation uses evidence
  • My files are named correctly
  • My LMS submission is complete

Common Mistakes to Avoid

Changing code after testing

Freeze the product and only make low-risk fixes.

Evaluation is only a description

Judge each requirement using evidence.

The teacher cannot open the product

Test the final file or link from a clean browser or device.

Useful Guides This Week

Define a Product Worth Building

Define a useful, realistic and assessable Study Session Helper Program.

Prototype and Wireframes

Plan the product experience before writing the final code.

Algorithm Design

Plan the logic so the product has clear processing, decisions and repetition.

Build the Minimum Viable Product

Build the smallest working version first, then extend it safely.

Test, Validate and Iterate

Use evidence to prove the product works and improve it before final submission.

Final Submission

Prepare a complete LMS upload that can be marked and moderated.

Weekly Checkpoint

Final product and evidence package submitted through the LMS.