Software Test Services: Waterfall Model
As I promised in the previous post “Software Test Services: 7 Software Development Models That Should Know Every Tester”, now we will analyze one of the most widely used models in independent testing – Waterfall Development Model.
Waterfall Model
It is linear-sequential software development model and it gained its name because when developing a product, every stage or work period should be finished before next one will start its performance. Activity periods don’t overlap, and at the end of each period, dedicated testing team should decide whether all done correctly, and whether you can proceed to the next period.
As a rule, each model has its benefits and drawbacks, and waterfall model is not an exception.
Benefits:
- The model is easy and user-friendly.
- It is suitable for small projects, when all requirements are clear.
- It is easy for design periods management, because each period has an exact amount of work to be completed.
Drawbacks:
- If there is a bug on testing stage – it’s a costly process, because tester should make changes in the requirements, in design, in the code and also perform an additional regression testing as a service.
- The program may be unworkable in the last stage of product development life cycle.
- There can be big risks for the project and product.
Is not suitable for big projects.
- Unscheduled changes in requirements can lead to greater risks.
It is Recommended to Use When:
- Precise requirements.
- The technology is well known for project participants.
- Project is limited in time.
- Qualified personnel.
As I promised in the previous post “Software Test Services: 7 Software Development Models That Should Know Every Tester”, now we will analyze one of the most widely used models in independent testing – Waterfall Development Model.
Waterfall Model
It is linear-sequential software development model and it gained its name because when developing a product, every stage or work period should be finished before next one will start its performance. Activity periods don’t overlap, and at the end of each period, dedicated testing team should decide whether all done correctly, and whether you can proceed to the next period.
As a rule, each model has its benefits and drawbacks, and waterfall model is not an exception.
Benefits:
- The model is easy and user-friendly.
- It is suitable for small projects, when all requirements are clear.
- It is easy for design periods management, because each period has an exact amount of work to be completed.
Drawbacks:
- If there is a bug on testing stage – it’s a costly process, because tester should make changes in the requirements, in design, in the code and also perform an additional regression testing as a service.
- The program may be unworkable in the last stage of product development life cycle.
- There can be big risks for the project and product.
Is not suitable for big projects.
- Unscheduled changes in requirements can lead to greater risks.
It is Recommended to Use When:
- Precise requirements.
- The technology is well known for project participants.
- Project is limited in time.
- Qualified personnel.
Posts
No comments:
Post a Comment