Verification
1. Definition
Verification is the process of evaluating work products (documents, designs, requirements, code, test cases) to ensure they conform to specified requirements and standards, without executing the software.
Verification answers the question: “Are we building the product right?”
2. Purpose of Verification
- Identify defects early in the lifecycle
- Prevent misunderstandings and incorrect implementation
- Ensure completeness, consistency, and correctness of requirements
- Reduce rework and cost
- Improve overall product quality
3. Nature of Verification
- Static activity (no execution of software)
- Performed before dynamic testing
- Focuses on documentation and design quality
4. Verification Activities
- Requirement reviews
- Requirement walkthroughs
- Design reviews
- Test case reviews
- Code reviews (conceptual understanding)
- Checklist-based inspections
5. Verification Techniques
- Reviews
- Walkthroughs
- Inspections
- Peer reviews
6. Work Products Verified
- Business Requirement Documents (BRD)
- Functional Requirement Specifications (FRS)
- User stories
- Design documents
- Test plans and test cases
7. Verification in SDLC
| SDLC Phase | Verification Activity |
|---|---|
| Requirements | Requirement review |
| Design | Design walkthrough |
| Development | Code review (conceptual) |
| Testing | Test case review |
8. Benefits of Verification
- Detects defects before development starts
- Prevents incorrect features from being built
- Saves time and cost
- Improves clarity and shared understanding
9. Verification vs Testing
| Aspect | Verification | Testing |
|---|---|---|
| Type | Static | Dynamic |
| Execution | No | Yes |
| Focus | Process & documents | Product behavior |
| Goal | Prevent defects | Detect defects |
10. Real-Time Example
If a requirement says:
“User should receive an email notification”
Verification checks:
- Is the requirement clear?
- Is email type defined?
- Is trigger condition specified?
Before any development starts.
11. Common Mistakes
- Skipping requirement reviews
- Assuming clarity without questions
- Not documenting review findings
- Treating verification as optional
12. Interview-Ready Answers
Short answer:
Verification is a static process of reviewing documents and artifacts to ensure they meet requirements without executing the software.
Detailed answer:
Verification ensures that the product is being built correctly by reviewing requirements, designs, and test artifacts early in the lifecycle to prevent defects.
13. Key Takeaway
Verification ensures defects are prevented early, before they become costly failures.