The spiral model, a methodology that maximizes risk management to reduce risk to its lowest form. It is also more appropriate for handling complex requirements that are needed for the information system. Because of its iterative process, it is easy to adjust to ongoing requirements that the client may want without any issues arising. This is best suited for companies that are medium to large of size, as most of these system projects run from medium to high risk. Although this can be a very expensive approach, it is one of the most preferred due to its iterative risk analysis approach to building a system. Therefore small businesses will not benefit from this approach due to its cost and having low risk for their type of projects.
For a multimedia …show more content…
From there constraints are laid out with possible alternatives of the system. Extensive calculations are made to see what kind of risk are we dealing with, dealing with the most uncertain risks preferably first. It is important to resolve these risks as soon as possible to prevent any issues down the track of developing the system. As (Boehm, 1988) has stated, “Risk are situations or possible events that can cause a project to fail to meet its …show more content…
Iteration like before is what this approach is all about, the more we iterate the more we understand of what we are dealing with. Having a complete understanding of how the system works, through cycles of iterations is the key to a successful project. As (Osterweil, 2011) has stated “… with iterations driven by the need to understand and contain risk, and with each iteration yielding the increasingly deep and complete understandings upon which successful software development must rest.”
There are many advantages to this approach, but when there are advantages, there are also disadvantages. The advantages of the spiral model approach are of the following:
• The high amounts of risk analysis performed, therefore risks are contained and controlled.
• Good for large and mission-critical projects.
• Strong approval and high level of documentation control.
• Addition requirement can be added at a later time, without disruption of the project life cycle.
• The software is produce in the early stages of the life cycle, so the client gets to see part of the software before being fully
For a multimedia …show more content…
From there constraints are laid out with possible alternatives of the system. Extensive calculations are made to see what kind of risk are we dealing with, dealing with the most uncertain risks preferably first. It is important to resolve these risks as soon as possible to prevent any issues down the track of developing the system. As (Boehm, 1988) has stated, “Risk are situations or possible events that can cause a project to fail to meet its …show more content…
Iteration like before is what this approach is all about, the more we iterate the more we understand of what we are dealing with. Having a complete understanding of how the system works, through cycles of iterations is the key to a successful project. As (Osterweil, 2011) has stated “… with iterations driven by the need to understand and contain risk, and with each iteration yielding the increasingly deep and complete understandings upon which successful software development must rest.”
There are many advantages to this approach, but when there are advantages, there are also disadvantages. The advantages of the spiral model approach are of the following:
• The high amounts of risk analysis performed, therefore risks are contained and controlled.
• Good for large and mission-critical projects.
• Strong approval and high level of documentation control.
• Addition requirement can be added at a later time, without disruption of the project life cycle.
• The software is produce in the early stages of the life cycle, so the client gets to see part of the software before being fully