SQA Higher Computing Science

A development methodology is an agreed way of organising the work of turning a problem into a working program. Two are needed at Higher: the iterative development process and agile methodologies. Both break the work into stages and both allow earlier work to be revised, and what separates them is how large each cycle is and how much the client is involved along the way. ## The stages of software development Whatever methodology is used, the same activities take place. They are usually listed as: 1. Analysis: finding out what the problem is and what the software must do. 2. Design: planning how the software will do it, using structure diagrams, pseudocode and wireframes. 3. Implementation: writing the code from the design. 4. Testing: checking the program against the requirements and finding errors. 5. Documentation: writing the user guide and technical information. 6. Evaluation: judging whether the finished solution is fit for purpose. 7. Maintenance: fixing faults and making changes after the software is in use. A methodology decides how these activities are ordered, how often they are repeated and who takes part. ## The iterative development process In the **iterative development process** the stages are followed in order, but each stage can send the team back to an earlier one. Testing may show that a design decision was wrong, so the team returns to design, changes it, and implements and tests that part again. Evaluation may show that a requirement was misunderstood…