Eduqas A-Level Computer Science A500QS
Data Structures: Arrays, Records and Hash Tables
Stacks, Queues, Linked Lists and Trees
Boolean Logic and Simplification
Algorithms, Pseudo-Code and Programming Constructs
Variables, Scope, Parameters and Identifiers
Recursion and Modular Programming
Sorting Algorithms
Searching and Shortest-Path Algorithms
Big O Notation and Algorithm Efficiency
Validation, Verification and Testing
Data Compression
Programming Paradigms and Computer Languages
Systems Analysis, Maintenance and Documentation
System Design and Human-Computer Interaction
Software Engineering Tools and Translators
Computing, Society and the Law
Computer Architecture, the Processor and Assembly Language
Input, Output and Secondary Storage
Networks, Protocols and the Internet
Data Transmission and Network Performance
Number Systems and Binary Arithmetic
Data Types, Characters and Floating Point
Files, Records and File Organisation
Databases, Normalisation and Entity Modelling
SQL, Big Data and Distributed Systems
The Operating System and Its Modes
Interrupts, Memory Management and Scheduling
Types of Software System
Data Security, Cryptography and Attack
System Design and Human-Computer Interaction
The design review
- 3 things to know
- Component 1
Overview
The formal check before any code is written — that the design matches its specification, that the techniques chosen are the right ones, and that the interface suits its users.
What you need to know
Answer each one before you reveal it.
State the three things a design review must confirm.
Why is a design review held before coding begins?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What is a design review?
Model answer
A design review is a formal check of a proposed design before it is built. Reviewers examine the design against the specification.
- 2
State the three things a design review must confirm.
Model answer
A review confirms that the design matches its specification. The reviewers also judge whether the chosen techniques are the right ones and whether the interface suits its users.
- 3
Why is a design review held before coding begins?
Model answer
A fault caught in the design costs a change to a document. The same fault found after coding costs rewriting and retesting the program.
- 4
How is correspondence between a design and its specification checked?
Model answer
Each requirement in the specification is traced to the part of the design that meets it. Any requirement with no matching design element is missing.
- 5
How does a review judge whether the right techniques were chosen?
Model answer
The reviewers ask whether the chosen data structures, algorithms and file organisation suit the problem. A better technique may exist for the same requirement.
- 6
Give one example of an inappropriate technique a design review might catch.
Model answer
A linear search chosen for a million-record lookup would be caught. An indexed or hashed access method is required at that scale.
Other ways to work this
The same content, four other ways.
What is inside Levo
Six ways to work the same material.
Every question in System Design and Human-Computer Interaction, on a schedule.
Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.
Or £46 a year, about £3.83 a month. Cancel anytime.