Design, build, test and evaluate the supplied Study Session Helper Program using the Software Development Cycle.
Project Structure
The project uses a fixed Study Session Helper scenario. Each stage creates evidence for the final marking rubric.
State the problem
Understand the user problem before building.
Plan and design
Turn the idea into a planned interface and logic model.
Develop
Create the minimum viable product first, then add features carefully.
Test
Check whether the product works and whether it meets the user need.
Evaluate
Improve the product and judge the final solution against the requirements.
Teaching Sequence
Term 3 Week 4
Week 1
Define a realistic Study Session Helper scope, then define the user, problem, requirements and success criteria.
Term 3 Week 5
Week 2
Create wireframes, user flow, pseudocode, flow chart and trace table evidence before full development.
Term 3 Week 6
Week 3
Create the smallest working version first, then add required programming concepts and evidence.
Term 3 Week 7
Week 4
Use normal, boundary and invalid testing, then validate the product with a user and iterate.
Term 3 Week 8
Week 5
Finalise the product, complete the evaluation and submit a complete LMS evidence package.
Required Product
User: A Year 12 student preparing for assessments.
Collect the student name or session label, study topic, available minutes and confidence or priority rating.
Stretch: Validate blank topics, impossible times and ratings outside the allowed range.
User: A student revising a course topic.
Ask at least three questions, flashcards or prompts and track attempts, score or completion.
Stretch: Add categories, random questions, retry logic or a weakness summary.
User: A student deciding what to study next.
Use selection to give different advice based on confidence, score, available time or priority.
Stretch: Add low, medium and high confidence bands with specific next steps.
User: A student completing a short study session.
Use iteration so the user can answer multiple prompts, repeat a menu action or complete another topic.
Stretch: Add a menu that lets the user practise, view summary or exit.
User: A student who needs a clear next step.
Output a study summary that includes topic, progress, score or recommendation.
Stretch: Add a targeted next-step message for weak areas.
Submit the final product and evidence through the LMS. Keep the working files unchanged until marking is complete.
Item 1
CSCGT_Task6_2026_Surname_FirstName_Product
The working product in the approved programming environment, plus any files needed to run it.
Item 2
CSCGT_Task6_2026_Surname_FirstName_Evidence.docx
Screenshots and explanations showing design, algorithm, code, testing, validation, iteration and evaluation evidence.
Item 3
CSCGT_Task6_2026_Surname_FirstName_Planning.docx
Completed project planning, product scope, wireframe/prototype and algorithm design evidence.
Item 4
CSCGT_Task6_2026_Surname_FirstName_TestingEvaluation.docx
Testing log, user validation notes, iteration log and final evaluation.
Assessment Documents
Use these essential documents and templates for the programming project.
Document
Assessment overview, purpose, conditions and policy notes.
Document
Concise student instructions: product, evidence, marks and conditions.
Document
Required Study Session Helper Program scenario and requirements.
Document
Template for planning the solution before coding.
Document
Pseudocode and algorithm planning template.
Document
Template for test data, expected results, actual results and fixes.
Document
Template for evaluating the completed solution.
Document
Student-facing instructions for the final LMS upload.
Document
Final checklist before submitting the project.
Download the key Word and PDF files for planning, building and submitting the project.