Term 3 Week 4 - Week 1

Define the Product and User Need

Define a realistic Study Session Helper scope, then define the user, problem, requirements and success criteria.

Learning Goals

  • Understand the Task 6 evidence package and marking rubric.
  • Define a Study Session Helper version that can be built and assessed.
  • Write a clear problem statement and target user profile.
  • Create functional requirements and success criteria.
  • Map planned input, processing and output.

Five-Lesson Sequence

1

Unpack the Task 6 project brief and look at examples of realistic Study Session Helper scope.

2

Explore the supplied Study Session Helper scenario and decide how your program will meet the required features.

3

Write functional requirements, constraints and success criteria.

4

Create an input-process-output table and identify the data the product needs.

5

Complete the product approval checkpoint.

Current Stage: Define

State the problem

Understand the user problem before building.

Checkpoint: A teacher can tell what problem the product solves and how success will be judged.

Problem statement
Target user
Requirements
Constraints
Success criteria

Detailed Lesson Build Pathway

Lesson 1

Task Launch and Study Session Helper Scope

Understand what will be marked and what a suitable product looks like.

  1. Open the Task 6 student package and read the assessment details.
  2. Highlight the required evidence: product, planning, prototype, algorithm, testing, validation and evaluation.
  3. Compare two possible Study Session Helper feature sets and decide which one has clearer user value.
  4. Write a one-sentence Study Session Helper pitch.

Evidence: One-sentence Study Session Helper pitch and initial scope notes.

Lesson 2

User and Problem Definition

Define a specific user group and problem before deciding features.

  1. Name the target user and describe what they are trying to do.
  2. List the current pain points or inefficiencies.
  3. Write the problem statement using user, problem and impact.
  4. Check that the problem can be addressed by the Study Session Helper Program.

Evidence: Problem statement and user profile.

Lesson 3

Requirements and Constraints

Turn the Study Session Helper scope into assessable requirements.

  1. Write at least five functional requirements.
  2. Write two non-functional or usability expectations.
  3. List practical constraints such as time, device, data and skill level.
  4. Rewrite vague requirements so they can be tested later.

Evidence: Requirements table with success criteria.

Lesson 4

Input, Processing and Output

Describe what the program receives, calculates or decides, and returns to the user.

  1. List each input and its data type.
  2. Describe the processing or decision made from each input.
  3. Describe the output or feedback shown to the user.
  4. Identify one input that needs validation.

Evidence: Completed input-process-output table.

Lesson 5

Product Approval Checkpoint

Confirm that the product scope is realistic and ready for design.

  1. Prepare your pitch, user problem, requirements and IPO table.
  2. Show your teacher the planned product scope.
  3. Record approval notes and required changes.
  4. Revise the scope before moving into prototype work.

Evidence: Teacher approval notes and revised scope.

Key Build Steps

Define the problem

  1. Name the target user
  2. Describe the problem
  3. Explain why the product is useful

Set the scope

  1. Write functional requirements
  2. Write constraints
  3. Confirm what will not be built

Student Checklist

  • I know what my Study Session Helper will do
  • My product has a specific user
  • My requirements can be tested
  • My teacher has approved my scope

Common Mistakes to Avoid

The Study Session Helper scope is too broad

Reduce it to one clear user problem and one main workflow.

Requirements are vague

Rewrite them so they can be checked with evidence later.

The idea is mostly design with little programming

Add meaningful input, processing, decisions and outputs.

Useful Guides This Week

Define a Product Worth Building

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

Weekly Checkpoint

Teacher approval for Study Session Helper scope, problem statement, requirements and input-process-output table.