V-Model - Advantages and Disadvantages
V-Model / VV-Model:
(Verification and Validation Model)
- In V-Model, at every stage we have testing.
- Static Testing:
Testing the project related documents is called as Static Testing.
- Review, Walk-through and Inspection are the Static testing techniques to verify the documents.
White Box Testing Techniques - Programming knowledge is required.
-> White Box Testing Techniques are Unit Testing and Integration Testing.
Unit Testing:
- Testing the single module.
- Developer conducts this testing.
Integration Testing:
- Developer conducts this testing.
- Testings conducted on code.
Black Box Testing Techniques - Programming knowledge is not required.
-> Black Box Testing Techniques are System Testing and User Acceptance Testing (UAT).
System Testing:
- Testers involved in this phase.
- No need to understand the code.
User Acceptance Testing (UAT):
- Conducted by Testers and Users.
Dynamic Testing:
- Testing the actual software.
Techniques:
- Unit Testing.
- Integration Testing.
- System Testing.
- User Acceptance Testing.
Static Testing:
- Testing the documents.
Techniques:
- Review.
- Walk-through.
- Inspection.
Verification and Validation
Verification:
- Checks whether we are building the right product or not.
- Focus on documentation.
- Verification typically involves -> Reviews, Walk-through, Inspection and Static testing techniques.
Validation:
- Checks whether we are building the product right or not.
- Focus on software.
- Verification typically involves actual testing.
- Takes place after verification's are completed.
- Dynamic testing techniques.
Advantages of V-Model:
- Testing is involved in each and every phase.
Disadvantages of V-Model:
- Documentation is more.
- Initial investment is more.
Static testing techniques:
1. Review
2. Walk-through
3. Inspection
Review: -> Conducts on documents to ensure correctness and completeness.
- Requirement reviews.
- Design reviews.
- Code reviews.
- Test plan reviews.
- Test cases reviews..
Walk-through: -> Informal reviews.
- It is an informal review, without any plan or schedule.
- Author reads the documents or code and discuss with peers.
- It is not preplanned and can be done whenever required.
- Also walk-through doesn't have minutes of the meet.
Inspection: -> It is a most formal review type.
- In which at least 3-8 people will involve in this meeting.
- Inspection will have a proper schedule which will be intimated via email to the concerned developer/tester.
No comments