Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
The Spiral Model
Transcript of The Spiral Model
Who invented the
The spiral model was first described by Barry Boehm in 1986 in his paper 'A Spiral Model of Software Development and Enhancement'. He is an American software engineer and professor of computer science.
Thank you for watching...
How does it work?
The idea of the spiral methodology is that you start in the centre of the spiral, then follow it around. Each section represents a different stage, e.g. design, coding and testing (these are sometimes subdivided).
General model Spiral model
◦High amount of risk analysis so it is suitable for high-risk projects as risk is reduced
◦Good for large and mission-critical projects.
Improvements can be added at a later date.
◦Software is produced early in the life cycle.
◦Project estimates in terms of schedule, cost etc become more and more realistic as the project moves forward and loops in spiral get completed.
A highly customized product can be developed using this.
What is the Spiral Model?
The Spiral model places a lot of emphasis on risk analysis (detail design), and has four stages: Planning, Risk Analysis, Engineering and Evaluation, combining the features of the waterfall and prototype methodologies. It repeatedly goes through these phases in iterations.
The Spiral Model
What is it used for?
The spiral methodology is generally used for large, complicated, expensive and mission-critical projects.
An example of the use of the spiral methodology is the development of Windows 3.1 to Windows 2003 (also other Windows developments). They are huge and costly projects.
It is not appropriate for smaller projects.
It takes a lot of time.
It can be very costly.
Risk analysis requires expertise.
Its success is dependent on the risk analysis phase.
Requirement and design is not tested.
Problems can be caused in negotiating a development contract with the client.
The spiral structure means that you go through each step several times over so it's less likely that problems are overlooked, and there are several opportunities for evaluation and improvement. It also works well if you need to make a prototype.