Term 3 Week 6 - Week 3

Build the Minimum Viable Product

Create the smallest working version first, then add required programming concepts and evidence.

Learning Goals

  • Build a working main user workflow.
  • Use variables, data types, sequence, selection and iteration.
  • Add validation or error handling.
  • Take development screenshots at meaningful stages.
  • Keep a build log of issues and fixes.

Five-Lesson Sequence

1

Create the first working input and output path.

2

Add selection and meaningful feedback.

3

Add iteration or repeated processing.

4

Add validation and improve readability.

5

Complete the working MVP checkpoint.

Current Stage: Build

Develop

Create the minimum viable product first, then add features carefully.

Checkpoint: The main product works for the most important user scenario.

Working MVP
Variables and data types
Selection
Iteration
Validation
Readable code

Detailed Lesson Build Pathway

Lesson 1

First Working Path

Make the product do one complete useful thing.

  1. Create the project file or workspace.
  2. Add the first inputs and outputs.
  3. Run the product with one simple successful example.
  4. Save a screenshot of the working path.

Evidence: Screenshot or export of first working version.

Lesson 2

Selection and Feedback

Add decisions that change what the product tells the user.

  1. Identify a decision from your pseudocode.
  2. Implement IF, ELSE IF or ELSE logic as appropriate.
  3. Show different outputs for different inputs.
  4. Test at least two branches.

Evidence: Code screenshot and branch test evidence.

Lesson 3

Iteration or Repeated Processing

Add a loop or repeated action that supports the product purpose.

  1. Choose what repeats: questions, records, turns, items, attempts or menu actions.
  2. Implement the loop.
  3. Check that the loop stops correctly.
  4. Record what data changes during each repeat.

Evidence: Loop code screenshot and test evidence.

Lesson 4

Validation and Code Quality

Make the product more reliable and easier to understand.

  1. Choose one input that needs validation.
  2. Add a check for invalid, empty or out-of-range input.
  3. Rename unclear variables.
  4. Add short comments only where the code needs explanation.

Evidence: Validation screenshot and improved code sample.

Lesson 5

Working MVP Checkpoint

Show that the main product is working before adding polish.

  1. Run the product from start to result.
  2. Show the teacher the current MVP.
  3. Record missing features and bugs.
  4. Choose the next two development priorities.

Evidence: Checkpoint notes and MVP screenshot.

Key Build Steps

Build core logic

  1. Input data
  2. Process data
  3. Display useful output

Add reliability

  1. Test branches
  2. Add validation
  3. Keep development evidence

Student Checklist

  • My product runs
  • My code has selection
  • My code has iteration
  • My product validates at least one input
  • I have development evidence

Common Mistakes to Avoid

The product has many screens but no working logic

Build the smallest working workflow first.

The loop never ends or does not change anything

Check the stopping condition and variable updates.

Validation is added only at the end

Add validation while building the feature it protects.

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.

Weekly Checkpoint

Working MVP with required programming concepts visible.