| Name |
Key Characteristics |
Applicability |
| Waterfall |
- A sequential approach to building a system in which iteration is not visibly evident.
- Elaborate and well-defined documents form the basis of obtaining feedback.
- In practice, prototypes are used to clarify requirements and validate design and thus reducing the over dependence on documents.
|
This model is suited for projects with a complete and clearly defined requirements based on well-understood technologies. |
| Module/ Component Waterfall |
- Project is divided into a set of Modules
- based on dependency, business needs etc.
- Each module (or a set of Modules) is developed
independently and follows the Waterfall model.
- Different Modules can be either undertaken
sequentially or in parallel.
- Specific attention required to Interface Design,
Integration and Transition.
|
This model typically
applies to large business applications made up of
multiple subsystems or modules. |
| Incremental |
- Development is carried out in increments
- Business drives the allocation of features to each increment
|
Suitable for projects where the complete requirements can not be determined upfront – may be based on market feedback, competitive pressures etc. |
| Task Based |
- Customer specifies tasks
- Tasks could pertain to any phase of the SDLC
- Seen from SRA’s viewpoint, there is
no pattern amongst the tasks
|
Typically used in Retainer Teams |
| Maintenance |
- Covers maintenance of SRA-developed systems
as well as Third-party systems.
- Provides for an explicit transition phase
in the case of Third-party applications
|
As the name implies, this model is suited for Application Support and Maintenance |
