Skip to topic
    ← Back to course topics

    The characteristics of contemporary processors, input, output and storage devices — OCR A-Level Computer Science

    Test yourself on The characteristics of contemporary processors, input, output and storage devices with OCR A-Level practice questions.

    Start free

    7 days Premium · Then free forever · No card, no charge

    The characteristics of contemporary processors, input, output and storage devices explained

    This subtopic explores the fundamental architecture of a processor, including the Arithmetic Logic Unit (ALU), Control Unit (CU), registers, and internal buses that facilitate data and control flow.

    Read the full explanation

    It examines the sequential fetch-execute cycle, detailing how instructions are retrieved from memory, decoded, and executed, and compares the unified memory model of von Neumann architecture with the separate instruction and data memory of Harvard architecture, crucial for understanding performance trade-offs in modern computing systems.

    Your focus

    1. Describe the components of a processor (ALU, CU, registers, buses)
    2. Explain the fetch-execute cycle
    3. Compare von Neumann and Harvard architectures

    The characteristics of contemporary processors, input, output and storage devices exam tips

    Topic Overview

    This topic explores the fundamental components of modern computer systems, focusing on the characteristics of contemporary processors, input devices, output devices, and storage devices. It covers how processors execute instructions (including pipelining, Von Neumann vs. Harvard architecture, and RISC vs. CISC), the role of input devices in data capture, output devices in presenting information, and storage devices in retaining data. Understanding these components is crucial for grasping how hardware and software interact to perform tasks efficiently.

    In the Cambridge OCR A-Level Computer Science syllabus, this topic forms the foundation for more advanced concepts like operating systems, computer networks, and system performance. Students must appreciate the trade-offs between speed, cost, capacity, and power consumption when selecting components. For example, choosing between an SSD and an HDD involves understanding access times, durability, and cost per gigabyte. Similarly, the choice of processor architecture affects instruction throughput and energy efficiency.

    Mastery of this topic enables students to critically evaluate computer systems, design efficient solutions, and prepare for questions on system performance, parallel processing, and emerging technologies. It also links to practical programming, as understanding the fetch-execute cycle and pipelining helps in writing optimised code. This knowledge is essential for both exams and real-world applications in computing.

    Key Concepts
    • →Von Neumann architecture: shared memory for data and instructions, single bus, sequential execution. Harvard architecture: separate memory for data and instructions, allowing simultaneous access and faster execution.
    • →Pipelining: overlapping fetch, decode, execute stages to increase throughput. Hazards (data, control, structural) can reduce efficiency.
    • →RISC vs. CISC: RISC uses simple, fixed-length instructions (one per cycle) and many registers; CISC uses complex, variable-length instructions with fewer registers. Modern processors often combine features.
    • →Input devices: sensors, keyboards, mice, microphones, barcode readers. Output devices: monitors, speakers, printers, actuators. Storage devices: magnetic (HDD), optical (DVD), solid-state (SSD), and cloud storage.
    Marking Points
    • Award credit for accurately labelling a diagram of the processor showing data paths between CU, ALU, registers, and system bus, with clear distinction between data, address, and control buses.
    • Award credit for correctly sequencing the stages of the fetch-execute cycle, including the role and transfers between Program Counter (PC), Memory Address Register (MAR), Memory Data Register (MDR), and Current Instruction Register (CIR).
    • Award credit for contrasting von Neumann and Harvard architectures with explicit reference to the von Neumann bottleneck, parallelism potential, and suitability for general-purpose vs. embedded systems.
    • Award credit for explaining how the control unit coordinates the fetch-execute cycle by generating control signals for memory read/write, ALU operations, and register transfers.
    Examiner Tips
    • 💡When describing the fetch-execute cycle, use a stepwise approach and clearly indicate register transfers (e.g., PC → MAR) to demonstrate understanding of data movement and control flow.
    • 💡For comparison questions on architectures, construct a table with criteria like memory space, bus complexity, common applications, and security implications to ensure all marking points are systematically addressed.
    • 💡Explain the von Neumann bottleneck not just as a limitation but also discuss how modern techniques like caching and pipelining help mitigate it, showing deeper insight.
    • 💡In diagram-based questions, label the system bus clearly and distinguish between internal processor buses and the external system bus to avoid oversimplification.
    • 💡When comparing architectures, explicitly state the differences in memory organisation and bus structure. Use diagrams to illustrate the fetch-execute cycle and pipelining stages.
    • 💡For storage devices, always mention specific metrics: access time (e.g., HDD ~5-10ms, SSD ~0.1ms), transfer rate, capacity, and cost per GB. Relate these to real-world scenarios like gaming or server use.
    • 💡In questions about performance, consider the impact of clock speed, number of cores, cache size, and pipelining. Explain trade-offs, e.g., higher clock speed increases heat and power consumption.
    Common Mistakes
    • Confusing the roles of the MAR and MDR: students often think the MAR holds the data rather than the address, or that the MDR holds the address after memory access.
    • Omitting the increment of the Program Counter during the fetch stage, leading to an incomplete cycle description and marks lost for accuracy.
    • Stating that Harvard architecture uses two separate buses without explaining the significance for simultaneous instruction fetch and data access, missing the performance implication.
    • Misidentifying the ALU as the component that fetches instructions, rather than performing arithmetic and logic operations under the control unit's direction.
    • Misconception: Pipelining always speeds up execution. Correction: Pipelining increases throughput but can cause hazards that require stalls or flushing, reducing speedup. Ideal speedup equals number of stages, but real-world speedup is less.
    • Misconception: RISC is always faster than CISC. Correction: RISC can be faster for simple tasks, but CISC can execute complex instructions in fewer lines of code. Modern processors (e.g., x86) use micro-operations to combine benefits.
    • Misconception: SSDs are always better than HDDs. Correction: SSDs are faster and more durable, but HDDs offer higher capacity at lower cost. The choice depends on the use case (e.g., archival storage vs. operating system).
    Frequently Asked Questions
    What is the difference between Von Neumann and Harvard architecture?
    Von Neumann architecture uses a single shared memory for both data and instructions, connected by a single bus. This can create a bottleneck (Von Neumann bottleneck) as the CPU cannot fetch data and instructions simultaneously. Harvard architecture has separate memory and buses for data and instructions, allowing simultaneous access and faster execution. Modern CPUs often use a modified Harvard architecture with separate caches.
    How does pipelining improve CPU performance?
    Pipelining divides the execution of instructions into stages (e.g., fetch, decode, execute, memory access, write-back). While one instruction is in the execute stage, the next can be fetched, overlapping operations. This increases throughput (instructions per cycle) but does not reduce latency for a single instruction. Hazards like data dependencies can cause stalls, reducing efficiency.
    What are the advantages and disadvantages of RISC vs CISC?
    RISC (Reduced Instruction Set Computer) uses simple, fixed-length instructions that execute in one clock cycle, with many registers. Advantages: simpler design, lower power consumption, easier pipelining. Disadvantages: more instructions needed for complex tasks. CISC (Complex Instruction Set Computer) has complex, variable-length instructions that can perform multiple operations. Advantages: fewer instructions per program, more memory efficient. Disadvantages: complex control unit, harder to pipeline. Modern processors often combine features (e.g., x86 decodes into micro-ops).
    Why are SSDs faster than HDDs?
    SSDs use flash memory with no moving parts, providing near-instantaneous access times (microseconds) and high data transfer rates. HDDs use spinning magnetic platters and a moving read/write head, resulting in higher latency (milliseconds) due to seek time and rotational delay. SSDs are also more durable and consume less power, but are more expensive per gigabyte.
    What is the role of cache memory in a processor?
    Cache memory is a small, fast memory located close to the CPU that stores frequently accessed data and instructions. It reduces the average time to access data from main memory (RAM) by exploiting locality of reference (temporal and spatial). Modern CPUs have multiple levels (L1, L2, L3) with increasing size and latency. A larger cache improves hit rate but increases cost and power consumption.
    How do input and output devices affect system performance?
    Input devices like keyboards and mice have minimal impact on overall performance, but high-speed input (e.g., from sensors or cameras) can require fast data transfer via USB or Thunderbolt. Output devices like high-resolution monitors or 3D printers demand significant processing power for rendering. Storage devices affect boot times, application loading, and data access. Slow I/O can bottleneck the CPU, so balanced system design is important.