4. Testing & Reflection

Once your program is complete, it’s time to test it and get feedback. You’ll have someone use your program and record their thoughts on its functionality and usability. After testing, you’ll analyze your results, reflect on how well your program meets its original goals, and consider how you could improve both your program and your development process. This final stage helps you learn from your experience and prepare for future programming projects.

Requirements: Testing & Reflection

By the end of this stage, you must submit a Testing & Reflection Report, which evaluates your program’s performance and your development process. This stage builds on Stage 3: Coding & Development by testing the program, gathering feedback, and reflecting on improvements. You will also analyze what worked well and what could be improved if you had more time.

Use these headlines in your document:

1. User Testing & Feedback

Select a user to test your program (a classmate, teacher, or another person).
Ask them to use your program and provide feedback on its functionality and ease of use.
Record their observations, comments, and suggestions for improvement.
Summarize what the user found easy, difficult, and what they would change.

Format: Include this section as a table in your Stage 4 document.

2. Program Evaluation

Compare your final program to your original Project Brief (Stage 1).
Identify which planned features were fully implemented, which were modified, and which were not included.
Explain why any changes were made and whether your program meets its original purpose.
This is related to the Development Log from Part 3 and you should refer to it, however this Program Evaluation should be in paragraph format and should focus more on comparing the completed work to the original idea of the final outcome.

Format: A structured paragraph comparing the original idea with the final outcome.

3. Reflection on Improvements

If you had more time, what improvements would you make to your program?
Identify two specific areas you would enhance (e.g., adding more features, improving efficiency, better UI).
Explain why these improvements are necessary and how they would benefit users.

Format: A structured paragraph discussing areas for improvement.

4. Reflection on the Development Process

Reflect on your workflow and problem-solving approach throughout the project.
Identify what went well and what challenges you faced.
Explain what you would do differently if you repeated the project.
Mention how your planning from Stage 2 influenced the final outcome.

Format: A structured paragraph discussing what worked, what didn’t, and lessons learned.

Stage 4 Rubric: Testing & Reflection

Each section is assessed on completion, clarity, and correctness, ensuring logical progression from Stages 1, 2, and 3.

User Testing & Feedback

4 – A tester used the program, and their feedback is well-documented with clear insights.
3 – A tester used the program, but feedback lacks detail.
2 – A tester used the program, but feedback is unclear or missing key points.
1 – No user testing feedback is recorded.

Program Evaluation

4 – All features are reviewed, with clear explanations of implementation and changes.
3 – Most features are reviewed, but some explanations are missing.
2 – Only a few features are reviewed, with little detail.
1 – Program evaluation is incomplete or missing.

Reflection on Improvements

4 – Identifies two areas for improvement with clear explanations of benefits.
3 – Identifies improvements but lacks depth in explanations.
2 – Mentions one improvement, but lacks clarity.
1 – No reflection on possible improvements.

Reflection on Development Process

4 – Well-structured reflection on workflow, challenges, and lessons learned.
3 – Reflection includes challenges but lacks depth.
2 – Basic reflection with minimal insights.
1 – No meaningful reflection on the development process.