Aspects of software development | AQA Computer Science 7517

Choose a revision tool

Start revising Aspects of software development

Quick active recall practice

Quick multiple-choice practice

Mixed practice and exam-style prompts

Syllabus checklist

0 objective pages available

Analysis1 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.

Design1 objectives

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.

Implementation1 objectives

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.

Testing1 objectives

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.

Evaluation1 objectives

Data modelAbstractionModular structureIterative designCritical pathPrototypeTest dataAcceptance testingEvaluation criterionSuccess criterion

Link each analysis activity to its purpose: When describing analysis, do more than list defining the problem, establishing requirements and creating a data model. Explain how each activity helps the proposed system to meet the problem and user needs.
Link design activities to their purpose: When explaining design, name relevant activities and explain how they help plan the solution before construction.

Ignoring the intended users: Explain that requirements must be established through interaction with the intended users of the system.
Treating design as only interface appearance: Remember that design can also include the data model, algorithms, modular structure and clear documented interfaces.

Choose a learning objective

Objectives are grouped by subtopic so students can jump straight to the exact skill they want to revise.