TK Study

Software Engineering › Key terms › Y11 Programming Fundamentals › Pseudocode

Pseudocode

Term Y11 Programming Fundamentals

Definition

Structured, language-independent English-like code: keywords in capitals (IF, ELSE, WHILE, ENDWHILE, FOR, NEXT, SET, GET, DISPLAY), paired structures and consistent indentation.

Example: Always write a mainline plus subroutines, use indentation and close every structure (ENDIF, ENDWHILE).

Found in: syllabus, course specifications, 2025 HSC marking guidelines, sample exam and familiarisation guidelines, school notes, past SDD papers.

Where it is used in the test

Syllabus area: Y11 Programming Fundamentals.

Question types it can appear in

Where it has appeared in the paper

The Software Engineering Project (Part A, B, C). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Other questions that mention it

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Structured, language-independent English-like code: keywords in capitals (IF, ELSE, WHILE, ENDWHILE, FOR, NEXT, SET, GET, DISPLAY), paired structures and consistent indentation.” Then apply it: Always write a mainline plus subroutines, use indentation and close every structure (ENDIF, ENDWHILE).

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Technique for the question types

What the marking guidelines and feedback say

2025 HSC Q17 (3 marks): Algorithm design

Marker feedback: use pseudocode control structures accurately; iterate an array and sum it; apply relational operators correctly; use the stimulus to choose the right structures.

Familiarisation Q8 (3 marks): Algorithm design (linear search)

The original (buggy) algorithm is not available. Note the 'Index - 1' because Index is incremented after the item is found.

Worked answers from the marking guidelines

Sample exam Q14 (3 marks): Algorithm design (subroutines) (3 marks): criteria and sample answer

Criteria

3: Substantially correct pseudocode that includes at least ONE subroutine. 2: Addresses some of the requirements. 1: Some understanding of the problem.

Sample answer

BEGIN main Get num_pizzas total_cost = 0 FOR i = 1 TO num_pizzas Get pizza_size Get num_toppings cost_per_pizza = calculate_pizza_cost(pizza_size, num_toppings) DISPLAY cost_per_pizza total_cost = total_cost + cost_per_pizza NEXT i DISPLAY total_cost END main

BEGIN calculate_pizza_cost(size, num_toppings) base_price = 10 topping_price = 1.5 IF size = "Medium" THEN base_price = base_price + 2 ELSEIF size = "Large" THEN base_price = base_price + 4 ENDIF pizza_cost = base_price + num_toppings * topping_price RETURN pizza_cost END calculate_pizza_cost

Open the question page

Familiarisation Q8 (3 marks): Algorithm design (linear search) (3 marks): criteria and sample answer

Criteria

3: Correctly modifies the algorithm to achieve its intended purpose. 2: Corrects some mistakes. 1: Some understanding of the problem.

Sample answer

BEGIN Search (SearchItem) Set LastIndex to the number of elements in ItemArray Found = FALSE Index = 1 WHILE Found = FALSE AND Index < LastIndex + 1 IF ItemArray(Index) = SearchItem THEN Found = TRUE ENDIF Index = Index + 1 ENDWHILE IF Found = TRUE THEN Display 'Position', Index - 1 ELSE Display 'Not found' ENDIF END Search

Open the question page

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • Pseudocode questions (2025 HSC exam Q17): use pseudocode control structures accurately; iterate an array and sum it; apply relational operators correctly; use the stimulus to choose the right structures.
General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Computational thinking · Algorithm · Sequence · Selection · Iteration (repetition) · Divide and conquer · Backtracking · Top-down design · Bottom-up design · Abstraction · Refinement · Flowchart · Subroutine (module, subprogram, procedure) · Function v procedure