TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Fri, 18 Dec 1998 13:40:13 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <"NOTES_CORRELATION_ITEM*"@MHS>
Content-Type: text/plain; charset=ISO-8859-1; name="Lotus"
From: Phil Thornley <[log in to unmask]>
Parts/Attachments: Lotus (21 lines)
Larry Kilgallen said:
> Whereas I think of a high-integrity system as one designed and
constructed
> to have those qualities to make it work right all the time.

Alternatively, high-integrity software is designed and constructed so that
it *can be demonstrated that* it has the desired properties. (In many
situations you have to get the software past a certification authority well
before any user gets to it).

This might seem nit-picking, but it's an important distinction. Correct
software can, obviously, be written in any language but Ada is particularly
valued because it supports the use of a variety of V&V techniques to build
confidence in the correctness of the software.

For more on this, have a look at the Guidance report produced by the Annex
H Rapporteur Group (a draft version was published in Ada Letters earlier
this year).

Phil Thornley

ATOM RSS1 RSS2