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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7df278df170d566b
X-Google-Attributes: gid103376,public
From: Ken Garlington <garlingtonke@lfwc.lockheed.com>
Subject: Re: ACVC and Compiler Quality (was: Ada Core Technologies blah blah
 blah)
Date: 1996/04/15
Message-ID: <31729E02.2021@lfwc.lockheed.com>#1/1
X-Deja-AN: 147696636
references: <316B9234.35AA@lfwc.lockheed.com> <4kji2p$spp@news.sei.cmu.edu>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Tactical Aircraft Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.01 (Macintosh; I; 68K)
Date: 1996-04-15T00:00:00+00:00
List-Id: <comp.lang.ada>

John Goodenough wrote:
> 
> The second is a "lessons-learned" paper and
> among other things, discusses the reason for taking a "usage-oriented"
> approach to the Ada 95 tests.  Unfortunately, this reference is not widely
> available and I don't have an online copy available.

Given this, could you perhaps briefly summarize how this paper addresses
the two questions I've posed?

1. How could the scope of the ACVC testing be modified to improve compiler
quality across all vendors?

   Perhaps this paper attempts to measure the impact of ACVC testing on
   the quality of Ada compilers? Defines the expected increase in quality
   from going to "usage-oriented" tests?

2. What steps could be taken outside the ACVC to improve compiler quality
across all vendors?

>     Goodenough, J. B. Ada compiler validation: an example of software testing
>     theory and practice.  In: A.N. Haberman and U. Montinari (Eds.), System
>     Development and Ada, Proceedings of the CRAI Workshop on Software Factories
>     and Ada, Capri Italy, May 26 - 30, 1986.  Lecture Notes in Computer Science
>     No. 275.  New York, Springer-Verlag 1986, pps. 195 - 232
> 
> John B. Goodenough                                      Goodenough@sei.cmu.edu
> Software Engineering Institute                          412-268-6391