From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f039470e8f537101 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-31 14:41:50 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newshub.sdsu.edu!elnk-nf2-pas!newsfeed.earthlink.net!wn14feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!sccrnsc04.POSTED!not-for-mail Message-ID: <3F298D00.20102@attbi.com> From: "Robert I. Eachus" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ariane5 FAQ References: <7u9Ua.13412$634.10307@nwrdny03.gnilink.net> <3F215120.1040706@attbi.com> <1059151910.357790@master.nyc.kbcfp.com> <3F248CEE.5050709@attbi.com> <3F269F90.2090706@attbi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 66.31.71.243 X-Complaints-To: abuse@comcast.net X-Trace: sccrnsc04 1059687707 66.31.71.243 (Thu, 31 Jul 2003 21:41:47 GMT) NNTP-Posting-Date: Thu, 31 Jul 2003 21:41:47 GMT Organization: Comcast Online Date: Thu, 31 Jul 2003 21:41:47 GMT Xref: archiver1.google.com comp.lang.ada:41111 Date: 2003-07-31T21:41:47+00:00 List-Id: Alexander Kopilovitch wrote: > Ok, I agree, I recognize that kind of logic (I think I have seen it several > times, when I contacted with high-position managers). And I think that too > high concentration of this kind of logic within a project is a smoking gun > by itself. Well, I downgrade the seriouseness of the allegation (in some > non-technical sense -;), but I'm still not sure enough that not giving the > part of the source code to the simulator's developers is true fact and not > just good guess. > > Anyway, assuming that that is a true fact, I'm going to include into the next > draft of FAQ the following Q-A pair: > > ---------------------------------------------------------------------------- > Q. So, if the limitations were clearly reflected in comments within the source > code then most probably they would be seen by the simulator's developers and > the disaster would be averted? > > A. Probably NO. Because that part of the source code (aligment function), > where the limitations were violated in the flight, was not given to the > simulator's developers. That happened because simulation of that function > of real device was excluded from the contract for the simulator development. > > The reason for that omission was that for Ariane 5 that function is not needed > after takeoff, and that before takeoff that function was really identical for > the Ariane 4 and Ariane 5. What was overlooked is that for the Ariane 4 that > function WAS executed after takeoff (about 40 seconds), so the unchanged real > device will execute that function for the Ariane 5 despite the absence of any > need for it there. > ---------------------------------------------------------------------------- As far as I know the simulation developers did have ACCESS to all of the source code. It was the documentation that they didn't have. So some programmer might have noticed that the alignment code ran for 40 seconds after ignition, but without the documentation the hypothetical simulation programmer had no reason to doubt that it was done for valid reasons. -- "As far as I'm concerned, war always means failure." -- Jacques Chirac, President of France "As far as France is concerned, you're right." -- Rush Limbaugh