From: JP Thornley <jpt@diphi.demon.co.uk>
Subject: Re: Mission Critical Definition and Compliance
Date: 1998/01/31
Date: 1998-01-31T00:00:00+00:00 [thread overview]
Message-ID: <157334680wnr@diphi.demon.co.uk> (raw)
In-Reply-To: 34D0F22A.41C67EA6@swl.msd.ray.com
In article: <34D0F22A.41C67EA6@swl.msd.ray.com> "John J. Cupak Jr."
<jcj@swl.msd.ray.com> writes:
> I have been asked to locate the *official* definition of "Mission
> Critical" software, together with the process for defining which
> language comply with it.
>
I would use the term to distinguish it from safety-critical (with which
some people confuse it).
My informal defitions are something like:-
Safety-critical code is any code whose incorrect operation creates the
risk of an accident leading to death or serious injury.
Mission-critical code is any code whose incorrect operation places a
mission at risk, but doesn't create any significant risk of an accident.
So if mission-critical code goes wrong then the plane has to turn back,
but can be expected to return safely, if safety-critical code goes wrong
then the plane might not get back at all.
HTH
Phil
--
------------------------------------------------------------------------
| JP Thornley EMail jpt@diphi.demon.co.uk |
| phil.thornley@acm.org |
------------------------------------------------------------------------
next prev parent reply other threads:[~1998-01-31 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-29 0:00 Mission Critical Definition and Compliance John J. Cupak Jr.
1998-01-29 0:00 ` Markus Kuhn
1998-01-29 0:00 ` Ed Falis
1998-01-29 0:00 ` Steve Doiel
1998-01-31 0:00 ` JP Thornley [this message]
1998-02-01 0:00 ` Marin David Condic
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox