A Level Computer Science Paper 1: 1.2.3 Software Development - Methodologies
This flashcard set outlines the Waterfall model, a linear approach where each stage must be completed before moving to the next. It highlights its simplicity and manageability as advantages, but notes key drawbacks like limited user involvement and inflexibility to changes.
Waterfall model
Each stage is completed before the next begins
The customer does not see the product until the end
Any change to the user requirements likely requires a restart
Key Terms
Waterfall model
Each stage is completed before the next begins
The customer does not see the product until the end
Any change to the user requirements likely...
Waterfall advantages
Simple to understand
Straightforward to manage
All self-contained
Waterfall disadvantages
Little user advantages
Software only produced late on
Too late to change if the user doesn’t like it
Waterfall model uses
Short projects with clear requirements
Spiral model
Continually looping through analysis, design, development and evaluation stages
Each loop forms a more refined prototype
Spiral advantages
Easy to manage
Some software produced early
Lots of user feedback
Can add functionality throughout
Related Flashcard Decks
Study Tips
- Press F to enter focus mode for distraction-free studying
- Review cards regularly to improve retention
- Try to recall the answer before flipping the card
- Share this deck with friends to study together
| Term | Definition |
|---|---|
Waterfall model | Each stage is completed before the next begins |
Waterfall advantages | Simple to understand |
Waterfall disadvantages | Little user advantages |
Waterfall model uses | Short projects with clear requirements |
Spiral model | Continually looping through analysis, design, development and evaluation stages |
Spiral advantages | Easy to manage |
Spiral disadvantages | Time-consuming |
Spiral uses | For long, fairly high-risk products with changing user requirements |
Agile model | A collection of methodologies to improve the flexibility of software development |
Agile advantages | Happens quickly |
Agile disadvantages | A lack of emphasis on design/documentation Needs clarity on desired outcome |
Agile uses | When small, frequent changes are needed or when needs rapidly change |
Extreme programming | An agile model involving a pair of programmers alongside an end-user |
Rapid Application Development | Uses workshops/focus groups to find user requirements |
RAD advantages |
A lot of feedback with customers |
RAD disadvantages | May not be perfect due to speed Changes in requirements are hard to adjust to |