[OT] Epic fail software testing

[François Chaplais]

Le 24 juil. 09 à 18:19, SparkOut a écrit :

>
>
> Sarah Reichelt-2 wrote:
>>
>> <http://it.slashdot.org/article.pl?sid=07/02/25/2038217>
>> Sooooo - we do all test our apps? Right?
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
> It's not the only example of software problems with "extreme value  
> systems":
> http://www.savive.com/casestudy/ariane5.html
> (I remember vividly because in the months prior to the launch I had  
> made a
> "day trip" from the UK to Florida with a part of the payload as hand
> luggage. It was to be integrated into a system in Cape Canaveral,  
> and then
> rebuilt into a satellite for launch from French Guiana.)
> -- 
> View this message in context: http://www.nabble.com/-OT--Epic-fail-software-testing-tp24619568p24647502.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
from what I heard from somebody who is really close to what happened  
in flight 501, the problem what actually diluted responsibility.  
Aerospatiale was the industrial project supervisor, but the final  
implementation of the GNC (guidance, navigation, control) into the  
actual hardware was subcontracted to another company. It seems that  
this company made the error at this stage, however it was the  
responsibility of the supervisor to make sure that things were done  
right. Doing a full check would have  probably implied some meddling  
with the contractor's intellectual and industrial property.
This potentially can happen in any collaboration, especially between  
competitors.

cheers
	François