In lectures on March 31st we discussed the "big V" project life cycle for testing. Study the testing framework outlined below, and relate the steps in it to those in the V model.
TEST FRAMEWORK
1. Business analysis
2. Requirements
- requirements testability review
- user interviews
- test analysis and design plan
- testing strategy
3. High level design
- non-functional test planning
- functional test planning
4. Detailed design
- functional test planning (continued)
- test planning
- test data generation
5. Modules integration
- unit testing planning
- unit testing
- integration testing
- results review
- test bed setup
6. System/user acceptance testing
- functional testing
- results review
7. Rollout
- non-functional testing
- results review
SAMPLE SOLUTION
The "big V" model outlined the design and development phases
of a project in a descending waterfall-like model (forming the
left half of the V) and the testing phases in a bottom-up
approach on the right half of the V.
Going left to right, the planning and preparation for each level of
testing could be seen as the interior of the V, with those activities
taking place at the same time as the other design/development/testing
phases were underway, e.g.
Requirements --> test plan/prep --> User acceptance tests
\ /
\ /
High level design --> test plan/prep --> Integration testing
\ / (modules, subsytems)
\ /
Detailed design --> test plan/prep --> Unit test
\ /
\ /
Implementation (Coding)
The model given in the question has many of the same stages,
where the numbered points identify where on the "V" we can
start the relevant test activities, and the subpoints list
the activities that can be begun there. E.g.
1. Biz analysis (new) 7. Rollout (new)
\ /
2. Requirements --> 2. subpoints --> 6. User acceptance tests
\ /
\ /
3. High level design --> 3. subpoints --> 5. subpoints cont.
\ /
\ /
4. Detailed design --> 4. subpoints --> 5. subpoints
\ /
\ /
(coding) 5. Module integration
|