The IDE Toolkit

Four tools, one window

An IDE looks like one program, and that is the thing to get past first. It is a bundle. Every tool inside it existed separately before anyone packaged them together, and they still do: you can write code in a plain text editor, run a translator from a command line, and read the error messages there. What an IDE changes is that all of it happens in one place, without you switching between things. ⚠️ Which is why the exam almost never asks what an IDE is. It asks what each PART does. And there is one answer that will not be accepted for any of them: "it helps you write code" is perfectly true of all four tools at once, which means it has identified none of them. So this module is really about precision. Four tools, four purposes, each one worded so it could only be about that tool.

The four tools this paper names

Read each purpose and notice it could not be swapped onto any of the others. That is the standard your own answers have to reach.

Vague, precise, and the test between

Your specification is unusually direct about this, so it is worth seeing the two kinds of answer side by side before you write one.

How to name a purpose

Two clauses, every time. What this tool does that the others do not, and when you would notice it. That second clause is what stops an answer drifting back into generality, because noticing something means picturing a moment. ⚠️ Three phrases to strike out before you write them down: "helps you", "makes it easier", "is used for coding". Each one is true of every tool on this topic, so each one costs you the mark it was meant to earn. If one of them is the only thing you can think of, you have not decided what the tool is for yet. ⚠️ And apply the swap test to your own sentence. Take what you have written, put a different tool from the same bundle in place of the one you meant, and read it again. If it still sounds right, it was never about your tool. Rewrite until the swapped version is obviously false.

Match each tool to what only it does

The answer that names nothing

Asked what error diagnostics does in an IDE, a student writes: "it helps you write your code properly". Why does that score badly?

• It would be just as true of the editor or the translator, so it has not identified this tool at all
• It is too short, and the examiner is looking for at least two sentences
• Error diagnostics is not really part of an IDE
• It should have said the tool helps you run your code instead

What the underline cannot see

Error diagnostics reads what you have written and checks that the language can make sense of it. So a missing bracket, a misspelled command or a line the parser cannot follow gets flagged, often before you have run anything at all, usually with a line number attached. That is genuinely useful and it is why the tool exists. ⚠️ Now the part worth remembering, because it is where people over-trust the green tick. Diagnostics cannot tell you that your total comes out one too high. It has no idea what you were trying to do. A program that is beautifully written and completely wrong will pass every check without a murmur. ⚠️ You have already met this boundary from the other side. On the testing topic, the dividing line was whether the program RAN: faults that stop it running against faults that let it run and produce nonsense. That is the same line. Diagnostics catch the first kind. Only testing catches the second, because only testing involves somebody deciding in advance what the right answer was. So "the IDE found no errors" and "my program is correct" are two completely different claims, and only one of them has been checked.

True about the IDE tools

Select the TWO statements that are true.

• Error diagnostics can flag a mistake before the program has been run at all
• The run-time environment lets the program be run from inside the IDE, without setting anything up separately
• Error diagnostics will warn you when a calculation produces the wrong answer
• A program cannot be written without an IDE

Complete the IDE paragraph

The part of an IDE where code is typed, with numbered lines and colouring, is the _____. The part that reports mistakes and shows you where they are is _____. The part that lets a finished program run without leaving the window is the _____. The part that turns what you wrote into instructions the machine can carry out is the _____.

Name the tool

Five moments at the keyboard, three lives. Name the tool doing the work.

Order what happens when you press run

Put these five stages into the order they happen.

• You type the code, and the editor numbers and colours it as you go
• Error diagnostics flags anything the language cannot make sense of
• You fix those, and the translator converts what you wrote
• The run-time environment starts the program
• You compare the output against what you expected, because no tool here can do that for you

Spot the true IDE facts

Tap the TWO statements that are true.

• Error diagnostics can flag a mistake before the program is run
• An IDE bundles together tools that each existed separately beforehand
• Error diagnostics will find a calculation that produces the wrong total
• The editor is the part that turns code into instructions the machine can carry out

Three toolkit calls

Three things a classmate says. Choose the response you could defend in writing.

• A student says: "the IDE checked my program and found no errors, so it must be right." What is wrong with that?
• A question asks what the run-time environment contributes to an IDE. Which answer earns the mark?
• A classmate says the editor and the translator do much the same job, since both deal with your code. What actually separates them?

Name what each tool actually does

A friend has written "it helps you code" for all four parts of this question and cannot see why it scored one mark out of four. Write them the answer.

• Explain what an IDE is, and why the question is usually about its parts rather than the whole
• Name the four tools this specification lists and give each a purpose that could not be said of the others
• Explain what error diagnostics can find, and what it cannot find at all
• Explain what the run-time environment contributes that the editor does not
• Finish with the test for telling a named purpose apart from a vague answer