Learn
4.2.5 | INTEGRATED DEVELOPMENT ENVIRONMENT
01 | WHAT IS AN IDE?
An integrated development environment (IDE) is software that brings together tools for developing programs in one workspace.
A programmer can edit source code, access a suitable translator, run the program and inspect feedback without continually switching between separate tools.
Integrated means brought together. The IDE is not a programming language, and it is not simply another name for a compiler. It provides a coordinated environment for using several tools.
Features vary by IDE and configuration. Focus on what each feature does rather than memorising where one product places its buttons.
02 | A LABELLED WORKSPACE
SOURCE CODE
1 price = 12
2 quantity = 3
3 total = price - quantity
4 print(total)Editor tools help enter and format instructions.
VARIABLE INSPECTION
price = 12
quantity = 3
total = 9
A debugger can show values at a paused point.
OUTPUT / DIAGNOSTICS
Output: 9
Expected cost: 36. The code runs, but the calculation is wrong.
This is an illustrative workspace, not a screenshot or a functioning editor. The run controls are labels. The wrong result helps show why an IDE does not guarantee correct logic.
03 | CODE EDITOR
A code editor lets the programmer enter, change and save source code. It may include line numbers, search and replace, indentation support and syntax highlighting.
Syntax highlighting uses visual differences for parts of the source, such as keywords, strings and comments. This can make structure easier to see.
Benefit: editing and navigating a long program becomes easier. However, coloured code does not prove that its syntax or logic is correct.
04 | RUN-TIME ENVIRONMENT
The IDE provides or connects to a run-time environment in which the program can execute. This can include the required runtime support and facilities for entering input and viewing output.
Example: after selecting Run, a Python program can ask for a value in a console and display its calculated result.
The runtime must be appropriate for the language and project. The IDE itself does not make every program compatible with every computer.
05 | TRANSLATORS
An IDE can provide access to a compiler, interpreter or assembler, as appropriate to the language and project.
The translator may be bundled with the IDE or installed separately and configured for it. Selecting Run or Build can invoke the necessary tools.
Do not confuse the interface with the translation: the IDE coordinates the workflow; the translator performs its specific translation or execution role.
06 | ERROR DIAGNOSTICS
Error diagnostics provide information about detected problems. The IDE can highlight a source location and display a message from an editor, translator or running program.
| Diagnostic | How it helps | Limit |
|---|---|---|
| Missing closing bracket | Points the programmer towards a syntax problem | Reported position can be near, rather than exactly at, the cause |
| Runtime division-by-zero message | Shows an invalid operation encountered during execution | Other inputs may reveal different faults |
| Warning about suspicious code | Draws attention to a potential problem | A warning is not always proof of an actual fault |
A valid but incorrect calculation may produce no diagnostic. In the workspace example, subtraction is legal, but multiplication was intended. Testing reveals the wrong result.
07 | AUTO-COMPLETION
Auto-completion suggests or completes a name or code construct while the programmer types. It may offer variable names, keywords or functions that are available in the current context.
Example: typing the first letters of quantity may show the full existing variable name as a suggestion.
This can reduce typing and mistakes caused by inconsistent spelling. The programmer must still choose the intended suggestion: completing a valid but wrong variable can change the result.
08 | AUTO-CORRECTION
Auto-correction corrects, or offers a correction for, a detected entry problem. An IDE may fix a recognised spelling issue or offer an appropriate quick fix.
Difference: completion helps finish what is being entered; correction changes something detected as wrong.
Features depend on the IDE and language. Auto-correction does not understand every intention and cannot be relied on to repair an algorithm. Check the change before accepting it.
09 | PRETTYPRINT
Prettyprint formats code into a clearer, consistent layout, for example by applying appropriate indentation and spacing.
| Before formatting: teaching notation | After formatting |
|---|---|
| IF score >= 5 THEN PRINT "Pass" ENDIF | IF score >= 5 THEN<br> PRINT "Pass"<br>ENDIF |
Formatting can help a programmer see blocks and understand the program. It does not automatically change a wrong calculation into the right one.
In languages such as Python, indentation has meaning. A formatter must follow the language’s rules; arbitrary indentation changes can alter or invalidate code.
10 | EXTRA DEBUGGING TOOLS
Many IDEs also offer a debugger. These tools extend the core syllabus features and help investigate program behaviour.
| Tool | Purpose |
|---|---|
| Breakpoint | Pause execution at a selected point |
| Single-step execution | Advance through execution in small steps |
| Variable inspection / watch | View relevant values while paused |
For the cost example, pause after the calculation. The values price = 12, quantity = 3 and total = 9 show that the wrong operation was used. Changing subtraction to multiplication gives 36 for this test.
One correct result is not complete testing. Check additional suitable inputs and any important boundaries.
11 | FOLLOW A DEVELOPMENT WORKFLOW
- Write the source.
Use the code editor and appropriate completion suggestions.
- Improve readability.
Use prettyprint to organise the layout.
- Translate and run.
Use the appropriate translator and run-time environment.
- Inspect feedback.
Read diagnostics and compare actual output with expected output.
- Investigate and correct.
Use debugging tools where available; edit or accept a checked correction.
- Test again.
Repeat the failed test and try other relevant cases.
The workflow is iterative: programmers return to earlier steps as they discover problems or change requirements.
12 | THE SEVEN SYLLABUS FEATURES
| Feature | Main purpose |
|---|---|
| Code editor | Enter, edit and save source |
| Run-time environment | Provide suitable execution facilities |
| Translators | Translate or interpret code as required |
| Error diagnostics | Report detected problems |
| Auto-completion | Suggest or finish code entries |
| Auto-correction | Correct or offer fixes for recognised problems |
| Prettyprint | Format code for clearer reading |
Developed explanation: auto-completion suggests an existing variable name, reducing the typing required and the risk of inconsistent spelling. It still needs the programmer to select the intended name.
13 | COMMON MISTAKES
- The IDE is a language: it is development software used with languages.
- The IDE and compiler are identical: a compiler is one tool the IDE may use.
- No diagnostic means correct logic: valid code can give the wrong result.
- Completion and correction are the same: finishing an entry differs from fixing a detected problem.
- Prettyprint repairs the algorithm: it improves layout, not the intended calculation.
- Every IDE has every tool built in: features and configuration vary.
- One successful run is enough: test relevant additional cases.