V-Test Model
0 likes37 views
The document outlines the V-Model of software testing, detailing various stages such as proposal, requirements, test planning, design, and coding phases, emphasizing the importance of testing as a lifecycle activity. Each phase includes specific testing activities that ensure structures are adequate, consistent, and verifiable. It also highlights critical roles and responsibilities for development, testing, and customer involvement throughout the software development lifecycle.
V-Test Model
- 1. V - Test Model Mustufa Sir
- 2. Index 1. Introduction 2. V Model for software 3. Testing during proposal stage 4. Testing during requirement stage 5. Testing during test planning phase 6. Testing during design phase 7. Testing during coding phase 8. VV model 9. Critical roles and responsibilities Mustufa Sir
- 3. 1. Introduction • Testing is a lifecycle activity • Starts with proposal software development is made. • For every development activity there is a testing activity. Mustufa Sir
- 4. 2. V Model for software Mustufa Sir
- 5. 1. Structured approach to testing 2. Activities during each phase of SDLC 3. Analyse structures produced during development phases for adequacy and testability 4. Generate test sets based on structures 5. Additional activities during design and coding 6. Determine that structures are consistent with previously generated structures 7. Define and redefine test sets. Mustufa Sir
- 6. 3. Testing during proposal stage • Requirement statement development starts from system proposal. • The success of these approach during proposal stage lies in defining the problem and proposed solution. Mustufa Sir
- 7. 4. Testing during requirement stage 1. Adequate 2. Clear/Unambiguous 3. Verifiable/Testable 4. Measurable 5. Feasible 6. Not conflicting with each other Mustufa Sir
- 8. 5. Testing during test planning phase 1. Generate test plan to support development activities 2. Generate test cases based on system structure 3. Analyse requirement/design coverage Mustufa Sir
- 9. 6. Testing during design phase 1. Consistency with respect to requirements 2. Analyse design for errors 3. Analyse error handling 4. Developer verify information flow and logical structure 5. Testers inspect design in detail Mustufa Sir
- 10. 7. Testing during coding phase 1. Coding standard/ Guideline implementation 2. Coding optimisation 3. Code interpreting design 4. Unit testing Mustufa Sir
- 12. Mustufa Sir
- 13. 9. Critical roles and responsibilities Development • Project planning activities including requirement elicitation, estimation, project planning, scheduling, definition of quality attributes required by the customer etc • Resourcing may include identification and organization of adequate number of people, machines, hardware, software, tools etc Mustufa Sir
- 14. Testing • Test planning including test strategy definition, test planning, test case writing etc • Resourcing may include identification and organization of adequate number of people, machines, hardware, software, tools etc Mustufa Sir
- 15. Customer • Specifying requirements and signing off requirement statement, designs etc • Participating in acceptance testing as per roles and responsibilities defined in acceptance test plan Mustufa Sir