Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Q1. Please compare waterfall and spiral models of SDLC on the basis of the liste

ID: 3668618 • Letter: Q

Question

Q1. Please compare waterfall and spiral models of SDLC on the basis of the listed criteria.

In addition to those already listed you may add more comparative criteria from your side to reflect your understanding of the two.

Criteria

Waterfall Model

Spiral Model

When are requirements specified?

Flexibility to change requirements?

Risks analysis

Duration of projects

Cost of projects

Rigidity

Repetitive phases

Expertise

Working prototype

Customer interaction

Criteria

Waterfall Model

Spiral Model

When are requirements specified?

Flexibility to change requirements?

Risks analysis

Duration of projects

Cost of projects

Rigidity

Repetitive phases

Expertise

Working prototype

Customer interaction

Explanation / Answer

Criteria

Waterfall Model

Spiral Model

When are requirements specified?

In waterfall the requirements are freezed

In Spiral Model the requirements are not freezed

Flexibility to change requirements?

The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement.

The Spiral Model approach can go back to the previous phase to handle changes in requirement.

Risks analysis

Not suitable for the projects where requirements are at a moderate to high risk of changing. So risk and uncertainty is high with this process model.

risk is not high in this model

Duration of projects

project schedule with 20–40% of the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to testing and implementation.

. Estimates ( i.e budget, schedule, etc) become more realistic as work progresses, because more important issues are discovered earlier.

Cost of projects

Waterfall model is not cost as compared to spiral model

Spiral Model is costely as Risk factor is covered.

Rigidity

waterfall model is a rigid model and can easily be
manageble

Spiral model is not rigid model

Repetitive phases

waterfall model is a iterative process

spiral model is not repetitive phase

Expertise

waterfall model is not expertise

spiral model is expertise

Working prototype

prototypes were not used in waterfall model

Prototypes can be viewed as tool for capturing
requirements eliminating design stage

Customer interaction

In waterfall model the customer
should have patience.

In spiral model there is a better communication between
developer and customer

Criteria

Waterfall Model

Spiral Model

When are requirements specified?

In waterfall the requirements are freezed

In Spiral Model the requirements are not freezed

Flexibility to change requirements?

The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement.

The Spiral Model approach can go back to the previous phase to handle changes in requirement.

Risks analysis

Not suitable for the projects where requirements are at a moderate to high risk of changing. So risk and uncertainty is high with this process model.

risk is not high in this model

Duration of projects

project schedule with 20–40% of the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to testing and implementation.

. Estimates ( i.e budget, schedule, etc) become more realistic as work progresses, because more important issues are discovered earlier.

Cost of projects

Waterfall model is not cost as compared to spiral model

Spiral Model is costely as Risk factor is covered.

Rigidity

waterfall model is a rigid model and can easily be
manageble

Spiral model is not rigid model

Repetitive phases

waterfall model is a iterative process

spiral model is not repetitive phase

Expertise

waterfall model is not expertise

spiral model is expertise

Working prototype

prototypes were not used in waterfall model

Prototypes can be viewed as tool for capturing
requirements eliminating design stage

Customer interaction

In waterfall model the customer
should have patience.

In spiral model there is a better communication between
developer and customer