Knowledge of the tools that an IDE provides; How each of the tools and facilities listed can be used to help a programmer develop a program; Practical experience of using a range of these tools within at least one IDE
What you need to know
An Integrated Development Environment (IDE) is a software application that provides tools to help programmers write, test, and debug code more efficiently. Key features include a code editor with syntax highlighting and auto-completion, error diagnostics that highlight mistakes, a run-time environment to execute programs, and built-in translators to convert code to machine code.
Key points
Text/code editor: allows program code to be written, entered, and changed. Supports features like line numbering and auto-indent.
Pretty printing / syntax highlighting: uses colour to distinguish keywords, strings, variables, and comments — helps identify them.
Auto-complete / keyword completion: suggests code/syntax when the first part is entered, speeding up coding.
Error reporting / diagnostics: identifies the location and detail of errors and may suggest fixes.
Run-time environment / output window: allows program/code to be run/executed and shows the output.
Translator (compiler/interpreter): converts high-level code to machine code so it can be executed.
Debugger: helps find errors in the program.
Stepping: executes the program LINE BY LINE, so you can see exactly what happens at each step.
Variable watch: lets you see the contents/data held in variables as the program runs.
Breakpoints: allow the program to STOP at a chosen/set position so you can inspect values.
Exam Tip:When naming IDE features, the description must ADD MORE than the name itself. 'Debugging tools — to allow debugging' scores only 1 mark (for the feature). Say what the tool DOES.
Exam Tip:You need TWO features with descriptions. Good pairs: (1) breakpoints — stop at a set position, (2) variable watch — see variable values during execution.
Exam Tip:Auto-correct and auto-indent are BOTH editor features — they only count as ONE tool. Don't list two sub-features of the same tool as separate answers.
Exam Tip:When asked to 'identify' features (not describe), just naming them is enough: e.g. error diagnostics, run-time environment, editor, translator, breakpoints, stepping.