Software Engineering › Key terms › Y11 Programming Fundamentals › Boundary values
Boundary values
Term Y11 Programming Fundamentals
Definition
Test data at and either side of a limit of the valid range. For a valid range of 1 to 10: 0, 1, 10, 11.
Example: Valid range 18 to 65 means test 17, 18, 65, 66.
Found in: syllabus.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Short answer: Select test data
- Matching or table: Complete a test data table (familiarisation Q5)
- Multiple choice: Pick the option that matches the definition or example.
Where it has appeared in the paper
The Software Engineering Project (Part B, C). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q5 (3 marks): Testing (test data) The Software Engineering Project (Part C) · 3 marks
- Sample exam Q11 (3 marks): Testing (test data) The Software Engineering Project (Part B) · 3 marks
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Boundary values in Programming Fundamentals (Year 11) · study that set
- Memorise: Testing and code quality (Year 11)
- Notes: Quality assurance, testing methods and test data (The Software Engineering Project (Year 12))
- Notes: Testing and code quality (Year 11) (Year 11 content (Programming fundamentals, OOP, Mechatronics))
- Master answer: sample-q11 (3 marks, table (test data)) (Master model answers: code, SQL, pseudocode, diagrams and tables)
How to use it in an answer
A model sentence
“Test data at and either side of a limit of the valid range.” Then apply it: Valid range 18 to 65 means test 17, 18, 65, 66.
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.
Command words used with it
No linked question shows the command word for this term. Across the past short answer questions in this bank the words used most are: Explain, Outline, Describe, Compare, Classify, Analyse. Check the actual word in your question.
Technique for the question types
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Matching or table: Tick or match each statement to the right column (for example ORM v SQL, SAST v DAST).
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
What the marking guidelines and feedback say
Good extras: 1023 (just below desktop boundary) and 767 (just below tablet boundary). Test boundary values, both sides of each boundary, and one value for each path.
Worked answers from the marking guidelines
Familiarisation Q5 (3 marks): Testing (test data) (3 marks): criteria and sample answer
Criteria
3: Test data that thoroughly tests the algorithm, with expected outputs and reasons for inclusion. 2: Tests most boundaries and/or paths, with most expected outputs and reasons. 1: Some relevant information.
Sample answer
85 -> H (testing greater than 80). 80 -> H (boundary value 80). 60 -> P (between 50 and 80). 50 -> P (boundary value 50). 45 -> N (testing 'otherwise', below 50).
Sample exam Q11 (3 marks): Testing (test data) (3 marks): criteria and sample answer
Criteria
3: Test data that thoroughly tests the algorithm, with expected outputs and reasons. 2: Tests most of the boundaries and paths, with relevant outputs and reasons. 1: Some relevant information.
Sample answer
1024 -> Desktop (boundary check). 768 -> Tablet (boundary check). 100 -> Phone (below lowest screen size check). 850 -> Tablet (between Tablet and Desktop). 2000 -> Desktop (above highest screen size check).
Common mistakes
- 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.
Related terms
Same group in the syllabus: Quality criteria for evaluating code · Syntax error · Logic error · Runtime error · Debugging tools · Breakpoint · Single line stepping · Watch window (variable watch) · Debugging output statements · Path coverage · Faulty and abnormal data · Code optimisation