Used where failure means death, not just a 404 error.
Author:Sambath Kumar Natarajan(Connect)Version:1.0
V-Model
The V-Model connects Requirements directly to Validation at every level. It is the gold standard for Automotive, Medical, and Aerospace.
Structure
- Left Side (Design): Requirements → Arch → Detailed Design
- Right Side (Verification): UAT ← System Test ← Unit Test
Why It Matters
In a typical SaaS startup, if you ship a bug, you revert. In a pacemaker, if you ship a bug, you cause critical failure.
Decision: Should you use V-Model?
| Factor | Weight | Score | Note |
|---|---|---|---|
| Safety Criticality | 5 | 5 | Essential for ISO 26262/IEC 62304 |
| Hardware Integration | 4 | 5 | Hardware leads times dictate software gates |
| Market Speed | 3 | 1 | Very slow. Do not use for consumer apps |
Common Mistakes
- Paperwork Over Process: Generating documents just for the audit, not for engineering value.
- Late Integration: Waiting until the very end of the 'V' to plug the cable in. (Hint: It never works).