AQA 7517 4.13.1.2: Design
The free BugBot lessons that teach this point, a robot to try it on, and the past-paper questions that test it.
What it covers
Every project passes through analysis, design, implementation and testing, but not in the same way. A methodology is an organised way of working through those stages: in what order, how often, and how closely the client is involved. The exam expects you to describe five, and, more importantly, to argue which suits a given project.
- Waterfall
- The spiral model
- Agile methodologies
- Extreme programming
- Rapid application development
- Comparing them
- Velocity in practice
Or do it in the simulator, with tasks that mark themselves
Lessons that teach it
- A14.2 Development methodologies Software development, law and ethics
Waterfall, spiral, agile, extreme programming and rapid application development: how each works, when to use it, and planning agile sprints. - A14.4 System design Software development, law and ethics
Structure charts, data flow diagrams, designing data, algorithms and the user interface, and printing a structure chart with recursion. - A14.9 Project: the delivery robot Software development, law and ethics
A small project taken through analysis, design, implementation, testing and evaluation, the way the NEA is written up.
Try it on a robot
The task from A14.2 Development methodologies, running here. Change the program and press Run.
The specification is AQA's own document; this page says which of our lessons teach point 4.13.1.2 and is not endorsed by the board.