IGCSE · Practice questions · Integrated development environments (IDEs)

Name it, explain it.

Six original Cambridge-style questions on integrated development environments, with mark-scheme solutions.

Original questions All questions on this page are original work, written in the Cambridge IGCSE style. They are not from past papers. They test the same concepts and skills the syllabus rewards.
Keep these straight

Seven functions.

01
Explain
[2 marks]

Explain the role of an integrated development environment (IDE) when writing program code.

  • An IDE is software that provides the tools a programmer needs in one place, ✓
  • to write, translate, run/test and debug program code. ✓
02
Recall
[4 marks]

Identify four common functions of an IDE.

  • Code editor. ✓
  • Error diagnostics. ✓
  • Auto-completion. ✓
  • Prettyprint. (Also accept: run-time environment, translators, auto-correction; one mark each, up to four.) ✓
03
Explain
[2 marks]

Describe how error diagnostics help a programmer.

  • They detect errors and show where they are, e.g. highlighting the line number. ✓
  • They describe what the error is, so the programmer can find and fix it quickly. ✓
04
Explain
[2 marks]

Describe the difference between auto-completion and auto-correction.

  • Auto-completion suggests how to finish a keyword or identifier while it is being typed. ✓
  • Auto-correction automatically fixes a mistake, such as a misspelt keyword, after it has been typed. ✓
05
Apply
[3 marks]

A student's code has inconsistent indentation and is hard to read. Name the IDE function that would help, describe what it does, and explain why this helps.

  • Prettyprint. ✓
  • It displays the code with consistent indentation and colour-coded keywords. ✓
  • This makes the structure (e.g. which statements are inside a loop) easy to see, so errors are easier to spot. ✓
06
Analysis
[2 marks]

An IDE contains both an interpreter and a compiler. Explain how a programmer might use each while developing and then releasing a program.

  • While developing, use the interpreter to run and test the code line by line, stopping at errors to debug them. ✓
  • When the program is finished, use the compiler to produce an executable file to release. ✓

Mark this once you have attempted all six and checked your working. It records a Practiced badge on the topic and adds a one-time bonus. Revealing the solutions alone does not count.