Testing Models
One of the initial testing decisions can be the selection of a Testing Model, which determines and sets the order and progression of software tasks. Three of the more popular options are:
Agile (or Spiral) Model: Under this model the focus is on developing and releasing software in smaller portions, instead of all at once as a completed package. Testing is typically performed at the same time as development (programming of the code), with a tester assigned to a programmer, working side-by-side to check and adjust the code as necessary. The spiral comes from the path that is repeated until all portions of the software application are complete: Planning -> Design -> Development & Testing -> Implementation -> Evaluation [repeat].
Benefits include early release of critical portions of the software; negative aspects include a longer final completion timeline. View Image of Agile/Spiral Model
Waterfall (or ‘W’) Model: This model has steps very similar to the spiral model, except that the phases aren’t repeated. Evaluation is performed at the end of each phase to ensure accuracy and completeness, and the entire software package as a whole (instead of smaller portions) moves through the process. It gets its name from a cascading waterfall, with the notion that once one phase is complete the only direction it can continue on is down to the next phase.
Benefits include the ability to deliver a complete software package in a fairly quick time frame. Negative aspects include longer development time than the Agile model, and the possibility that the business requirements may be incomplete or require changes after development has been completed (due to issues or missing functionality found during testing).
View Image of Waterfall Model
‘V’ Model: This model gets its name from the V shape that the overall process takes. It has features of the Waterfall and Spiral/Agile model, but allows for movement in both directions of process, which often makes it the selected model. There is a specific testing/verification phase [right side of the V figure] assigned for each of the specific planning, design and development phases [left side of the V]. This model also supports both verification and validation efforts, as outlined on the Overview page.
Benefits include a high quality, complete software release; negative aspect is that this model usually has the longest time of software delivery to the Market. Note: because of its popularity and ability to provide high quality software, the V Model process will be examined and used throughout this website.
View Image of 'V' Model
Agile (or Spiral) Model: Under this model the focus is on developing and releasing software in smaller portions, instead of all at once as a completed package. Testing is typically performed at the same time as development (programming of the code), with a tester assigned to a programmer, working side-by-side to check and adjust the code as necessary. The spiral comes from the path that is repeated until all portions of the software application are complete: Planning -> Design -> Development & Testing -> Implementation -> Evaluation [repeat].
Benefits include early release of critical portions of the software; negative aspects include a longer final completion timeline. View Image of Agile/Spiral Model
Waterfall (or ‘W’) Model: This model has steps very similar to the spiral model, except that the phases aren’t repeated. Evaluation is performed at the end of each phase to ensure accuracy and completeness, and the entire software package as a whole (instead of smaller portions) moves through the process. It gets its name from a cascading waterfall, with the notion that once one phase is complete the only direction it can continue on is down to the next phase.
Benefits include the ability to deliver a complete software package in a fairly quick time frame. Negative aspects include longer development time than the Agile model, and the possibility that the business requirements may be incomplete or require changes after development has been completed (due to issues or missing functionality found during testing).
View Image of Waterfall Model
‘V’ Model: This model gets its name from the V shape that the overall process takes. It has features of the Waterfall and Spiral/Agile model, but allows for movement in both directions of process, which often makes it the selected model. There is a specific testing/verification phase [right side of the V figure] assigned for each of the specific planning, design and development phases [left side of the V]. This model also supports both verification and validation efforts, as outlined on the Overview page.
Benefits include a high quality, complete software release; negative aspect is that this model usually has the longest time of software delivery to the Market. Note: because of its popularity and ability to provide high quality software, the V Model process will be examined and used throughout this website.
View Image of 'V' Model