Waterfall Model
Waterfall Model
Waterfall Model
When to use:
The model is used when the requirements are well known, clear and fixed.
The project is large.
Also used when working on an experienced project.
V-Model
Advantages of V-Model:
It's simple and easy to use.
The model has applicability in situations where requirements are well defined and stable.
Testing tasks like as planning and developing tests take place prior to coding.
Quick and saves time
As a result, the waterfall model has a better probability of succeeding.
Disadvantages of V-Model:
Very strict.
The least adaptable.
Because software is developed during the implementation phase, no early prototypes are created.
If any modifications occur in the middle of the project, the test documents, as well as the
requirement documents, must be updated.
V-Model is risky.
When to use:
The project is short and the technology is understood.
The product definition is clear.
When need to describe the development of the system and its subsystems.
Incremental Model
When to use:
When the requirements are superior.
A project has a lengthy development schedule.
When the customer demands a quick release of the product.
Prototyping Model
Spiral Model
Advantages of spiral model:
As a result of the extensive risk analysis, risk avoidance is improved.
It's ideal for big, mission-critical projects.
Controlled permission and documentation.
At a later time, further functionality can be introduced.
Early in the software life cycle, software is created.