Task 6: Study Session Helper Program Project
Assessment Details
| Item | Details |
|---|---|
| Course | Year 12 Computer Science General |
| Unit | Unit 4 - Developing computer-based solutions and communications |
| Assessment type | Project |
| Weighting | 20% |
| Raw mark total | 50 marks |
| Timing | Term 3 Weeks 4-8 |
| Final submission window | Monday 7 September to Friday 11 September 2026 |
Purpose
Task 6 is the major Unit 4 practical project. Students design and build a small coded Study Session Helper Program using the supplied stimulus. Students make design decisions about interface, question content, recommendation rules and programming environment, but the assessed product type is fixed so the task remains clear and comparable.
The final product does not need to be a large app. It must be a purposeful, working programming solution with clear planning, algorithm design, testing, validation and evaluation.
Project Model
Students follow five project stages to produce the supplied Study Session Helper Program:
| Stage | Main question | SDC link | Required evidence |
|---|---|---|---|
| Define | Who is the product for, and what problem does it solve? | State the problem | target user, study-session problem, at least four functional requirements, constraints, success criteria |
| Prototype | What should the user experience look like before coding? | Plan and design | SDC plan, user flow, wireframe/prototype/interface plan, input-process-output plan, data/variable plan, user-need links |
| Algorithm design | How will the logic work before coding? | Plan and design | pseudocode and/or flow chart, sequence, selection, iteration, validation/error handling and trace table |
| Build | How will the solution work in code? | Develop the solution | running Study Session Helper Program, input, processing, output, variables, data choices, sequence, selection, iteration and validation |
| Test and Validate | Does it work, and does it suit the user need? | Test the solution | normal, boundary and invalid tests; expected and actual results; debugging evidence; validation evidence |
| Iterate and Evaluate | What changed, what is strong, and what should improve? | Evaluate the solution | documented improvement, final judgement against success criteria or requirements, strengths, limitations and future improvements |
Syllabus Content Assessed
- Stages of the SDC: state the problem, plan and design, develop the solution, test the solution and evaluate the solution.
- Factors affecting software development, including user needs and user interface.
- Data types, variable naming, source code and executable code.
- Control structures: sequence, selection and iteration.
- Program error types: syntax, run-time and logical errors.
- Test data, trace tables, debugging and documentation.
- Pseudocode and flow charts to model algorithm logic.
Supplied Stimulus
Students create a Study Session Helper Program for a Year 12 student preparing for assessment. The program must collect study session information, include at least three practice questions or prompts, track progress, use selection and iteration, validate at least one important input and display a useful final study summary or next-step recommendation.
The required product gives students enough programming opportunity to demonstrate input, processing, output, variables, data types, sequence, selection, iteration, validation, testing and evaluation.
Student Website Package
Keep the website package focused on the documents students need to complete and submit the project:
- Student task sheet
- Project brief
- Planning and design template
- Algorithm design template
- Testing log template
- Evaluation and reflection template
- Final submission LMS instructions
- Submission checklist
Additional teacher, marking, authentication and moderation files remain in the repo but are not part of the student website document set.
Conditions
- Work is completed across supervised class time and approved homework time.
- Authentication checkpoints are compulsory.
- The teacher may ask students to explain or demonstrate any part of their project.
- Students may use class notes, teacher examples, approved tutorials and approved design tools.
- Any external code snippets, tutorials, assets, examples, AI support or peer support must be acknowledged.
- The final submitted work must be the student's own adapted product and code.
School Policy Notes
- Missed assessments, extensions, late submission and academic integrity follow the school assessment and reporting policy.
- Copying, unauthorised collaboration, plagiarism or unauthorised AI-generated work may be treated as academic misconduct.
- For moderation, keep the final evidence document, source code, prototype evidence, teacher checkpoint records, marking sheet and any submitted media/screenshots.