Answer
Flashcards · 7517 · Topic 13
Systematic approach to problem solving flashcards
5 cards on Topic 13. Pick a subtopic or study them all.
Study mode needs JavaScript. Every card is listed below, so you can still cover the answers and test yourself.
Choose your cards
Session complete
Worth another look:
All 5 cards
For a quick read-through or printing. Cover the right-hand side to test yourself.
Topic 13: Systematic approach to problem solving
- What happens in the analysis stage?
- The problem is defined and the requirements are established with the client and users, often by interview and observation, and agreed as measurable objectives. A data model may be produced.
- What happens in the design stage?
- Plans are made for the solution: data structures, algorithms, modular structure, the user interface, and the testing strategy.
- Why is prototyping and agile development useful?
- Working versions are shown to users early and often, so feedback can be used to refine the requirements and design as development proceeds.
- What are normal, boundary and erroneous test data?
- Normal: typical valid data, should be accepted. Boundary: values on and just beyond the limits. Erroneous: invalid data, should be rejected.
- What happens in the evaluation stage?
- The finished system is judged against the original requirements and objectives, with feedback from users, and possible improvements are identified.
Revise Systematic approach to problem solving further
- Study guideAQA A Level Computer Science (7517): Systematic approach to problem solving – Study Guide
- Revision notesAQA A-Level Computer Science: Systematic Approach to Problem Solving — Revision Notes
- Practice questionsAQA A-Level Computer Science: Systematic Approach to Problem Solving — Practice Questions