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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,d4801f5d6baa249d
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!j27g2000cwj.googlegroups.com!not-for-mail
From: JPWoodruff@gmail.com
Newsgroups: comp.lang.ada
Subject: Re: F-22 Raptor software problem
Date: 27 Feb 2007 21:09:45 -0800
Organization: http://groups.google.com
Message-ID: <1172639385.361444.188410@j27g2000cwj.googlegroups.com>
References: <UDtEh.6201$iF.5520@trndny03>
   <1172502110.098416.297700@q2g2000cwa.googlegroups.com>
   <es1ff7$unm$1@f04n12.cac.psu.edu>
NNTP-Posting-Host: 24.4.18.74
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1172639391 30964 127.0.0.1 (28 Feb 2007 05:09:51
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Wed, 28 Feb 2007 05:09:51 +0000 (UTC)
In-Reply-To: <es1ff7$unm$1@f04n12.cac.psu.edu>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.0.10) Gecko/20070216 Firefox/1.5.0.10,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: j27g2000cwj.googlegroups.com; posting-host=24.4.18.74;
   posting-account=fJYhjA0AAADq5HS0Ommw0DzKlat-I76I
Xref: g2news2.google.com comp.lang.ada:9592
Date: 2007-02-27T21:09:45-08:00
List-Id: <comp.lang.ada>

On Feb 27, 6:33 am, "Bob Spooner" <r...@psu.edu> wrote:
> "Aurele" <aurele.vit...@gmail.com> wrote in message
>
> news:1172502110.098416.297700@q2g2000cwa.googlegroups.com...> On Feb 26, 3:55 am, "Alex R. Mosteo" <devn...@mailinator.com> wrote:
>
> > Well, someone is likely to lose their job for improperly implementing
> > the geoid and/or datum model!
>
> I would be inclined to think that the (derived) requirements were
> incompletely specified and therefore didn't cover the case of what happens
> when the nav system, while using GPS signals for time, crosses the date line
> (or something like that.)  -- Bob


Something's bothering me about this case, and hasn't been mentioned
yet.

I think I'm correct in guessing that this aircraft has been in service
for some time. If that's true, then almost certainly some F-22 has
crossed the dateline without difficulty in the past. So it's a change
in the software that started the failure.

My own experience taught me it's difficult to assure integrity as a
large system evolves. The system needs an effective configuration
control board, and that team needs a really sound process.  This is
easier said than done.   We can hope that practical "lessons learned"
will be shared when this case has been analyzed.