AQA A-Level Computer Science Paper 2, June 2025: Question 1

✅ Correct Labels

💡 Key Knowledge

• Software Tree Split: Top tier divides into Application Software (carries out user-oriented tasks) and System Software (manages and operates computer hardware).
• System Software: Composed of Operating Systems, Utility Programs (system maintenance tasks like compression, anti-virus), Library Programs (pre-compiled routines), and Translators.
• The 3 Translators: Assembler (assembly to machine code), Compiler (source code to machine code in one go), and Interpreter (translates and executes line by line).

❌ Common Errors & Lost Marks

• Informal terms: Writing apps for position 1 is strictly marked as Not Enough (NE). Use the formal academic term: Application software.
• Mixing up levels: Confusing Translators with Utilities (e.g. putting "Compilers" under utility programs).

🧠 Exam Technique

Trace the tree branches: Look at the children nodes to deduce the parent!
• Children are Word Processor and Photo Editor → Parent must be Application Software.
• Siblings under Translators are Assembler and Compiler → The missing 3rd translator is Interpreter.

✅ Any Two Distinct Descriptions (1 mark each)

• Processor scheduling: Allocates processor time/cores to competing processes using time-slices to decide which process executes and when.
• Memory management: Allocates RAM/primary memory to active processes and manages moving inactive data/pages between RAM and virtual memory/paging file.
• Hardware abstraction / Virtual Machine: Hides the physical complexities of hardware components from applications and users.
• Interrupt handling: Detects hardware/software interrupts and invokes the appropriate Interrupt Service Routine (ISR).
• File / Secondary Storage management: Allocates space on storage devices for files, maintains directory structures, and manages the file allocation table (FAT/file system).
• User authentication & security: Manages access rights and permissions, authenticates user credentials (passwords/biometrics), and isolates processes into sandboxes so they cannot access unauthorised memory.

❌ Examiner Pitfalls — Where Students Failed

• Giving vague 2-word labels: The question asks to describe. Simply writing "Memory management" , "Processor management" , or "File management" earned 0 marks. You must state what the OS actually does (e.g. allocating RAM to processes).
• Repeating the prompt: Repeating "Allocates I/O devices" or "Manages I/O devices" is rejected as it is already given in the question stem.
• Vague interface statements: Stating merely "Provides a user interface" or "Hides complexities of computer" is Not Enough.

🧠 Exam Technique: The "Action + Resource" Formula

Always use the structure: [Verb / Action] + [Hardware / System Resource] + [Purpose].

Example: "Allocates (action) time slices of the CPU (resource) to competing processes (purpose)." This guarantees full marks.

✅ Any 4 Valid Points (1 mark each, Max 4)

• Readability & Maintenance: Code is much easier to understand, maintain, read, and debug because it uses English-like keywords and mathematical syntax.
• Portability (Machine Independence): Source code is portable across different processor architectures (different instruction sets) since compiler/interpreter handles machine translation.
• Higher Productivity: Faster development time; one statement in an HLL often equates to many lines of low-level assembly/machine code.
• Control & Data Structures: Availability of structured flow control (such as while loops, if-else branching) and complex built-in data structures (such as arrays, records, lists, dictionaries).
• Modularity & Abstraction: Built-in support for modular code via functions, procedures, subroutines, and object-oriented classes.
• Rich Standard Libraries: Access to extensive built-in libraries and pre-tested functions, reducing the need to reinvent low-level algorithms.
• Problem-Oriented & Multi-Paradigm: Allows programmer to focus on solving the logic of the problem rather than managing hardware registers and memory addresses.

❌ Common Misconceptions

• "HLL runs faster": INCORRECT! Low-level languages typically execute faster and require less memory overhead because they map 1:1 to machine architecture. HLL code is faster to write, not faster to run.
• "No translation needed": INCORRECT! HLL requires a compiler or interpreter to run, whereas machine code runs directly.
• Vague answers: Just writing "It is easier" without qualifying what is easier (e.g. easier to read, write, debug, maintain) loses marks.

🧠 Exam Technique: Structure Your 4 Marks

For a 4-mark descriptive question, write 4 distinct, well-developed sentences covering different aspects:

1. Human perspective: Easier to read/debug due to English-like syntax.
2. Hardware perspective: Portable/machine-independent (runs on different CPUs without rewriting).
3. Productivity: One line of HLL replaces multiple assembly instructions, speeding up development.
4. Language features: Offers high-level control structures (loops/selection) and built-in complex data structures.