Qualification:
Cambridge Advanced National in Computing (AAQ)
Unit:
F160: Fundamentals of Application Development
Certificate:
Computing: Application Development (H029 / H129)
2.1 - Software Development Models
Watch on YouTube:
Software Development Models
Waterfall
Rapid Throwaway
Incremental
Evolutionary
Rapid Application Development
Spiral
Agile
There are seven software development models you need to know:
​​
-
Traditional models: Waterfall​​
-
Prototype models: Rapid Throwaway, Incremental, Evolutionary​​
-
Iterative models: Rapid Application Development (RAD), Spiral, Agile
​
For each development model, you need to know:
​​
-
Its characteristics.
-
How to represent it in a diagram.
-
Its advantages and disadvantages.
-
The types of development it is suitable for.
Software Development Models
Each development model has its own video below but you also need to know the advantages and disadvantages of using development models in general.
Waterfall Model
The waterfall model is a linear and structured approach where each phase is completed one at a time in order.
It needs all requirements to be clearly defined at the start, with little to no changes allowed once a phase is finished.
This model is best suited for projects with fixed requirements and minimal risk of change.
Rapid Throwaway Prototype Model
The rapid throwaway prototype model involves quickly creating temporary prototypes to explore ideas and gather user feedback before building the final system.
​
Prototypes are discarded after they help refine requirements, and are especially useful in projects where user needs are initially unclear.
​
This model is suitable when user interaction and efficient interface design are critical.
Incremental Model
The incremental model develops a system in small, manageable sections with each part being designed, built and tested individually.
Functionality is added step by step until the full system is complete.
This approach allows for early partial deployment and easier handling of changing requirements over time.
Evolutionary Prototype Model
The evolutionary prototyping model involves building an initial prototype that is continuously improved based on user feedback until it becomes the final system.
Unlike throwaway prototyping, the prototype is not discarded but gradually evolves into the full product, once the user is satisfied.
This model is ideal when user requirements are expected to change or develop over time.
Rapid Application Development (RAD)
The rapid application development (RAD) model focuses on quickly building software through iterative development and frequent user feedback.
It uses reusable components, time-boxing and constant feedback to speed up the delivery of an effective final product.
RAD is best suited for projects that need to be completed quickly and where requirements can evolve during development.
Spiral Model
The spiral model combines iterative development and risk management, progressing through repeated cycles of planning, risk assessment, engineering (development and testing) and evaluation.
​
Each loop focuses on identifying and addressing risks early in the project.
​
It is ideal for complex and high-risk projects where requirements may change over time.
Agile Model
The agile model is an iterative and flexible approach that progresses in small, usable chunks called iterations (or sprints).
It relies on frequent collaboration with stakeholders and user feedback to adapt to changing requirements.
​
This model is ideal for dynamic projects where quick delivery and frequent updates are important.
Questo's Questions
2.1 - Software Development Models:
​​​
1. Choose three development models to explain and draw a diagram for each. [6]
​​​
2. A large company is making the next sequel in a hugely popular video game series, FieldBattle 2043. Justify which application development model(s) they should use (and which they shouldn't). ​[5]
​
3. Describe the advantages and disadvantages of any development models you have not covered in Q1 or Q2. ​[6]
Agile development is named after the 'Agile Manifesto' - a set of principles for software development agreed by a group of developers at a ski resort in Utah, USA in 2001.
Did You Know?
