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.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,850aac543a8c1492,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1993-03-12 08:02:55 PST
Newsgroups: comp.lang.ada
Path: sparky!uunet!cs.utexas.edu!mars.tsd.arlut.utexas.edu!bemont
From: bemont@tsd.arlut.utexas.edu (Les Bemont)
Subject: relaible ada development systems
Message-ID: <1993Mar12.154601.1931@titan.tsd.arlut.utexas.edu>
Sender: usenet@titan.tsd.arlut.utexas.edu
Nntp-Posting-Host: griffin
Organization: Applied Research Laboratories, University of Texas at Austin
Date: Fri, 12 Mar 1993 15:46:01 GMT
Date: 1993-03-12T15:46:01+00:00
List-Id: <comp.lang.ada>

Newsgroups: comp.lang.ada
Subject: reliable Ada development systems
Summary: 
Followup-To: 
Distribution: world
Organization: Applied Research Laboratories, University of Texas at Austin
Keywords: 

** I am posting this for a colleague.  Please e-mail Steve, not me. **


We have been involved in developing several Ada systems (some large)
on Suns and PCs with UNIX, and are very interested in finding a highly
reliable Ada development system.  With Verdix we find ourselves
pushing the limits of the development system -- breaking
features/tools.  We understand that Alsys is no better.  We would
greatly appreciate input on the following topics,

1) Surveys of Ada development system reliability for large systems.

2) Candidate "high reliability" development systems -- not limited to
US companies.

3) Descriptions of how you deal with unreliable/breakable development
tools (what price do you pay).  What is the ratio of your software
development staff to your build/configuration management/software
tools staff?  Is your development staff restricted to using only
certain (reliable) features of the development system?  Do you use
in-house tools or third party tools?  Do you consult with tool vendors
often?  (Weekly?)  Do you use formal software development procedures
to minimize risks due to develop tool reliability issues.  Do you
cultivate your own in-house "experts"?... or don't you have these problems?

Again, pertinent input is greatly appreciated.

Our objective is not to flame Verdix or Alsys.  (I won't respond
to flames).

Steve Glicker
Applied Research Laboratories
The University of Texas at Austin
(steve@titan.tsd.arlut.utexas.edu)