The Win-Win spiral approach is an extension
of the spiral approach. The phase in this approach is same as the phase
in the spiral approach. The only difference is that at the time of the
identifying the requirements, the development team and the customer hold
discussion and negotiate on the requirements that need to be included
in the current iteration of the software.
The approach is called Win-Win because it is a winning situation for
the development team and also for the customer. The customer wins by
getting the product that fulfils most of the requirements while the
development team wins by delivering software which is developed with all
the requirements established after negotiations with the customer. The
Win-Win approach is generally used when you have time-bound releases.
Advantages of Spiral model:
- High amount of risk analysis hence, avoidance of Risk is enhanced.
- Good for large and mission-critical projects.
- Strong approval and documentation control.
- Additional Functionality can be added at a later date.
- Software is produced early in the software life cycle.
Disadvantages of Spiral model:
- Can be a costly model to use.
- Risk analysis requires highly specific expertise.
- Project’s success is highly dependent on the risk analysis phase.
- Doesn’t work well for smaller projects.
0 comments:
Post a Comment