Systems Engineering and the V-Model: Lessons from an Autonomous Solar Powered Hydrofoil¶
Sutherland et al. (2015, University of Tokyo)
A retrospective analysis of a failed student engineering project (autonomous solar-powered hydrofoil) using Systems Engineering frameworks.
The Project¶
An autonomous solar-powered hydrofoil engineering project that placed 3rd out of 4 teams due to systemic breakdowns — despite an otherwise advanced design.
Analysis Framework¶
The researchers mapped the project onto four V-Model views:
- Basic-V — The standard systems engineering lifecycle
- Dynamic-V — Captures iteration and cycles
- Development-V — Tracks design evolution
- Assurance-V — Maps verification and validation activities
They also compared the project against the Lean Systems Engineering Enablers (Oppenheim et al., 2011).
Key Findings¶
- All iterations were event-driven (reactive) rather than proactive
- Few requirements flowed down the V — requirements were not properly decomposed and allocated
- Verification was compressed into the final days — no time for meaningful testing
Redesigned Process¶
The authors propose a redesigned process that would dramatically improve outcomes:
- Explicit prototype loop
- Scheduled iterations (not event-driven)
- Assigned work product owners
- Phased V&V schedule
Broader Context¶
These findings mirror systemic inefficiencies found in large-scale government programs. Studies from NASA, GAO, and DoD consistently show that 60–90% of charged Systems Engineering time is wasted due to similar breakdowns in process discipline.