TK Study

Software Engineering › Key terms › Y11 OOP › Consistency (collaboration)

Consistency (collaboration)

Term Y11 OOP

Definition

Using the same naming, layout and coding standards across the team so everyone can read and change the code.

Example: Use snake_case for every variable.

Found in: syllabus, sample exam and familiarisation guidelines, school notes.

Where it is used in the test

Syllabus area: Y11 OOP.

Question types it can appear in

Where it has appeared in the paper

The Software Engineering Project (Part B). 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

“Using the same naming, layout and coding standards across the team so everyone can read and change the code.” Then apply it: Use snake_case for every variable.

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

Worked answers from the marking guidelines

Sample exam Q4 (1 mark): Collaboration (1 mark): criteria and sample answer

Criteria

1: Correctly identifies the benefits.

Sample answer

Different points of view can be considered. Tasks can be delegated to those with expertise.

Open the question page

Common mistakes

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: Task definition · Facade pattern · Agility · Code commenting · Version control · Feedback