How programming languages, source code, translators and integrated development environments fit together: why source code must be translated to machine code, and how the choice of language and tools supports writing software.

Source code (up to 2): the code a programmer writes in a programming language (high-level such as Python, or low-level such as assembly); it is designed to be read and written by humans.

Machine code (up to 2): the binary instructions (1s and 0s) that the CPU executes directly; it is what the hardware actually understands.

Why a translator is needed (within the marks): the CPU can only run machine code, but humans write in source code, so a translator (compiler, interpreter or assembler) is needed to convert the source code into machine code that the processor can execute.

Markers reward source code as human-written and machine code as the binary the CPU runs, and the clear point that translation bridges the two.

A 6-mark question, so a developed discussion across the three areas.

Language level: a high-level language is the likely choice for productivity and portability (easier to write and debug, runs on different machines), though performance-critical parts might use lower-level code for efficiency. State the trade-off.

Translator: during development an interpreter is convenient (runs immediately, reports errors as it goes); for release a compiler produces a fast executable that can be distributed without the source code. So the choice depends on the stage.

IDE: an IDE supports the whole process with an editor (syntax highlighting, auto-complete), debugging tools (breakpoints, stepping, watches) to find logic errors, a run-time environment to test, and a built-in translator, all in one place, speeding development and catching errors early.

Markers reward developed points across language level, translator choice and IDE tools, with reasons and a sense of the trade-offs, rather than three short lists.