Learning objective
Evaluation: Know the criteria for evaluating a computer system.
Read the explanation, check the common trap, then practise with flashcards and questions.
At a glance
0
Flashcards
0
Questions
Topic
Aspects of software development
Subtopic
Evaluation
Aqa A Level Computer ScienceSystematic approach to problem solving
Study support
Understand this objective
Quick explanation
Evaluation: Know the criteria for evaluating a computer system
- This point belongs to Aspects of software development, especially Evaluation.
- You need to be able to evaluation: Know the criteria for evaluating a computer system.
- Use the linked flashcards and practice questions to check recall, then practise applying the idea in an exam-style answer.
Why it matters
This objective helps connect Evaluation to exam-style questions, flashcards, and revision notes for Aspects of software development.
Quick student answer
A school system is evaluated against whether it provides every feature specified by its users. Which evaluation criterion is being applied?
Direct answer
Fitness for purpose
Key terms
- Evaluation criterion: A specific quality or requirement used to judge how well a computer system meets its intended purpose.
- Success criterion: An agreed, testable condition that indicates whether an aspect of a computer system has achieved the required standard.
Common trap
Naming criteria without evidence: Link each criterion to a test and state the evidence that would show success, such as user errors, response times or repeated correct results.
Related questions
Try this as a practice card
Question 1 of 4
Choose an answer, get feedback, then move sideways through the set.
0 of 4 attempted
Flashcard prompts
Flip through the key recall cards
Flashcard 1 of 4
Press Space to flip, arrows to move
Revision tools
Choose how to practise
Flashcards0 linked cards
No objective-specific flashcards are cached for this page. Use the topic hub to revise the surrounding flashcards without triggering a frozen-subject DB fallback.Open topic hub
Practice Questions0 linked questions
No objective-specific practice questions are cached for this page. Use the topic question bank to practise nearby curriculum questions without weakening the egress guard.Open topic questions
Related learning objectives
- Analysis: Be aware that before a problem can be solved, it must be defined, the requirements of the system that solves the problem must be established and a data model created. Requirements of system must be established by interaction with the intended users of the system. The process of clarifying requirements may involve prototyping/agile approach. Students should have experience of using abstraction to model aspects of the external world in a program.
Analysis
- Design: Be aware that before constructing a solution, the solution should be designed and specified, for example planning data structures for the data model, designing algorithms, designing an appropriate modular structure for the solution and designing the human user interface. Students should have sufficient experience of successfully structuring programs into modular parts with clear documented interfaces to enable them to design appropriate modular structures for solutions. Be aware that design can be an iterative process involving a prototyping/agile approach.
Design
- Implementation: Be aware that the models and algorithms need to be implemented in the form of data structures and code (instructions) that a computer can understand. Students should have sufficient practice of writing, debugging and testing programs to enable them to develop the skills to articulate how programs work arguing for their correctness and efficiency using logical reasoning, test data and user feedback. Be aware that the final solution may be arrived at using an iterative process employing prototyping/an agile approach with a focus on solving the critical path first.
Implementation
- Testing: Be aware that the implementation must be tested for the presence of errors, using selected test data covering normal (typical), boundary and erroneous data. Students should have practical experience of designing and applying test data, normal, boundary and erroneous to the testing of programs so that they are familiar with these test data types and the purpose of testing. It should also undergo acceptance testing with the intended user(s) of the system to ensure that the intended solution meets its specification. Students will only need to provide evidence of user feedback not details of the tests carried out by the end user.
Testing