On 27 Sep 2003, Rick Eversole wrote: I also put forth the argument that flying *is* testing.
More accurately: flying is *integration* testing.
Performing integration testing before you have performed adequate unit testing is, in my experience, nearly always a net loss of manpower relative to doing more unit testing.
Please remember that our goal was not to develop an ideal engine, just design and build one that worked as designed.
It didn't really though.
However, that's all beside the point, because whether the failure happened on the test stand or in flight, the same lesson is there to be learned.
Yup. But the point is that everyone else's testing suffered this way- they all contributed equipment to the test and got little or no data back.
Still, it flew, and you made progress, and it's certainly not a total loss; it's just that you very probably would have done better if you'd have done more unit testing- no project development is ever optimal; but some projects are more optimal than others.
-Dave McCue
_______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
