This is a discussion on Waterfall model,Spiral model within the Software Testing forums, part of the Software Quality Assurance category; Can anyone share waterfall,spiral model Anbudan, Prasath.K...
| |||||||
| Register | FAQ | Members List | Calendar | Mark Forums Read |
| |||
| This is the most common and classic of life cycle models, also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed in its entirety before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. Waterfall Life Cycle Flow (Requirement) | | --->(Design) | | --->(Implementation & Unit Testing) | | ---> (Integeration and System Testing) | | --->(Operation) Advantages Simple and easy to use. Easy to manage due to the rigidity of the model each phase has specific deliverables and a review process. Phases are processed and completed one at a time. Works well for smaller projects where requirements are very well understood. Disadvantages Adjusting scope during the life cycle can kill a project No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Poor model for complex and object-oriented projects. Poor model for long and ongoing projects. Poor model where requirements are at a moderate to high risk of changing. |
| |||
| The spiral model is similar to the incremental model, with more emphases placed on risk analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation. A software project repeatedly passes through these phases in iterations (called Spirals in this model). The baseline spiral, starting in the planning phase, requirements are gathered and risk is assessed. Each subsequent spirals builds on the baseline spiral. Requirements are gathered during the planning phase. In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. Software is produced in the engineering phase, along with testing at the end of the phase. The evaluation phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral. In the spiral model, the angular component represents progress, and the radius of the spiral represents cost. Spiral Life Cycle Model (See attachment) Advantages High amount of risk analysis Good for large and mission-critical projects. Software is produced early in the software life cycle. Disadvantages Can be a costly model to use. Risk analysis requires highly specific expertise. Projects success is highly dependent on the risk analysis phase. Doesnt work well for smaller projects. |
![]() |
| Thread Tools | |
| Display Modes | |
| |
LinkBacks (?)
LinkBack to this Thread: http://www.discussweb.com/software-testing/1798-waterfall-model-spiral-model.html | |||
| Posted By | For | Type | Date |
| Waterfall Model Waterfall | The Waterfall Model: IT Project Management Solutions | This thread | Refback | 09-20-2007 07:16 PM |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Limitation in waterfall model | prasath | Software Testing | 1 | 08-20-2007 08:42 AM |
| what is the threading model used for ASP.Net? | mobilegeek | ASP and ASP.NET Programming | 1 | 07-21-2007 01:48 AM |
| Can anyone explain spiral model | prasath | Software Testing | 2 | 07-19-2007 11:13 PM |
| OSI model | vadivelanvaidyanathan | Server Management | 0 | 07-15-2007 06:18 PM |
| About W-model | stephen | Software Testing | 1 | 05-16-2007 06:00 AM |