Re: Faulty languages and Liability

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Yup. The article got it dead wrong - which leads one to wonder who their
source is for this information. If it was a "systematic software design
error" as they claim, I'd find that to be at best "questionable". But it was
most certainly NOT a "buffer overflow" - as they claim. In the opinions of
many, it wasn't a "design error" at all - the software functioned 100%
according to its design. It was a "management error" to change the
requirements and then never test the software to be sure it met the new
ones.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"chris.danx" <spamoff.danx@ntlworld.com> wrote in message
news:2JIP8.6961$AZ6.519787@news6-win.server.ntlworld.com...
>
>
> That article blaims coders and buffer overflow errors for the Ariane 5
> fiasco.  I thought it was a management issue to reuse of a software module
> which worked ok for the Ariane 4?  That data valid for the Arian 5 was
> invalid data for Arian 4 (due to their differing flight characteristics),
> and that the module perfomed as it should have if it were in an Arian 4?
>
> i.e. the software worked ok, it was just in the wrong rocket.
>
>
> Perhaps someone should tell them.
>
>
> Chris
>
>