TK Study

Software Engineering › Key terms › Y11 OOP › Subsystem testing

Subsystem testing

Term Check Y11 OOP

Definition

Testing a group of modules that work together as a subsystem, checking their interfaces and data passing.

Example: Between unit and system testing.

Check this one: Not found word-for-word in the supplied syllabus, specifications, marking guidelines or notes; the definition is standard computing knowledge, so check it against your class notes.

Where it is used in the test

Syllabus area: Y11 OOP.

Question types it can appear in

No past question in this bank is linked to this term yet. It can still be tested through the question types above.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Testing a group of modules that work together as a subsystem, checking their interfaces and data passing.” Then apply it: Between unit and system testing.

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

General advice

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

Common mistakes

Marker feedback on other questions of the same type (code and diagram feedback often applies across questions)
  • Check the sources: Not found word-for-word in the supplied syllabus, specifications, marking guidelines or notes; the definition is standard computing knowledge, so check it against your class notes.
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: Clear and uncluttered mainline · One logical task per subroutine · Stub · Ease of maintenance · Regular backup · Unit testing · System testing · Black box testing · White box testing · Grey box testing · Quality assurance