Key term
WJEC A-Level Computer Science 601-5345-3
Hardware: Architecture, Memory and Storage
Networks and Data Transmission
Logic Gates and Boolean Algebra
Data Representation and Data Types
Data Structures
Organisation of Data: Files and Records
Database Systems
The Operating System
Algorithms and Programs
Principles of Programming
Systems Analysis
Software Engineering and Program Construction
Topic overviewIntegrated development environments and their purposeEditors, syntax highlighting and code entry toolsDebugging tools: breakpoints, stepping and watchesTranslation, source code and object codeLexical analysis and the symbol tableSyntax and semantic analysisCode generation and optimisation
Types of Software System
Practical Programming
Data Security and Integrity
Computing, Society and the Law
Topic overviewSocial and economic change from computingComputers and the nature of employmentThe digital divide and cultural changeEnvironmental cost of computingData protection and freedom of information lawThe Computer Misuse Act 1990 and computer crimeCopyright, surveillance and professional codes
Advanced Data Structures and Logic
Recursion, Sorting and Searching
Programming Paradigms and Translators
Topic overviewFunctional, declarative and imperative paradigmsClasses, methods and object-oriented designStandardisation of computer languagesAmbiguity in natural language and unambiguous notationBackus-Naur form and syntax diagramsCompilers, interpreters and assemblersTranslation and execution errors
System Design and Human-Computer Interaction
Software Engineering Tools and Professional Practice
Topic overviewSoftware tools for the software engineering processSoftware packages in systems analysis and specificationSoftware packages in systems designTesting tools and testing strategiesProgram version managementProgram libraries and project management toolsCodes of conduct and professional behaviour
Advanced Architecture and Assembly Language
Communication Networks and File Organisation
Number Representation and Floating Point
Databases and Distributed Systems
Topic overviewConsistency, redundancy and data independenceRelational organisation and normalisationRestructuring data into third normal formEntity relationship modellingQuery languages and SQLValidation, verification and the DBMSBig Data, data warehousing and miningDistributed systems and distributed databases
Operating System Management
Software Systems and Applications
Data Security, Cryptography and Attack
System Design and Human-Computer Interaction
Design review and validation
- 3 things to know
- A2 Unit 3
Overview
Design review and inappropriate technique that a review should catch.
What you need to know
Answer each one before you reveal it.
Your recallNot started
Key term
What is a design review?
Key term
In a design review, why is correspondence with the specification checked first?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What is a design review?
Model answer
A formal examination of a design, before it is implemented, to establish that it is correct and appropriate.
- 2
State the three things a design review must confirm.
Model answer
That the design corresponds to the specification, that the most appropriate techniques have been used, and that the user interface is appropriate.
- 3
Why is correspondence with the specification checked first?
Model answer
A design that solves a different problem is worthless however well constructed, and this is the cheapest point at which to discover it.
- 4
How is correspondence with the specification demonstrated?
Model answer
Each requirement is traced to the part of the design that meets it, and any requirement with nothing against it is a gap.
- 5
Why is a requirement with no corresponding design element a serious finding?
Model answer
It will be absent from the built system and will not be found until acceptance testing, when it is expensive to add.
- 6
What does it mean to confirm the most appropriate techniques have been used?
Model answer
Checking that the data structures, file organisation and algorithms chosen suit the volumes and access patterns the system will actually meet.
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.