SOFTWARE PROCESS MODELS

‘Classical’ model of system development...

• Waterfall models

• Prototyping Model

• Incremental Model

• Component-based development

Not suitable for project with uncertainty.

• Rapid Application Development (RAD)

• Component-based development

• Waterfall models

• Spiral model

It is discarded after the necessary information is gathered; it is not used in the final system.

• Rapid Application Development (RAD)

• Spiral model

• Incremental Model

• Throw-away prototype

Useful when user requirements are uncertain.

• Waterfall models

• Prototyping Model

• Spiral model

• Component-based development

can be time-consuming if several iterations are needed to refine the design.

• Prototyping Model

• Waterfall models

• Rapid Application

• Development (RAD)

  Incremental Model

short development time

• Incremental Model

• Rapid Application Development (RAD)

• Waterfall models

• Prototyping Model

Not suitable for system that cannot be modularized.

• Rapid Application Development (RAD)

• Waterfall models

• Prototyping Model

• Component-based development

What is the drawback of RAD?

• requires large number of resources

• Excessive documentation requirements.

• Not suitable when technical risks are high

• Long time completion

The software is designed, implemented, and tested in increments (smaller portions or modules) NOT delivering the entire system at once.

• Component-based development

• Spiral model

• Incremental Model

• Waterfall models

"These components are then integrated to create a complete system. "

This refer to..

• Rapid Application

• Component-based development

• Spiral model

• Development (RAD)

  Incremental Model