Software Engineering › Key terms › Y11 Programming Fundamentals › Integration
Integration
Process Y11 Programming Fundamentals
Definition
Combining separately built modules or subsystems into one working system and checking they communicate correctly through their interfaces.
Example: Integration comes AFTER development and BEFORE system testing.
Found in: syllabus, sample exam and familiarisation guidelines, school notes.
Where it is used in the test
Syllabus area: Y11 Programming Fundamentals.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Drag into order: Know where it sits in the sequence.
- Short answer: Explain why integration testing is needed
Where it has appeared in the paper
Secure Software Architecture (Part C). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q1 (1 mark): Development steps Secure Software Architecture (Part C) · 1 mark
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: Integration in Programming Fundamentals (Year 11) · study that set
- Memorise: Software development steps and algorithm design
How to use it in an answer
A model sentence
“Combining separately built modules or subsystems into one working system and checking they communicate correctly through their interfaces.” Then apply it: Integration comes AFTER development and BEFORE 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
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
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Drag into order: Put the steps in the correct order; know the SDLC order and the web request order.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
Know the order of the software development cycle: define and understand the problem (requirements) -> plan and design -> develop/construct -> test and evaluate -> deploy/implement -> maintain.
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: Software development steps (the order) · Requirements definition · Determining specifications · Design · Development · Testing and debugging · Installation · Maintenance · Online code collaboration tools