0% found this document useful (0 votes)
96 views4 pages

Spiral Model and Waterfall Model

The document compares and contrasts the Spiral, Waterfall, Agile, and Iterative models. The Spiral model allows for better risk management than the Waterfall model but has a more complex process. The Waterfall model is simpler to understand but has higher risks. The Agile model delivers partial working solutions earlier and is suitable for smaller projects, while the Spiral model has undefined end points and is better for larger projects. The Iterative model identifies and resolves risks through iterations while the Agile model focuses on adaptability and rapid development through incremental builds.

Uploaded by

Sonakshi Das
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
96 views4 pages

Spiral Model and Waterfall Model

The document compares and contrasts the Spiral, Waterfall, Agile, and Iterative models. The Spiral model allows for better risk management than the Waterfall model but has a more complex process. The Waterfall model is simpler to understand but has higher risks. The Agile model delivers partial working solutions earlier and is suitable for smaller projects, while the Spiral model has undefined end points and is better for larger projects. The Iterative model identifies and resolves risks through iterations while the Agile model focuses on adaptability and rapid development through incremental builds.

Uploaded by

Sonakshi Das
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

SPIRAL MODEL AND WATERFALL MODEL

SPIRAL MODEL

WATERFALL MODEL

1] Spiral model is not suitable for


small projects.

1] Waterfall model is suitable for


small projects.

2] Better risk management.

2] High amount of risk and


uncertainty.

3] Process is complex.

3] Easy to understand.

4] The process may go indefinitely.

4] Stages are clearly defined.

5] This model is suitable for long and


ongoing projects.

5] This model is not suitable for long


and ongoing projects.

6] Iterations are followed

6] Sequence is followed

7] Flexible with user requirements

7] Requirements once fixed cannot be


modified

8] Refinements are easily possible

8] Refinements are not so easy

9] Phases are repeated itself

9] Phases are processed and


completed one at a time.

AGILE MODEL AND SPIRAL MODEL

AGILE MODEL

SPIRAL MODEL

1] More risk of sustainability and


maintenance.

1] Better risk management

2] Minimum rules, documentation easily


employed.

2] Large number of intermediate stages


requires excessive documentation.

3] Little or no planning required.

3] Planning is required.

4] Easy to manage.

4] Management is more complex.

5] Early delivery of partial working


solutions.

5] End of project may not be known.

6] Suitable for small projects.


7] Depends heavily on customer
interaction

6] Not suitable for small or low risk


projects.
7] Does not depend heavily on
customer interaction

8] Every iteration is a separate


model

8] Every iteration is not a


separate model

9] Agile is the combination of


iterative and incremental

9] Spiral is the combination of


iterative and waterfall

AGILE MODEL AND ITERATIVE MODEL


AGILE MODEL

ITERATIVE MODEL

1] It contains more risk of sustainability,


maintainability and extensibility.

1] Risks are identified and resolved during


iteration

2] Agile method breaks the the product in


small incremental builds. These builds are
provided in iteration.

2] An iterative life cycle model, project is


divided into different builds which are
proceed iteratively.

3] It is incremental and iterative model.


So it can be used to build more complex
project.

3] It is iterative, all builds are developed,


tested
Iteratively.

4] The main focus is on adaptability and


customer satisfaction with rapid
development of project

4] The main focus is on producing new


version of software at the end of each
iteration to satisfy customer needs.

5] It can be used to develop more complex


projects.

5] It can not be used for more complex


projects as iterative practice will increase
complexity, time requirement.

6] Quick in development of application

6] Comparatively slower development

7] Various modules of the application can


be developed simultaneously
8] Constant monitoring is required

7] Only 1 module is developed at a time

9] More flexible with customer


requirements

9] Less flexible

10] Evaluation is done more frequently

10] Evaluation is after every iteration

8] Monitoring is required after every


iteration

resulting in better error detection

hence errors if any are detected after a delay

11] Progress cannot be clearly measured.

11] Progress can be clearly measured.

12] Less resoures are required.

12] More resoures are required.

You might also like