Ada INFORMATION CLEARINGHOUSE NEWSLETTER
Vol VIII, No. 1 -- March 1990
The
Dr.
MAJ
Maj
Ada Joint Program Office
John P. Solomond, Director
Edward Liebhardt, Army Deputy Director
Dirk Rogers, Air Force Deputy Director
The Ada Information Clearinghouse (AdaIC) Newsletter is published
quarterly. Comments concerning this publication should be sent to: Ada
Information Clearinghouse, c/o IIT Research Institute, 4600 Forbes
Boulevard, Lanham, MD 20706-4312; or call 703/685-1477. The AdaIC is
operated by IIR Research Institute for the Ada Joint Program Office
(AJPO).
Letter from the Director, Ada Joint Program Office
==Tri-Service Working Groups: In the last issue, I mentioned that we have
begun work on establishing several Tri-Service working groups to examine
critical technology areas. I've been very pleased by the enthusiastic
response of the Ada Executive Officials, and at my next meeting with them
I
hope to receive the first nominations for membership in the working
groups.
==Ada 9X: By last fall's deadline for open submissions, the Ada 9X
Project
received 774 requests for revision of Ada. In August, the Project
published a Revision Request Report containing the first 150 of these
requests. In January, the balance of the requests were collected into a
supplemental volume.
Copies of the new volume can be ordered through the AdaIC. If you ordered
the first volume through the AdaIC, you will receive the supplement
automatically. There is no need to order them separately. In any event,
there is no charge for these reports.
==Question of Freezing the ACVC: The current version of the Ada Compiler
Validation Capability is 1.11 -- which became the current version on Dec.
1, 1989, and will remain in place until June 1, 1991, when it will be
succeeded by version 1.12. Under current procedures, v. 1.12 would
similarly have a lifespan of 18 months. As Ada matures, however, we have
to consider whether it is necessary to update and replace the validation
test suite. This question is going to be studied by the Ada Validation
Organization, the ACVC Maintenance Organization, and the managers of the
Ada Validation Facilities.
==PCIS -- CAIS-A and PCTE+ Convergence: I've mentioned before the work
being
done towards a convergence of the Common APSE Interface Set (CAIS) and
the
Portable Common Tools Environment (PCTE). CAIS-A here in the U.S. and
PCTE+ in Europe both provide tool-portability layers that allow the
development of software tools that can be employed by all Ada users. As
has been indicated in other articles, the joint effort will be called the
Portable Common Interface Set (PCIS -- pronounced like "pieces").
On Feb. 14-15, I took part in a third meeting on the PCIS program with
representatives of the Independent European Programme Group - Technical
Area 13 (IEPG-TA13) -- this time, with the participation of the chairman
of
the Special Working Group on Ada Programming Environments (SWG on APSE).
This group was formed by ten nations under a Memorandum of Understanding
that agrees to a collaborative effort in the area of Project Support
Environments.
At the February meeting, we reaffirmed the contents of the two previous
public statements (Jan. 6 and Aug. 23, 1989). In particular, the
following agreements were reached:
1. The SWG on APSE Memorandum of Understanding is the recognized
mechanism
for conducting the Definition Phase of the PCIS program. IEPG-TA13 and
the
AJPO will contribute all available information that will enhance the
success of the PCIS program.
2. The Definition Phase is the initial phase in a complete program whose
objectives are to establish the PCIS as a single, internationally
recognized Public Tool Interface, and to encourage its use. The SWG on
APSE will investigate appropriate mechanisms for achieving these
remaining
phases.
3. Efforts will be made to encourage civil organizations to become
actively involved in the PCIS program.
In This Issue
CAIS-A Update 2
DoD Software Master Plan 2
Space at Computer-Security Conference 3
NTIS Has Latest Version of Ada/Ed 3
TRI-Ada Call for Papers 4
BBS Previews Validation Tests 5
ALS/N Quarterly Review 5
TQM Comes to Ada Support 6
Videotape Update 6
Dear AVO 7
Evaluation & Validation of APSEs 8
Ada 9X Report 9
ARTEWG Meeting -- Getting into Technical Details of RTEs 11
AdaJUG Conference Highlights Major Issues 13
Behind the Ada 9X Revision Process -- Chris Anderson Interview 17
Validated Ada Compilers List 19
Ada Calendar 39
CAIS-A Update
Revision A of the Common Ada Programming Support Environment (APSE)
Interface Set (CAIS) was approved as a DoD standard on October 3, 1989;
it
is now DOD-STD-1838A. Although it was not yet on the ordering system at
presstime, the CAIS-A document should be available shortly through
Military
Specifications and Standards.
(This used to be the Naval Publications and Forms Center. Note the new
address, below.)
The CAIS (originally released in 1986) was designed to provide a
tool-portability layer that would be implementable on a variety of
computer
hardware and operating-system configurations.
With DOD-STD-1838A -- CAIS-A -- the basic functionality of the CAIS has
been expanded to include such features as typing, distribution,
transaction
support, expanded input/output, resource control, and security.
There is no charge for the document, but if you are not from a Federal
activity, you may be asked to submit your order on a letterhead. You may
wish to check beforehand to make sure the document has become available.
CAIS-A -- DOD-STD-1838A
Order from:
Military Specification and Standards
Building 4, Section D
700 Robbins Avenue
Philadelphia, PA 19111-5094
215/697-2667
Corrections
We received a couple of corrections to the article "Service and DoD
Facilities Offer Variety of Ada Courses", in the December 1989 issue.
Under Navy & Marine
School, the correct
course is conducted
AFB,
Miss.; and students
experience.
Corps courses, in the entry on the Computer Sciences
course title is "Ada Applications Programmer"; the
for the Marine Corps by 3390 TCHTG/TIMKPP, Keesler
should have high-order language (HOL) programming
Under Air Force courses, there are corrections in the entry for 3390
Technical Training Group. The fundamentals course is a 9-day course,
taught at Keesler and on the road; the schedule is based on requirements;
students should have a fundamental knowledge of programming concepts.
The orientation course is a two-day course, taught on the road only;
there
are no prerequisites.
If there are any other corrections or updates to Service and DoD course
offerings, please let us know.
Contact:
Ada Information Clearinghouse
c/o IIT Research Institute
4600 Forbes Boulevard
Lanham, MD 20706-4324
703/685-1477.
Public Forum on DoD Software Master Plan
The Department of Defense (DoD) is developing a Software Master Plan, a
draft of which will be available for review and comment by the public in
late February 1990. A forum will be held April 3-5, 1990, to obtain
public
comments.
The Software Master Plan will address the challenges faced by the DoD
because of the escalating costs of software and software development in
our
Defense systems. The Plan is being developed through the collaborative
efforts of numerous offices and organizations within the DoD, under the
auspices of the Defense Acquisition Board's Science and Technology
Committee.
To help defray the costs of conducting the public forum, a registration
fee
of $30 is being charged to all attendees. Participants are encouraged to
preregister by March 21, 1990; attendance at the public forum will be
limited to the first 500 people registered.
==The Plan
The draft Software Master Plan is divided into four major sections:
1. Software acquisition and lifecycle management.
2. DoD software policies.
3. Personnel.
4. The software-technology base and software-technology transition.
The plan identifies problems arising in each of the sections, establishes
goals, and suggests how to accomplish those goals.
==The public forum
The public forum will be held at the Ramada Hotel -- Tysons Corner, at
7801
Leesburg Pike, in Falls Church, Va.
The forum will consist of: (1) a general session in which DoD personnel
will present the various sections of the plan; (2) smaller breakout
sessions running in parallel for detailed discussion and comment on the
four major sections of the plan; and (3) a closing general session to
report on the results of the breakout group sessions.
The tentative agenda is as follows:
Tuesday, April 3
8:00 am -- Registration
9:00 am -- Opening Remarks by Dr. George Millburn, Deputy Director of
Defense Research and Engineering for Research and Advanced Technology
9:30 am -- Presentation and Discussion of the DoD Software Master Plan
12:00 pm -- Lunch (not provided)
1:30 pm -- Presentation and Discussion of the DoD Software Master Plan
(cont'd)
4:30 pm -- Adjourn
Wednesday, April 4
9:00 am -- Parallel Breakout Sessions
1. Acquisition and Life Cycle Management
2. Policy
3. Personnel
4. Technology Base and Transition
12:00 pm -- Lunch (not provided)
1:30 pm -- Parallel Breakout Sessions (cont'd)
Thursday, April 5
9:00 am -- Reports by Breakout Session Chairs
12:00 pm -- Adjourn
==For further information
To obtain a copy of the draft DoD Software Master Plan or a registration
form for the DoD Software Master Plan Public Forum, interested parties
should contact:
Ms. Karen Marinoff
DoD Software Master Plan Public Forum
Institute for Defense Analyses/CSED
1801 North Beauregard Street
Alexandria, VA 22311
703/824-5506
FAX: 703/820-9680
Space Available at Computer-Security Workshop
IIT Research Institute and the University of Houston - Clear Lake are
sponsoring a workshop on "Issues of Integrity & Security in an Ada
Runtime
Environment". As reported in the last issue, the workshop will be held
April 3-5, 1990, in Orlando, Fla.
Coordinated by the Ada Joint Program (AJPO), this workshop is aimed at
those with a background in either computer security or Ada runtime
environments. It will serve as a forum for the exchange of ideas between
these areas.
Invitations are currently being sent out based on acceptance of position
papers, and the organizers expect some space to be available for others
to
attend.
For further information, contact:
George Buchanan
Integrity & Security in Ada
IIT Research Institute
4600 Forbes Boulevard
Lanham, MD 20706
NTIS Offers Latest Version of Ada/Ed (NYU)
The National Technical Information Service (U.S. Department of Commerce)
has announced the availability of version 1.10 of Ada/Ed (NYU).
This is the latest version of the NYU Translator/Interpreter -- the first
product to be receive a validation certificate as conforming to the Ada
standard. The original version of Ada/Ed (NYU) was developed by the
Courant Institute at New York University under the sponsorship of the
U.S.
Army Communications-Electronics Command, Fort Monmouth, N.J., and
received
its validation in April 1983.
The latest version (sponsored by Wright-Patterson AFB) was validated
under
version 1.10 of the Ada Compiler Validation Capability (ACVC) test suite.
Ada/Ed is written in SETL -- a high-level programming language developed
at
NYU, whose constructs are based on set theory. While quite slow, Ada/Ed
is
of interest to language implementers and designers. Ada/Ed is a semantic
model of Ada, and describes Ada's executable aspects by way of an
interpreter for an intermediate representation -- Ada Intermediate
Source.
In effect, Ada/Ed can serve as a definition of the Ada language itself.
==Commands, etc.
The translation process involves several steps. Initially the Ada source
is analyzed, and an aisfile (Ada Intermediate Source) is created. One or
more aisfiles are then bound, creating an aixfile (Ada Intermediate
eXecutable file) -- which can then be executed. Unless explicitly
requested, intermediate files are not retained following a compilation
(or
binding).
The Ada/Ed system includes the following commands:
The ADA command compiles and executes an Ada file; it is assumed that the
complete program and all referenced units are in that file. It requires
use of the adafile (or a) option. No library specification is necessary.
lADAC compiles an Ada source file and places it in a program library.
lADAB binds a library with the specified (or implied) main unit to form
an
executable file (aixfile). It requires specification of both libfile and
aixfile.
ADACB compiles an Ada source into a library, and then binds the library
to
create an executable aixfile. It requires specification of a source file
and aixfile. In order for the libfile to be updated, library and aisfile
specifications are necessary.
ADAXB exeutes the specified bound aixfile.
ADAXL binds the specified library and executes the resulting bound code
file (aixfile).
Note: All desired file options must be explicitly specified, and may
occur
in any order.
Information and ordering
For substantive questions, the point of contact at NYU is:
Bernard Banner
212/998-3493.
The software is available for both VAX/VMX (backup format) and SUN/UNIX
(TAR format) computer environments.
Ada/Ed costs $890; at press time, its accession number was not yet
available. For ordering information, please telephone NTIS's Federal
Computer Products Center: 703/487-4763.
NTIS
U.S. Commerce Dept.
5285 Port Royal Road
Springfield, VA 22161
TRI-Ada '90 Issues Call for Papers
The third annual TRI-Ada conference will be held this year in Baltimore.
Sponsored by the Association of Computing Machinery's Special Interest
Group on Ada (ACM SIGAda) and the Baltimore SIGAda, it will be held
December 3-7, 1990, at the Baltimore Convention Center.
The conference organizers are seeking papers from all sectors of the Ada
community: industry, academia, and government. They hope to present a
balanced program of panels, tutorials, and refereed papers about Ada -ones that address management as well as technical issues, theory as well
as
applications, and commercial as well as defense sector. They particularly
encourage papers that contain comparative statistics of Ada's impact on
projects, that describe Ada's application in the commercial sector, or
that
provide new insights into paradigms of software engineering with Ada. For
further information on desired topics, please contact the Program Chair,
Dr. Erhard Ploedereder.
Submissions are due by May 21, 1990.
Abstracts and Papers
Authors of papers should plan to submit an extended abstract that is
sufficiently detailed, or alternatively submit a full paper.
Papers must not have been previously published or submitted for
publication
elsewhere, unless substantially revised. The recommended length for an
extended abstract is 1,200 to 2,400 words (three to six pages).
Full papers should not exceed 15 pages.
Submission of an abstract should indicate a commitment by the author and
the author's organization to present a paper at the conference, and to
convey authority for publication in the TRI-Ada '90 Conference
Proceedings
in accordance with ACM copyright policies.
==Project Summaries
Tri-Ada '90 will offer space in a conference track for unrefereed status
and experience reports of on-going large Ada projects. Submission of a
paper is not expected. However, for program planning purposes, a short
description (one to three pages) of the project scope and status is
required. Presentation time will be allocated competitively.
==Tutorials
The tutorial committee is looking for volunteers to help others
understand
new concepts. Proposals should include a description of the materials to
be presented, the level of the course, the course outline and estimates
of
time allocation.
Proposals for tutorials should be directed to the tutorial Co-Chair,
Steve
Grimaldi.
Steve Grimaldi
Booz, Allen & Hamilton
Airport Square Eight, Suite 150
891 Elkridge Landing Road
Linthicum, MD 21090
301/850-5006
301/850-4592
grim@terminus.umd.edu
==Panels
Proposals for panels should include a short topic statement, rationale of
its importance, and a prospective list of panelists.
Submit six copies of all abstracts, full papers, project summaries, and
panel proposals to the Program Chair, Dr. Erhard Ploedereder.
Dr. Erhard Ploedereder
Tartan Laboratories
300 Oxford Drive
Monroeville, PA 15146
412/856-3600
412/856-3636
ploedere@tartan.com
ploedere@ajpo.sei.cmu.edu
Deadlines:
May 21, 1990 Submissions due
July 7, 1990 Acceptance-notification date
Sept. 10, 1990 Camera-ready copy due
Dec. 3-7, 1990 TRI-Ada '90
Bulletin Board to Preview Validation Tests
The development of the next version of the Ada Compiler Validation
Capability (ACVC) is of particular importance to vendors of validated Ada
compilers. But in a larger sense, the quality of the validation test
suite
affects the entire Ada community. And much of the success of the
validation effort to date has been attributable to the interest and input
of members of the community at large.
To increase the visibility of planned changes to the ACVC during the test
development period, the ACVC Maintenance Organization (AMO) has
implemented
an ACVC Test Delivery System. This is an interactive program and database
on the AMO's VAX 8650, for public access and review of all proposed ACVC
1.12 tests as the AMO produces them. This system allows any interested
person to obtain a source listing of proposed tests from any or all
deliveries and to submit comments or recommendations to the AMO. The
user's comments are sent to the AMO, but are invisible to other general
users of the system. This ensures the confidentiality of comments.
The system has immediate benefits. It provides compiler implementers an
opportunity to comment on proposed changes and to prepare for an updated
version long before the final release. Furthermore, a wider review by
language experts and compiler implementers increases the probability that
errors will be detected much earlier in the ACVC software lifecycle, thus
reducing software lifecycle costs.
==Accessing the Test Delivery System
You can gain access to the AMO's VAX 8650 in either of two ways.
One way to gain access is connecting to the AMO machine through the
Defense
Data Network (DDN) via TELNET. You can type "TELNET jalcf.wpafb.af.mil".
Alternatively, if the host table does not contain that name, you can use
"TELNET 26.13.0.124" followed by a carriage return at the system prompt.
Another way to gain access is dialing either 513/476-7351 or 513/476-7327
through a modem. This will connect you to the IMS switch. A menu of
machines will be displayed. At the prompt, you should choose SEWS Ada
(number 5).
Once you have gained access to the AMO machine, you should type
"Adatests" at the username prompt. Once done, you will fall immediately
into an interactive menu-driven program. You will be asked to provide a
password: just hit carriage return. You will then have access to source
code from any or all deliveries. Every user will be given the opportunity
to make comments to the AMO and to download a report on the interactive
session to his system.
The Test Delivery System allows primarily three options:
1. to generate information about specific tests (for this, the user must
specify the name of the test desired);
2. to allow the user to enter comments about tests, using the VAX EDT
editor; and
3. to generate information about all of the tests delivered at a specific
time.
For further information
Any questions concerning the use of the AMO Test Delivery System should
be
directed to:
Mr. Thomas Stripe
Validation Engineer
Wright-Patterson AFB, OH 45433-6503
USA
513/255-4472
e-mail: <stripet@jalcf.wpafb.af.mil>
ALS/N Review Hears Reports
User Meetings to Go on the Road
Lessons from Ada projects and technical user comments were the focus of
the
regular quarterly public review of the Navy's compiler project -- the Ada
Language System/Navy (ALS/N). Another topic that came up was the
possibility that future ALS/N Users Group meetings would be held outside
the Washington, D.C., area.
The meeting was held on January 19, 1990, in Arlington, Va., in tandem
with
the ALS/N Users' Meeting. The next review is scheduled for April 26, also
in Arlington.
The Public Review session in the morning heard a report of ALS/N
technical
users on a "Prioritized Top Ten ALS/N Required Improvements". The
afternoon session was taken up by a discussion of four Navy embedded-Ada
projects.
==The Technical Users report
Acting as a go-between between users and developers, Anna Deeds, of PMS
4123G, presented the Technical Users' report. The top priority was to
ensure that all the requirements of the ALS/N System Specification were
met
for all specified configurations of the AN/UYK-43, AN/UYK-44, and AN/AYK14
computers. (For instance, the report cited the need for a symbolic
debugger and performance-measurement aids.)
The second priority was to modify pre-release procedures to improve
quality, and the third called for improvements to documentation. (For
example, the absence of an index was noted.)
Other points ranged from a call for improved processing of certain
reports
and more exchange of technical information between users, developers, and
testers, to the need for a means to reduce time and size requirements of
application initialization.
==Comments on the report
In his comments on the report, Bill Wilder, ALS/N Acquisition Manager,
discussed his agreements and differences with various points. He
indicated, for instance, that the first point, on meeting requirements,
was
not in debate -- but commented that the effect of funding limits and
interruptions had to be taken into account.
Regarding point two, on modifying pre-release procedures, he indicated
that
change was already on the way. New versions will be released annually
rather than every six months, and this should allow developers to make
each
version stronger. And on point three, staff who were present from Control
Data subcontractor TRW indicated that an index could be done quite
quickly
so long as it were limited to a word search.
==Project descriptions
In the afternoon, Roger Baker from Verdix presented a discussion of four
Navy embedded-Ada projects. They were the Navy's Sea Lance Missile (a
Boeing project); the BSY-2 fire-control system (General Electric); fire
control, similar to the BSY-2, for the Royal Australian Navy's new
submarine (Rockwell Australia); and onboard location and tracking systems
for the P-3 aircraft's Update-IV (Boeing).
The projects ranged in size from 80 thousand lines of code for the Sea
Lance (programmed 100 percent in Ada) to 2 million LOC for the BSY-2. Mr.
Baker observed that extremely large, realistic programs stress the
toolset
in unforeseen ways. Ada definitely works, he said, but new, large
programs
will have "pioneer" problems.
==Going on the road
Cathy Ruiz, ALS/N Users Group chair, announced that it was hoped that
future users meetings could be held at locations in the field. The first
such meeting will be held in Virginia Beach, Va., Feb. 27-Mar. 1, 1990.
This will be hosted by Fleet Combat Direction Systems Support Activity
(FCDSSA), Dam Neck, Va. (Another meeting is now scheduled to be held at
Naval Underwater Systems Command in Newport, R.I., the week of May 21.)
Anyone interested in attending or speaking at the Virginia Beach meeting
should contact Guy Taylor at 804/433-7230, or Maura Pineda at 804/4337290.
Total Quality Management in Ada Support -- You're Part of It
Total Quality Management (TQM) is a concept that is making waves in
American industry -- and it's coming to the Ada Information
Clearinghouse.
TQM has gained attention as one of the purported keys in Japan's
industrial
growth. But it is based on the works of such people as W. Edwards Deming,
and has "Made in the USA" stamped all over it.
==It's not new
TQM has been described as a combination of old-fashioned craftsmanship
and
modern statistical methods. One of its approaches is to track a
production
process and spot any events that are out of the ordinary -- whether good
or
bad. Finding out why they happened will improve the process and the
product.
Another element of TQM is to see that there are a variety of "products"
and "customers" within the production process. For instance, secretaries
and floor workers are frequently the customers of a manager. If the
manager doesn't deliver an adequate product to these customers, they
can't
deliver adequate products to their customers.
In both its origins and its usual applications, TQM is generally regarded
as an industrial tool. It may seem odd that it would be brought to an
information activity like the AdaIC. But the AdaIC still produces things
-- newsletters, flyers, etc. And TQM can help in those aspects of our
job.
One of the challenges is that information workers may be less apt to
think
in quantitative terms. (How long does it take to answer the average
telephone request for information?) But awareness of quantitative aspects
can open up areas for improvement that a simply qualitative approach
might
overlook. (Should we be taking more time to answer questions fully? Or
should we learn to be more succinct?)
Other aspects of TQM can help in the substantive areas of the AdaIC
effort.
One of the long-time rules of business is that the customer is always
right. In TQM terms, one implication of this is that it doesn't matter
whether a product is within specifications. If it doesn't meet the needs
and expectations of the customer, it should be changed.
This means that input from the ultimate consumer is an essential part of
TQM. So -- how do you view our products?
==Any comments?
For instance, we've changed the typeface we use in this newsletter. Among
other things, it lets us fit in the same amount of text at about the same
readability, but in less space than our previous typeface. In your view,
is the change an improvement? Or a step backward?
Either way, let us know -- the typeface is just one step in redesigning
the
newsletter, and your comments will help.
And don't limit yourself to the newsletter. It will help us considerably
if you tell us whenever you think our services or our products have been
particularly good or bad -- or if you think there's a service we ought to
be providing but aren't.
Send your comments to:
Ann Eustice
Ada Information Clearinghouse
c/o IIT Research Institute
4600 Forbes Boulevard
Lanham, MD 20706-4324 703/685-1477
Videotape Update
In the September issue, we reported on a 19-tape series of Ada training
videotapes and gave a distribution list of installations that would have
them. In the December issue, we reported that we had been given an
incorrect distribution list, and that the tapes were being put through
the
National Audiovisual Center for public sale and distribution.
At press time, the tapes have not yet been finally cleared for public
release. As we noted in the December update, all those who have contacted
us about the tapes will be notified as soon as we have the final word.
If you would like to be added to this list, contact:
John Walker
Ada Information Clearinghouse
c/o IIT Research Institute
4600 Forbes Boulevard
Lanham, MD 20706-4324 703/685-1477
Dear AVO
The AJPO, the Ada Validation Organization (AVO), and the Ada Validation
Facilities (AVFs) receive and answer many questions concerning procedures
and guidelines for compiler implementation. In the interest of promoting
a
better understanding of how the compiler validation process works, the
AdaIC publishes the answers as a regular column. Ifyou have questions or
comments, please send them to the AdaIC. (Attn: Michele Kee.)
Question: What are the current rules regarding "automatic extension" of
validation certificates? (These are marked with the label "pending" in
the Validated Compiler List.)
In October 1988, the Ada Joint Program Office announced changes to the
Ada
validation process. The life of each version of the Ada Compiler
Validation Capability (ACVC) was extended by six months (to 18 months);
also, certificates were given a common expiration date. Every vendor's
certificate will expire on the same day -- one year after expiration of
the
version of the validation test suite used in testing.
The Ada Compiler Validation Procedures 2.0 reflects these rules; however,
unlike the earlier Procedures & Guidelines 1.1, there is no provision for
granting "an automatic extension [of the certificate or validated
status]" if a vendor is in the process of revalidating the implementation
when a certificate expires. Are there still extensions? Answer: The
current rules, as described by Ada Compiler Validation Procedures 2.0, do
not allow a "pending" validated status: all certificates that were issued
for validations under ACVC 1.10 will expire on 1 December 1990, without
exception -- the rule applies uniformly to every implementation.
For validations that were performed under ACVC 1.9, extensions were
granted; at this time, few "pending" compilers remain. The last of ACVC
1.10 validations are now being completed, and the certificates will soon
be
issued. The label "pending" will not again appear in the Validated
Compilers List.
The purpose of the old rules in allowing "extensions" was to ensure that
the normal processing of validation information did not coincidentally
result in a lapse of validated status for a vendor's compiler for some
configuration.
But also under the old rules, certificates expired one year after the
date
of issue (normally within a month of validation). Under such
certificate-expiration rules, vendors always "revalidated" compilers near
the time when their certificates expired. To do so earlier would mean
that
their compilers were in some sense covered by two certificates; also, the
new certificate would expire sooner than if revalidation were delayed.
(This is similar to the vehicle inspection policy in states where
inspections are required annually: people have no incentive and even have
a
disincentive to get a vehicle inspected before the expiration month!)
Eventually, the vendors' tendency to put things off became a problem.
There were too many cases where "revalidations" occurred months after a
related certificate expired. The old rule (P&G 1.1, section 4.2) stated
that revalidations must be performed "in a timely manner", but this rule
proved too subjective to enforce. Thus, in revising the P&G 1.1, there
was
strong motivation to eliminate any sort of continual "extension"
adjudication and labeling VCL entries "pending"!
The rules in Ada Compiler Validation Procedures 2.0 intentionally do not
treat any validation as a "revalidation." All validations are regarded
as being unique; thus, they are unaffected by, and have no effect on, any
other validation.
Of course, in practice, vendors are still revalidating maintained
versions
of validated compilers. But with a common expiration date for
certificates, the "revalidation" is free to occur whenever the vendor is
ready -- rather than being coerced by validation rules to occur near a
certificate's expiration date. The certificate expiration date is
determined solely by the ACVC version; therefore, any compiler that is
validated with a particular version will have the same expiration date as
all others that use the same version (which is both the earliest and
latest
date possible!).
Question: I notice variations in the descriptions of hardware
configurations on the Validated Compiler List. Some compilers seem to be
validated for only one computer system while other compilers are
validated
for a "family" of computer systems. Why do these variations exist?
Answer: Most of these variations exist because of the distinction between
a
base and a derived compiler -- which was discussed in the December "Dear
AVO" column.
When an Ada compiler is validated by an Ada Validation Facility (AVF),
the
certificate issued for it specifies the computer system used for the
validation testing. This is the base compiler, and the VCL entry for it
is
taken from the certificate.
There is no need for the AVF to validate the compiler for all the members
of a family of computer systems offered by the same manufacturer -Digital
VAX/VMS computer systems, for example. This is because there is a
registration process that provides a mechanism for deriving validated
status for the compiler when installed on other models within the family
of
computer systems.
For derived compilers, vendors must complete a registration request and
submit it with a Declaration of Conformance for the Ada implementations
that are derivable from the Ada implementation that has a Validation
Certificate. (See December's column for the conditions that must be met
here.) VCL entries for these registered compilers are labeled *Derived
and
give the certificate number for the Ada implementation from which
validated
status was derived.
To request registration for "all models" or a "family" of computer
systems, a compiler vendor must supply supporting technical information
with the registration request. There is some risk to a compiler vendor
who
has not established the conformity of the compiler on all models by
testing
under the current ACVC validation test suite. There is also a risk that a
hardware manufacturer will introduce a new model later with some
significant change in its internal architecture.
To reduce their risk of a user challenge, compiler vendors are advised to
list only the models known to be architecturally equivalent at the time
of
registration, and to perform ACVC testing themselves before requesting
registration.
Thus, VCL entries for base compilers tested by an AVF will show a
specific
computer system, and *Derived entries may list several computer system
models, a series, or a family.
Other variations in the description of computer systems stem from
differences among hardware manufacturers and suppliers in part-naming and
-numbering conventions. The AVFs have encountered difficulty in obtaining
a complete and accurate description of the computer systems used to
conduct
validation testing. We are all trying to obtain uniformly complete and
accurate information for the validated compiler listing.
*********
If you have any comments about the validation test suite, please send
them
to the AVO so that future releases can be improved.
Ms. Audrey Hook
Institute for Defense Analyses
1801 North Beauregard Street
Alexandria, VA 22311-1772
Evaluation and Validation of
Ada Programming Support Environments
-- An Introduction
Raymond Szymanski
As a programming language, Ada's strengths are in such areas as
facilitating sound software engineering. But for Ada to be successful in
actual practice, the bare language itself must function within a
framework
of support tools -- an editor, debugger, library routines, etc.
These are part of an Ada Programming Support Environment (APSE), and the
strength of such support tools is critical to the project on which they
are
used.
To look at this area, the Ada Joint Program Office (AJPO) sponsors the
Evaluation and Validation (E&V) Task, which is under my direction at
Wright
Research and Development Center, Wright Patterson Air Force Base, Ohio.
==The E&V Task
The E&V Task provides a focal point for addressing APSE assessment needs,
and performs work in such areas as:
1. identifying and defining specific E&V technology requirements;
2. developing selected elements of the required technology;
3. encouraging others to develop E&V elements; and
4. collecting and disseminating information describing existing elements.
This information is made available to DoD components, other government
agencies, industry, and academia.
The current development status of each E&V Task technology is summarized
below.
==The Ada Compiler Evaluation Capability (ACEC)
The ACEC is a suite of tests, scenarios, and support tools that enable
the
user to assess the performance and usability characteristics of an Ada
compilation system. The most recently completed version is ACEC 2.0; it
consists of:
1. 1300 performance tests;
2. a set of tests and scenarios to assess the utility of the compiler's
diagnostic message system, the Ada library system and the symbolic
debugger; and
3. support tools that facilitate the generation and analysis of test
results.
The ACEC is fully documented for the user through the ACEC User's Guide,
the ACEC Reader's Guide, and the ACEC Version Description Document.
ACEC Version 2.0 is distributed by the Data Analysis Center for Software
(DACS). Those interested in ordering the ACEC should contact DACS at
315/336-0937 and request the ACEC Ordering Information Package.
Plans are currently being developed for ACEC Version 3.0. Details of this
version will be published in a future edition of this newsletter.
==The E&V Reference System
The E&V Reference System consists of two companion documents: The E&V
Reference Manual, and the E&V Guidebook.
The purpose of the E&V Reference Manual is to provide information that
will
help users to:
1. gain an overall understanding of APSEs and approaches to their
assessment;
2. find useful reference information (e.g., definitions) about specific
elements and relationships between elements; and
3. find criteria and metrics for assessing tools and APSEs, and find
techniques for performing such assessments.
The purpose of the E&V Guidebook is to provide information that will help
users to assess APSEs and APSE components. It also:
1. assists in the selection of E&V procedures, the interpretation of
results, and integration of analysis and results;
2. describes E&V procedures and techniques developed by the E&V Task; and
3. assists in the location of E&V procedures and techniques developed
outside the E&V Task.
The E&V Reference Manual Version 2.0 and the E&V Guidebook Version 2.0
are
available from the National Technical Information Center (NTIS -- which
sells to the general public) and from the Defense Technical Information
Service (DTIC -- for the military, Federal government, and defense
contractors who are registered users of DTIC). The accession number for
the Manual is AD-A214 167; for the Guidebook, it is AD-A214 166.
NTIS
DTIC
U.S. Commerce Dept.
Cameron Station
5285 Port Royal Road
Alexandria, VA 22314
Springfield, VA 22161
703/274-7633
703/487-4650
AV: 284-7633
These documents are also available electronically on the Ada Information
Clearinghouse Bulletin Board at 202/694-0215 and 301/459-3865. (See page
10 for information on accessing this bulletin board.)
==CAIS Implementation Validation Capability (CIVC)
CIVC is a validation capability for implementations of the Common APSE
Interface Set (CAIS) Standard, DOD-STD-1838 -- which defines a set of
common interfaces to promote Ada tool transportability and
interoperability.
Version 1.0 of the CIVC has been completed, and plans are being
formulated
to distribute it through the DACS. The initial release will include over
200 individual test cases, an integrated and versatile test manager, and
a
hypertext product to provide traceability between the 1838 standard, the
taxonomy, and the actual test cases.
Future work under this contract activity will focus on development of
CIVC-A -- a validation capability for CAIS-A (MIL-STD-1838A.) A kick-off
meeting fo CIVC-A was held Feb. 8 at the Navy's Fleet Combat Directions
Systems Support Activity (FCDSSA), in San Diego, Calif. CIVC-A will reuse
tests from the CIVC suite that prove to be applicable top the CAIS-A
standard. Additionally, much of the support technology developed for CIVC
will be enhanced and reused in CIVC-A.
==For further information
For information on E&V products, contact:
Raymond Szymanski
WRDC/AAAF-3
Wright Patterson AFB, OH 45433-6543
513/255-3947
MILNET/Arpanet: szymansk@ajpo.sei.cmu.edu.
Ada 9X REPORT
REQUIREMENTS PROCESS
We are deeply involved in the requirements process -- having received 774
Revision Requests received during the year of open submissions, plus
numerous comments from other sources.
The Requirements Team is developing revision issues -- which will
represent
aggregates of comments submitted. Following review and comment by the Ada
9X Distinguished Reviewers, revision issues will be released to the Ada
community for comment. The final requirements for the revision will be
developed from these revision issues.
A few example revision issues include: more user control of task
scheduling, improved mechanisms for shared variables,
extended-character-set capability, and improved exception-handling
facilities.
The first release of revision issues will be available to the public
mid-April on various Ada 9X bulletin boards (i.e., 1-800-Ada9X25,
301/495-8939, the AJPO host, and on EUROKOM). Subsequent revision issue
releases will occur in June and August. The final requirements developed
from the revision issues will be available in December.
As always, if you have any comments please send them directly to me at
the
Ada 9X Project Office.
REQUIREMENTS TEAM RESTRUCTURE
The type of work needed to complete the Requirements Phase successfully
has
changed in the past few months -- from collecting, analyzing, and
sorting,
to balancing language change versus stability. Because of this shift in
work, the Requirements Team membership has been restructured.
I would like to keep everyone and add more Team members, but budget
constraints do not allow me to do this. Therefore, Karl Nyberg and Paul
Baker will be leaving the Team a little early (March versus May). Robert
Dewar, Paul Hilfinger, and Olivier Roubine are being added.
I wish to emphasize that this restructure in no way implies a lack of
performance by any Team members. On the contrary, Karl and Paul have each
done an outstanding job. However, as the type of work changes, so must
the
make-up of the work force.
I would like to thank Karl and Paul for a job well done.
NOTEWORTHY DECISIONS
Based on numerous Revision Requests focusing on performance
real-time applications, it was decided to include this type
information
in the revised Standard. The issue of being able to predict
level of behavior has been reiterated many times by a large
the
Ada community.
behavior for
of
a certain
segment of
A second noteworthy decision concerns the formal definition of the
Standard. It is widely accepted that a formal static and dynamic
definition of Ada would not only serve the safety critical/trusted
systems
community, but also serve to validate any revision decisions.
Unfortunately, due to the magnitude and risk associated with such a task,
it has been decided not to put this activity on the critical path of the
Ada 9X revision; nor will such a definition be included in the revised
Standard.
However, other options are being explored for developing a formal
definition in a parallel effort.
"REACH OUT Ada" PROGRAM
In an attempt to learn first hand what types of revisions the Ada user
would like, the Project Office is planning several informal meetings with
key representatives of the Ada community.
The first such meeting occurred 25-26 January in Washington, D.C.
Twenty-two members of the safety-critical/trusted-systems user community
were invited to discuss their concerns with several Ada 9X Distinguished
Reviewers, Requirements Team members, and me. It was a very productive
meeting, from which several concrete recommendations resulted.
The underlying concern was the need for predictability. This translates
into many specific activities that we plan to pursue in the revision
effort.
Other similar meetings in different application domains are planned in
the
near future.
CALENDAR OF EVENTS
I am trying to discuss current Project activities with the Ada community
as
often as possible. The following represents a partial list of Ada 9X
Project presentations in 1990.
Electronics Industries Association (Jan.)
American Institute of Aeronautics and Astronautics (Jan.)
Ada Exhibition (Feb.)
AdaUK (Feb.)
Ada Technology Conference (Mar.)
Society of Automotive Engineers (Apr.)
International Requirements Review Workshop (Apr.)
NATO (May)
Ada Europe (June)
WADAS (June)
SIGAda (Aug.)
TRIAda (Dec.)
NEW ADA 9X DOCUMENTS
Hard copies of all 774 Revision Requests (plus more than 60 suggestions
gleaned from other sources) are now available from the Ada Information
Clearinghouse (703/685-1477). The document contains indices by topic,
author, request number, and organization.
A revised Ada 9X Project Plan is also available. The Plan is updated
yearly to reflect accurately the current status of the Project.
ADA TODAY
I am in a unique position to be able to talk to many of you regarding the
use of Ada worldwide. I am constantly amazed at the widespread successful
use of the language. Too often, I read only negative stories that I feel
do not really depict the current state of affairs. Therefore, from now on
in each "Report to the Public", I am going to include a few applications
of Ada that may serve as inspirations to us all.
Ada is currently mandated by the U.S. DoD and the West German Ministry of
Defense (MoD), and is an approved (and highly recommended) language by
the
MoD in France and the MoD in the U.K. Ada is being used in the following
systems and operations -- and this list is definitely not all-inclusive:
Rafale - French fighter aircraft
Base 2000 (C2) - Sweden, Denmark, Finland
Advance Tactical Fighter - U.S.
European Airbus
Racetrack Betting System - Australia
Nippon Telephone & Telegraph - Japan
Commercial Airlines - Boeing
NASA Space Station
Financial System (STANFINS) - U.S. Army
Shell Oil - U.S., Netherlands
OPEN DOOR POLICY
As always, please free to contact me if you have any concerns or comments
regarding the Ada 9X process. I can be reached by e-mail at
anderson@uv4.eglin.af.mil, by telephone at 904/882-8264, or by FAX at
904/
882-2095.
Ada Information Available through AdaIC Bulletin Board
The AdaIC Bulletin Board makes information on the Ada language available
to
the public. It announces current events and general activities, and
provides a current listing of validated Ada compilers. Access to the
bulletin board requires a computer terminal and modem.
Data: 202/694-0215 or 301/459-3865
Telecommunications setup information:
300/1200/2400 baud; No Parity; 8 data bits; 1 stop bit
If the line is busy, please try again. If the sytem does not respond
immediately, enter three carriage returns slowly. Once the system
responds, please follow the instructions as indicated. To read a file,
you
must download it to a local PC using straight ASCII or XMODEM protocol.
To
accomodate the greatest number of users, sessions are limited to 45
minutes.
ARTEWG Meeting -Getting into the Details of Ada Runtime Environments
Fred Maymir-Ducharme
The Ada Runtime Environments Working Group (ARTEWG) held its winter
meeting
in Fort Lauderdale, Fla., January 29 through February 2, 1990. The first
two days were devoted to general business and status reports, and the
meeting of its three subgroups (which address general tasks). The second
two days were primarily spent on meetings of task forces (which focus on
more specific issues). The last day was devoted to the new Security Task
Force.
==ExTRA presentation
Among the special presentations was a report by Dominique Chandesris from
a
French effort: ExTRA -- Extension Temps Riel Ada -- a proposed set of
extended Ada services for hard real-time applications. ExTRA is
comparable
to ARTEWG's Catalogue of Interface Features and Options for the Ada
Runtime
Environment (CIFO). (A report giving an "ExTRA-CIFO Comparison", by M.
J. Carolus, has been produced by Aerospatiale Aircraft Division,
A/DET/EI/CE B1401, 31060 Toulouse, France.)
ExTRA is funded by the French Armament Board/Electronic Direction
primarily
to aid the transition of avionics applications toward Ada. The ExTRA
representatives are seeking input on their proposed standards from ARTEWG
members. The intent is to proceed in parallel with CIFO and possibly
merge
into a single standard in the future.
==Ada 9X Update and Workplan
There was also an update from the Ada 9X Project, presented by Mike
Kamrad.
The majority of the Ada 9X effort this year is scheduled to address
Requirements -- language capabilities that should be present in Ada 9X.
The Requirement Analysis Team will take as input the set of over 800
Revision Requests received last year, the proceedings of the Requirements
Workshop held in Destin, Fla., last June, and the output from the Complex
Studies effort.
The Requirements Analysis team is expected to produce a definitive
Requirements and Justification Document by the end of 1990. This document
will consist of three sections. Section I will define the set of
requirements for Ada 9X -- these will be named "Revision Issues".
Section II will discuss the proposed requirements rejected and found out
of
scope, and state the reason for their rejection. Section III will
describe
policy decisions on how the Ada standard should be updated.
The current state of the Requirements Analysis will be discussed at
several
places this year, including the Requirements Workshop in Sweden (April),
the Washington Ada Symposium (June), and the SIGAda summer meeting ARTEWG
Meeting -- (August). Of particular interest to ARTEWG was the report that
Ada 9X will address implementation run-time characteristics.
ARTEWG has agreed to supply input to the Ada 9X effort by June.
Approximately 20 ARTEWG members volunteered to meet separately and help
address this request by identifying the set of Revision Requests
associated
with ARTEWG issues and defining the necessary Revision Issues.
==Subgroup 1: Scheduling
Subgroup 1 covers implementation dependencies, and at this meeting they
reviewed the CIFO entry on task scheduling. It was decided to propose
adding an optional and more generic task-scheduling package to the one
already present in the CIFO.
Previously, the Joint Integrated Avionics Working Group (JIAWG) had
presented Subgroup 1 with requirements for additional scheduling features
to meet the needs of the CART program. Here, they reviewed some proposed
solutions.
Also, two new pragmas were derived and defined as CIFO entries: pragma
PRIORITY_QUEUEING and pragma GLOBAL_PRIORITY_QUEUEING. These pragmas
specify that the entry queue will order tasks by priority; the existing
first-in/first-out (FIFO) order will be the default.
These pragmas also affect the select statement in that they specify that
the selection of alternatives consider priorities after the guards are
evaluated for availability. Pragma PRIORITY_QUEUING is specified in the
task specification, and affects all entry queues and select statements in
the task. Pragma GLOBAL_PRIORITY_QUEUING may be specified in the main
program and affects every entry queue and select statement in the
program.
(Specifying this pragma in the main program is currently under debate.)
Subgroup 1 met with subgroup 3 and presented both of these CIFO entries.
Also, they gave to subgroup 3 a request for the definition of another
entry
for a general-purpose pragma that would provide configuration information
to the runtime environment (RTE) (The suggested syntax is: pragma
RTE_OPTION (string);).
Additionally, Subgroup 1 received a special presentation on scheduling
approaches used at the Software Engineering Institute. This presentation
covered Rate Monotonic Theory for aperiodic servers, sporadic servers and
synchronization issues. Priority-ceiling protocol and priorityinheritance
concepts were also discussed.
At the next ARTEWG meeting, the Subgroup 1 schedule will include
presentations by the following invited speakers:
John Stankovic (Spring Project - Distributed, Real-Time, Predictability)
Jane Liu (Algorithms that can produce useful results over a range of
available execution times)
Al Mok (Multiprocessor on-line scheduling of hard-real-time tasks)
Still to be confirmed: Doug Jensen (Alpha Kernel, Large C-cubed systems)
The presentations are scheduled for the first two days of the next
meeting
and will be open to all ARTEWG members. Panel discussions will follow the
presentations.
==Subgroups 2 and 3
Subgroup 2 covers applications, and is currently generating statistical
data from a recent user survey.
Subgroup 3 covers interfaces, and continues to work towards the next
release of the CIFO document. This will be a major revision and will be
structured as follows:
1. Preface
2. Objectives
3. Using the Catalogue as a Standard
4. Rationale
5. Catalogue Entries:
Run-time Environment Primitives
Control of Data Objects
Tasking Primitives
Task Execution
Critical Run-Time Environment Features
Storage Management
Rationale for Deletions
Deferred Items
Distributed Systems Task Force
The distribution task force is currently working to produce appropriate
CIFO entries for nested atomic actions, nested atomic transactions, and
checkpointing.
They are extending their activities to a number of areas. 1. They will
investigate communication mechanisms for location-independent programs
and
their associated interfaces. These mechanisms (e.g., rendezvous, remote
procedure calls, and asynchronous communications) should not preclude
their
use within a single program. 2. They will investigate interfaces to
support intra-program communication across distributed processors. And 3.
they will investigate and assess the advantages and disadvantages of
multiprogramming versus those of alleviating the problems that force a
multiprogramming approach instead of a single-program approach.
==Task Force on Fault-Tolerant Systems
This task force continues to work on its guidelines document for
fault-tolerant applications. The structure of this document will be:
1. Introduction
2. Background for highly reliable and fault-tolerant systems
3. Critical issues for high reliability run-time environments
4. Concepts of implementing fault tolerance
5. Fault tolerance in executive services
6. Ada-specific considerations for fault tolerance
7. Summary
==Task Force on Model RunTime System Interface (MRTSI)
The MRTSI task force has now finished its review of the MRTSI, and a list
of changes has been produced. These changes mainly concern tightening up
the semantics of some of the entries. The list will be offered for
publication in SIGAda's Ada Letters and Ada UK's Ada User.
The task force also considered the relationship between Ada tasking and
the
proposed POSIX threads standard. The task force's position is summarized
below. (The position was unanimously supported by the full ARTEWG
meeting.)
1. POSIX threads should support implementations of Ada tasks in hard
real-time.
2. The current POSIX threads proposal appears inadequate for supporting
Ada task implementations for real-time applications.
3. POSIX threads should not be elevated to a proposed standard until Ada
implementors who are not also POSIX producers have had time to review it
and evaluate its impact.
==Security Task Force
The newly formed Security Task Force met to define the task force charter
and the pressing issues relating to security and the Ada RTE, and to
generate a plan of action (along with action items and deliverables.)
Two presentations were given to this subgroup: one by Ken Rowe on
architectures and scopes of trusted computing bases (TCBs); the second by
Dr. Charles McKay on models and issues of access control.
The charter will describe the impact of security and integrity support on
the RTE by way of a number of items, including: CIFO security entries;
security restrictions; security guidelines; security standards; and
security modeling techniques.
The charter will also: define its relationship to the "Orange Book"
(TCSEC - DoD 5200.28-STD); address static and dynamic security issues;
cover issues of TCB architectures; and cover issues and techniques of
formal verification.
The issues to be addressed by the task force include:security boundaries
(multi-programming, granularity, etc.); communication issues; "Silicon
Valley" support for B3-level proof-of-concept performance issues;
sufficiency model approach - performance issues; tagged architectures;
the
compilation of security technologies; standardization/public-domain
issues;
security/reliability/fault tolerance/safety & criticality interactions;
reuse issues; models; and terminology.
At this meeting, the subgroup identified their first two tasks: first, to
review the current CIFO entries and identify the associated security
issues
and concerns; second, to generate and centralize information on: 1.
current security technologies; 2. models and architectures; and 3. a
glossary of security terminology
(For a related item, see page 3 for notice of an April computer-security
conference.)
==Meetings and publications
ARTEWG meets formally four times a year. Meetings are scheduled for four
or five days. The meetings tentatively scheduled for the remainder of
1990
are:
Spring: April 30 - May 4, 1990, in Tewksbury, Mass. (sponsored by
Raytheon)
Summer: August 20 - 24, 1990, in Redondo Beach, Calif. (sponsored by
SIGAda)
ARTEWG documents can be ordered from:
Mike Kamrad
Unisys CSD 612/456-7315
MS/Court mkamrad@ajpo.sei.cmu.edu
P.O. Box 64525
Saint Paul, MN 55164-0525
Note: There is no handling or copying charge for ARTEWG publications; but
include a large (8.5"x11") envelope with suitable postage -- indicated
below:
Title: Postage
Catalogue of Runtime Implementation $2.40
Framework for describing Ada Runtime Env. $.85
Survey of Mission Critical Application Req. $2.90
Catalogue of Interface Features and Options $1.25
Model Runtime System Interface $1.25
All five documents $8.65
[Author's note: I wish to thank Tom Griest and Andy Wellings for their
input to this report. For more information, please contact me
(301/731-8894) or Mike Kamrad, Chairman, ARTEWG.]
AdaJUG Conference
Highlights Major Issues in Current Ada Use
Ann S. Eustice
==The Conference in a Nutshell
AdaJUG divided its agenda almost evenly between updates on government
efforts and updates on industry efforts. The government topics included:
a
summary of Ada9X Revision Requests; a briefing on the Navy's ALS/N
compiler
project; and progress in the Army's RAPID program for developing a
library
system for accessing reusable Ada components.
On the last day, the meeting adjourned with the annual "Government
Corner". There a panel of DoD officials met with AdaJUG members from the
commercial and public sectors to talk frankly about how they can help
each
other achieve their common goal of increasing the use of Ada. The panel
included Dr. John Solomond, AJPO director; Mr. Marshall Potter,
Technology Assessment director, Navy IRM; LTC David Schottel,, from the
Army, and Lt Col Bill Cato, from the Air Force.
On the corporate side, several sessions addressed lessons learned in
8888888888888888888
*************************************************************************
"We'd use Ada again in a heartbeat. It's better than anything else
available in the world."
This comment, from Bob Fritz of Orincon Corp., was one of the many
enthusiastic opinions heard on the real-time, real-life uses of Ada at
the
Ada Joint Users Group (AdaJUG) conference held in San Diego this Feb. 57.
The conference was not just enthusiastic; it also gave an excellent
picture
of Ada today -- both in the language's technical aspects, and in how Ada
is
being used in actual projects, and measured in its performance.
Please see the box "AdaJUG in a Nutshell" for a quick summary of the
meeting. We are not able to report on all the briefings in this issue,
but
we hope to use them as the basis for articles in future issues. Most of
the briefings packed enough interest to attract a full audience. This was
helped by their being scheduled consecutively rather than during the same
times.
The exception to that scheduling was on the first day: Gregg Reed, from
Jackson Systems Corp., conducted an all-day tutorial on "Ada Systems
Development", while the Software Cost Estimation Working Group held a
session during the afternoon.
Predicting costs with REVIC
The working group invited Raymond L. Kile, from Hughes Aerospace, to
discuss the history, future, and accuracy of the Revised Enhanced Version
of Intermediate COCOMO -- REVIC, a tool he developed for the Air Force
Contract Management Division (CMD) estimating software costs and
schedules.
Mr. Kile, a major in the Air Force Reserve, did the development work
while
on active duty assigned to CMD at Kirtland AFB, NM. He wanted to create a
cost-estimation model for managers, and used as his basis the formulas
and
definitions from Dr. Barry W. Boehm's book, "Software Engineering
Economics".
Using a current base of DoD projects completed in the last ten years, Mr.
Kile found it necessary to alter some of Dr. Boehm's formulas.
Specifically, he recalibrated the organic, semidetached, and embedded
modes
for REVIC's effort and schedule formulas.
The REVIC model has many other enhancements and features not found in the
COCOMO model -- including the ability to estimate the system-engineering
and development phase and the test-and-evaluation phase of software
development. Mr. Kile was also able to add an Ada-estimation mode to the
REVIC model. This was done when CMD provided calibrated formulas based on
the projects described by Dr. Boehm in his revision to the Ada-COCOMO
model and on 1.2 million lines of code from the Army's AFATDS program.
REVIC estimations of a project's required effort are often 20-30% higher
than those from the standard COCOMO model, Mr. Kile said. Hughes has
reported the REVIC model's estimates to be within 5-10% of actuals, while
other contractors have reported accuracies of approximately 110%.
However,
REVIC's schedule estimates are often considered to be too lengthy. This
is
because REVIC assumes that a project's documentation and formality of
reviews comply with the full requirements of DoD Standard 2167A. Most
government software development projects, Mr. Kile said, use a tailored
version of 2167A. Consequently, "You may be able to beat [REVIC's]
schedule," he said, "but it's extremely risky." He added that it's not
clear whether projects beating the schedule have done so by reducing
documentation requirements.
Responding to a question from the audience, Mr. Kile said that the
distribution of staff effort is based on Dr. Boehm's book, and that not
enough data have been collected to justify changing the distribution in
the
model for Ada projects. "We are in the infancy of collecting data at that
level," he said. He added, however, that 50% of the effort does seem to
be spent upfront, prior to the start of actual coding.
==REVIC nuts and bolts
When developing the tool, Mr. Kile was concerned with keeping it
inexpensive and simple to use. He developed the model on his own time and
donated it to the government. As a result, he said, it lacks a lot of the
"bells and whistles" of commercial models -- such as color and graphics.
But it does not take extensive training to understand and operate. "We
are deliberately keeping it simple so managers will use it instead of
relying on a single local expert," he said. It was not designed to
compete with commercial models. However, its accuracy is comparable.
The REVIC model considers the start of a project to be the
system-engineering phase, and the end to occur after the development,
test,
and evaluation phases. No operational testing is included in the
estimate.
However, it does estimate the costs for maintenance over 15 years, and
provides estimated page counts for 2167A documentation. It estimates the
costs of developing new software and of adopting or reusing existing
software.
REVIC supports the three COCOMO modes (organic, semidetached, and
embedded)
in addition to a new mode for Ada. Mr. Kile explained that Dr. Boehm
provides for a gradually decreasing exponent to account for the the
learning curve present in the Ada software-development process.
The equation in the REVIC model, on the other hand, assumes a fully
trained
team using object-oriented design methodology. Therefore, REVIC may
underestimate a team's effort on their first Ada project, and the
embedded
mode should be used instead.
REVIC assumes a 152-hour manmonth, which the user can change. Many of the
other defaults can also be changed by the user. In addition, REVIC allows
the user to constrain the model by specifying either the staffing levels
or
the schedules; also, REVIC predicts the effects on the overall effort
associated with Brooks Law and compressed schedules.
==Surprise results
According to CMD's data, the equations for the embedded mode and the Ada
mode show a crossover point of approximately 16 thousand lines of code
(KLOC); any less, and Ada becomes the more expensive choice during the
development phase. The data also show that using Ada and the
object-oriented design approach lowers the cost of both the development
and
maintenance phases.
Mr. Kile theorized that because a large project requires many small
teams,
a company's communications overhead usually increases dramatically with
16
KLOC and over. With Ada, the teams do not have to be in constant
communication because the software-specifications part of the code can be
compiled separately and handed to the teams developing the body of the
code.
He added that Don Reifer of Reifer Consultants, has studied over 126
completed projects and agrees with the REVIC equation and the positive
impact of Ada on the development process.
==REVIC in use
REVIC was tested during a six-month mandatory use period at CMD and its
28
AFPROs, and it has been in use by CMD for more than two years. To date,
more than 450 individuals, government organizations, and corporations are
known to be using the model. REVIC is being used and taught at the Air
Force and Navy software-management schools, including the CRAC course at
Brooks AFB and the Air Force Institute of Technology at Wright Patterson
AFB. All three military services are using REVIC, as well as the Defense
Logistics Agency (DLA)and NATO. Major commercial contractors using REVIC
include Hughes, TRW, Westinghouse, Rockwell, and Magnavox.
==For more information
The REVIC object code and user's manual are available free to contractors
and government agencies on an electronic bulletin board system (BBS)
maintained by CMD. (The BBS is at 505/846-5000; 1200 or 2400 baud; use a
communications package that includes XMODEM or Kermit file-transfer
protocol.)
Because of a pending reorganization of CMD and the DLA, however, the
dissemination process for REVIC may change. Negotiations are underway to
transfer the program to the Software Technology Support Center (STSC) at
Hill AFB, Utah.
In the meantime, CMD has fostered two groups to further information
exchange and encourage contractors and program offices to use REVIC: the
REVIC User's Group; and the Cost Working Group at Air Force Systems
Command. Mr. Kile suggested that interested parties join the user's group
to ensure getting the latest information and latest versions of the
model.
Membership in the REVIC User's Group costs $10 a year for individuals,
$50
a year for corporate sponsorship. Contact:
Darrel Knutson
Ball Systems Engineering Division
2901 Juan Tabo, N.E., Suite 235
Albuquerque, NM 87112-1893
The user's group has available for members an analysis of software data
collection and REVIC projects, instructions on calibrating REVIC for Ada,
proceedings of its two meetings, and miscellaneous training session notes
and papers. Contact:
Ms. Karen Sivley
Magnavox Electronic System Co.
1010 Production Road
Fort Wayne, IN 46808; 219/429-4705.
DoD employees interested in receiving training should call Major Walt
Koozin at 505/844-0859. All others should call Ray Kile at 303/344-6692.
==Back to one track
After the parallel sessions of Mr. Kile and Mr. Reed, the conference went
back to a single track -- with overviews of two other DoD-sponsored
efforts: first, on the convergence of software development tool standards
CAIS-A (Common APSE Interface Set) and PCTE+ (Portable Common Tool
Environment).
After that session, Cathy Ruiz of the Naval Ocean Systems Command, San
Diego, updated the audience on the Navy's Ada compiler project, the Ada
Language System/Navy (ALS/N).
CAIS-A/PCTE+ Convergence
Dr. John Solomond, director of the Ada Joint Program Office (AJPO),
started the convergence discussion with the motivation behind the effort.
He emphasized that a standard is essential to achieve economies in the
acquisition of Ada Programming Support Environments (APSEs). He said the
convergence team hoped the existence of an international standard would
increase private-sector interest in developing high-quality integrated
tools.
==Interface technology
Currie Colket, of the Naval Air Development Center (NADC) in Warminster,
Pa., continued the discussion with an introduction to interface
technology.
Both CAIS-A (developed by DoD) and PCTE+ (which evolved from the European
commercial sector) were developed to support Integrated Project Support
Environments (IPSEs). To relate CAIS-A and PCTE+ to the world of
interfaces, Mr. Colket used the preliminary Integrated Software
Engineering Environment (ISEE) Model proposed at the 2nd ISEE Workshop.
This defines the interfaces between a platform (e.g., host and operating
system), a framework (e.g., an object management system), tools (e.g.,
compiler, linker, editor), and a user.
The ISEE model defines only three interfaces: the User to Tool Interface
Set (e.g., X-Windows, GKS); the Tool to Framework Interface Set (e.g.,
CAIS-A, PCTE+); and the Framework to Platform Interface Set (e.g.,
POSIX).
This model was intentionally created to reflect the desired interfaces
and
relationships -- not the world as we know it today. Consequently, it does
not allow a tool to interface directly to a platform. Most tools today
interface directly to the platform, but this circumvents the object
management system and can result in serious database integrity
violations.
CAIS-A, PCTE+, and PCIS are Tool to Framework interfaces. As such, they
provide the necessary services to effectively control the object
management
system in the framework.
==CAIS-A
Gary Pritchett, of SofTech, Inc., San Diego, explained the CAIS-A
standard.
The DoD funded CAIS (DOD-STD-1838) in an effort to reduce APSE
development
costs. CAIS was to save money by enabling projects to share tools and
databases. The latest version (CAIS-A) has been approved as DOD-STD1838A.
CAIS-A added many powerful services to the CAIS interface, Mr. Pritchett
said. They include database typing and support of different views from
tool to tool; data process management, which provides consistent
transactions; and a mechanism to allow distributed or single-machine
implementations. CAIS-A also added input-output packages. (Mr. Pritchett
was quick to say these packages are "not as sophisticated as X-Windows",
but can be extended to include X-Windows.) Secrecy and data integrity are
ensured through new access controls. Finally, there is a triggering
mechanism that can update accounting information, and report on the
status
of products against their scheduled progress.
==PCTE+
Currie Colket explained the PCTE+ interface standard -- sponsored by the
Independent European Programme Group (IEPG), Technical Area-13 (TA-13),
an
organization made up of many European NATO nations.
PCTE+ was defined by IEPG TA-13 to promote a free interchange of
components
between participants. A primary goal of PCTE+ is to support the
integrated
software development environment based on cohesive rather than
heterogeneous tools. PCTE+ is based on PCTE because of PCTE's previous
industry input and acceptance -- as well as its independence from
proprietary systems. PCTE+ supports a distributed database using an
object
management system, supports processes and activities, the distribution of
processes, a notify mechanism, an accounting mechanism, and ensures data
security and integrity.
One of the most noticeable differences between the two standards is
PCTE+'s
graphically sophisticated user interface -- which was identified in the
Winnersh Report as a candidate for the converged interface specification
in
lieu of of CAIS-A's simple terminal input/output interface. Another
difference that will default to the PCTE+ standard is an accounting
system
for resources. Users can specify which objects to be accounted for -such
as programs, files, pipes, message queues, and workstations.
==PCIS
Currie Colket also described the events leading up to the current
convergence effort. The primary events included:
1. An experts workshop in Waltham, Mass., Jan. 25-Feb. 5, 1988, to
identify the similarities and differences of concept between CAIS-A and
PCTE+. These are reported in the "Comparison of CAIS-A and PCTE+", known
as the Waltham Report.
2. An experts workshop in Winnersh, England, Apr. 14 - 28, 1989, to
assess the technical feasibility of specifying an interface standard
based
on upward compatibility with PCTE+ and CAIS-A. The assessment and
recommendations are provided in "PCTE+ and CAIS-A Convergence" -- the
Winnersh Report.
3. An AJPO/IEPG TA-13 meeting on Aug. 22-23, 1989, which accepted the
Winnersh Report and agreed in principle to converge the two interface
standards. The converged specification would be available in the mid-1994
time period.
The new standard will be the "Portable Common Interface Set" (PCIS -pronounced like "pieces"). The name, Mr. Colket pointed out, "takes
the best from both interface specifications". The preliminary PCIS
Programme includes eight phases: 1) PCIS definition; 2) demo
implementation/assessment; 3) conformance capability; 4) update
implementation; 5) standardization; 6) encouragement of PCIS
implementations; 7) encouragement of PCIS environments; and 8)
encouragement of PCIS use.
The first phase will produce an abstract specification, an Ada binding, a
C
binding, user guides, and transition guides. Input from the general
community will be encouraged to produce a standard that will be
acceptable
to widest possible spectrum of interests.
Dr. Solomond ended the briefing by encouraging the AdaJUG members to find
out more about the PCIS interface technology -- which will provide
effective integrated software-engineering environments in the near
future.
Available documentation on the CAIS-A/PCTE+ convergence includes: the
Waltham Report (June 88); NATO Requirements and Design Criteria (NRAC)
(Dec. 88); Rationale for the NRAC (Dec. 88); and the Winnersh Report
(Nov. 89).
Documents can be obtained from:
In the U.S.:
In Europe:
Mr. Currie Colket
Ken Hayter
Code 7031
N 132 RSRE
Naval Air Development Ctr
Saint Andrews Road
Warminster, PA 18974
Great Malvern, WORCS WR14 3PS
215/441-2149
England, UK
FAX: 215/441-3225
+44 (0684) 895 836
e-mail: colket@nadc.arpa
FAX: +44 (0684) 894 540
e-mail: KWH%hermes.mod.uk@relay.MOD.UK
For information on the For information on the
CAIS-A standard, contact: PCTE+ standard, contact:
Duston Hayward Ian Campbell
Code 411 GIE Emeraude
Naval Ocean Systems Ctr BULL LV58F23
San Diego, CA 92152-500068 route de Versailles
619/553-4077 78430 Louveciennes
hayward@nosc-tecr.arpa France
Ada and 2167
Robert Fritz, whose very upbeat views on Ada opened this article, spoke
on
some practical aspects of Ada. During his presentation, "Managing the
Chaos: Ada, 2167, and DoD Software", Mr. Fritz said that he hoped to
encourage the audience to question "conventional wisdom" about Ada, and
to learn more about the language as it is used to build systems. He
talked
about Orincon's multi-sensor data fusion and tracking software that it
built as a subcontractor for an airborne anti-submarine surveillance and
attack system.
Factors that affected the project's schedule, Mr. Fritz said, were that
the customer mandated the use of Ada, of DoD-STD-2167 documentation, and
of
a UNIX operating system.
In order to program in Ada, more training and design time was needed.
Complying with the extensive documentation required under DoD-STD-2167
put
pressure on the contractor's schedule, as did the customer's production
lead times. He said that the job is made easier if the government manager
understands not only the particular application but the overall process,
which may require special training.
==Comparisons with COCOMO
Both the time and effort expended on the project were higher than
estimated
by the software cost-estimation tool used -- Basic COCOMO. Mr. Fritz
attributed this to the complexity of the system and software -- which had
increased since the original formulas and assumptions of COCOMO were made
available in Dr. Barry Boehm's book, "Software Engineering Economics" -the same discussed in Mr. Kile's earlier comments on REVIC.
Also, in what he admitted was a very subjective estimate, Mr. Fritz said
that, when a complex operator interface was present, 2167 documents
doubled
the effort COCOMO predicted.
His experience in producing full DoD-STD-2167 documentation gave Mr.
Fritz
a chance to create other estimations for scheduling time and effort. For
example, if the software required a complex operator interface, the
effort
COCOMO predicts actually doubles under 2167 documents. If the software
involves a moderate to extensive operator interface, Mr. Fritz said,
assume one page of documentation for every 2.5 lines of code (LOC); one
page for 10 LOC if little or no operator interface is present. Those
pages, Mr. Fritz said, each require four hours to write and edit in the
draft phase, two hours in the preliminary phase, and another two hours in
the final phase. The requirements and design pages alone, he said,
approach one page per 2-5 LOC.
==Lessons learned
Turning to lessons learned in designing the system, Mr. Fritz said that
if
Ada tasks are eliminated, Ada has little impact on the software design.
Ada exception policy and error handling strategy, he said, should be
established in high-level design. In general, he encouraged designers to
keep the Ada programming simple and straightforward on large projects. He
also suggested that the developers build system-throughput and memory
estimates using spreadsheet models.
In terms of working with DOD-STD-2167, Mr. Fritz said that completing the
documents does not necessarily mean that the design is completed. He
warned that, in the face of overwhelming documentation requirements,
teams
must focus on completing the design.
Mr. Fritz's final recommendations to the DoD software community were to
acknowledge that both the customer and the builder are not certain what
systems to build or how to build them. He asked that the community work
to
ensure that tools mandated for use, such as validated compilers, actually
work for the volume and complexity of modern-day software projects. He
also suggested that the community develop a means for nonjudgemental
reporting of actual project experience with software technology.
AdaJUG business meeting
AdaJUG elections were held on Wednesday during the business meeting, and
Joe Dangerfield, of TeleSoft in San Diego, was elected for his third
consecutive term as AdaJUG chair, CEO, and Chairman of the Board. Also
elected were:
First Vice Chair: Mike Ryer (Intermetrics, Boston, Mass.)
Second Vice Chair: Dudrey Smith (SLI Avionics Sys., Grand Rapids, Mich.)
First Secretary: Ingeborg O'Reilly (Systems Designers Software,
Cambridge,
Mass.)
Second Secretary: Cathy Peavy (Martin Marietta, Denver, Colo.)
Treasurer : Janice Chelini (Delco Systems, Goleta, Calif.)
Non-officer Members of the Board:
Carolyn Gannon (Gannon Consulting, Woodside, Calif.)
Elaine Hauser (Boeing Aerospace, Seattle, Wash.)
==Universal suffrage
Federal employees, both civilian and military, can now vote in AdaJUG.
Prior to this meeting, they had not been able to do so. The Future
Directions Committee had suggested removing this ban, and the proposal
was
approved by the AdaJUG Executive Council.
After the elections, Mr. Dangerfield reiterated the Executive Council's
statement that AdaJUG is now encouraging members of the military and
civil
service to chair working groups and to join committees.
In a telephone interview the following week, Mr. Dangerfield said that
this is a "very subtle, but very important change for the AdaJUG." The
military and government members now have the right to vote on
resolutions,
except in elections for board members or officers, or when the resolution
is directed at the DoD or government. "Their own admirals and generals
don't want them to vote on [such issues]," Mr. Dangerfield said. "It's
a potential conflict of interest." They can vote on any other
resolutions.
Military and federal employees were soon given an opportunity to exercize
their newly won suffrage. Mr. Dangerfield brought a suggestion to the
general assembly from the Future Directions Committee that AdaJUG go
beyond
its traditional purview, embedded systems, to address issues concerning
non-embedded systems as well. In the discussion that followed, members
said they hoped this would attract papers on subjects outside the realm
of
the real-time use of Ada, such as on Ada in management information
systems
(MIS) applications. The suggested expansion of interest was supported
overwhelmingly when Mr. Dangerfield asked the members for a spontaneous
vote during the business meeting. The meeting ended with Mr. Dangerfield
encouraging the members to volunteer for existing working groups and to
suggest new ones -- which "can be created on the spot".
Behind the Revision Process -An Interview with Chris Anderson
John Walker
The shape of Ada in the '90s is being determined right now -- by the
entire
Ada community: users, developers, managers, educators, and everyone else.
The focal point is the Ada 9X Project -- headed up by Chris Anderson, of
the Air Force Armament Lab. This project is charged with developing and
proposing the Requirements, the actual changes that will be made to Ada.
Chris has always emphasized that community input is essential at every
stage in the process. She's made that point at countless conferences,
briefings, and other meetings.
By submitting Revision Requests, many of you have already told the
project
what you'd like to see (or avoid) in Ada 9X. But not everyone can get to
those conferences to see what the Ada 9X Project is thinking about.
So, we thought it would be helpful to ask Chris to give some background.
(In a future issue, we hope to look at some of the technical questions
the
Ada 9X effort will consider.)
Here, then, is an interview the newsletter editor, John Walker, had with
Chris last month.
==The response from the public
Was there anything in the Revision Requests -- either by the
subject matter or by the number of submissions -- that
surprised you?
I don't think so -- the biggest surprise was not the end volume, but that
so many came in the last three weeks. We got about 200 out of the 774
responses in the last week of October -- even though it was open for a
year.
I was pleased with the response from the public. To me it indicated an
interest in the whole process. I think they believe that we're serious
about this and that we're seriously considering their requests for change
-- which we are. I felt good about that because I've stressed it over the
past year and a half at every presentation that I've given, and I think
that the public senses my sincerity.
As far as the type of requests we've gotten -- not too many surprises.
The
areas that you'd initially think that there might have been requirements
for change are the ones with requests coming in. There are a lot in the
real-time embedded area, where people wanted to see some changes and
improvements. Some requests concerned object-oriented programming -which
we're trying to tackle, right now. The extent has still not been
determined.
The guiding Ada 9X philosophy makes us balance change and stability. It's
important to make some changes to meet user needs -- but by the same
token,
we're being very conservative. We want to preserve stability in the
marketplace -- and not make devastating changes. So we're taking all of
this in, and we're listening very intently to the users.
==Experts meetings
I might add another thing here -- you didn't ask about it, but I'll
volunteer it -- about our attempt to listen to what the user wants. Of
course, we had the year for "Tell me what your Revision Request is." And
of course it was great to hear those.
But I'm also having some special meetings with users of various segments
of
the users community. We had one last month [January] with the
trusted-systems and safety-critical people, and it went extremely well.
We
invited in about 25 experts in that particular area -- users, hands-on
people. We said, "Okay, tell us -- if you're not using Ada, why? What do
you look for in programming languages. If you are using Ada, what are the
stumbling blocks? And what are the workarounds?"
We had a few of the Distinguished Reviewers there, and a few of the
Requirements Team members, and it was an extremely good exchange of
information. We came away with a much better feeling for what their
requirements were. Even though some of the ideas may have been written
down and submitted in Revision Requests, I think the one-on-one contact
and
the dialogue was extremely valuable; a lot of that is going to be folded
in.
Because that meeting was so successful, we're planning some other ones in
the future. Next month, I've scheduled two more meetings. One is in the
information-systems area; the other is in the SDI area. Information
systems is an area that I feel very strongly about. I think Ada is
suitable in that area, but it's been rather slow in being picked up.
==Revision Issues versus Requirements
Did you have anything that you wanted to emphasize for the
future? Predictions or lack thereof? Anything about how
we'll get to see the actual changes to the language -- the
Requirements?
One thing that we're doing right now is organizing the revision requests
into what we call Revision Issues. You can see this in my project report
to the public. [See the Ada 9X column, p. 9.]
We're going to start releasing things incrementally so the public can
start
getting a view into the process -- which, as they might imagine, is a
very
arduous process of analyzing all these revision requests, trying to group
them and decide what the revision issues are, and then from that actually
developing the Requirements.
What we decided to do is start releasing Revision Issues -- which will be
groupings of Revision Requests. Then from those, we're going to actually
develop the requirements. So, initially you will not see "Requirements",
you'll see "Revision Issues". As we se the totality of them, we'll start
to see the forest and start pruning a few trees. It's important that the
public understands that a Revision Issue they see in June may disappear
in
August. This "pruning" process will continue until we finally come up
with the ultimate set of Requirements.
We're planning a Requirements Workshop in Sweden in April; this is
sponsored by AdaEurope, the International Standards Organization's
Working
Group 9, and the Ada9X Project Office in coordination with AdaJUG and
SIGAda. Each one of these groups gets to pick a certain number of people
to send to this workshop, and the total will be about 50 attendees. At
the
same time that those people will be seeing the first set of releases of
Revision Issues, we will also publish them on the bulletin boards and
various other places. That way, we can get them out to people so that can
take a look; if they have comments, they can send them in.
The next release will be at the end of June at the Washington Ada
Symposium, in the Washington, D.C. area. Then the one after that will be
at the SIGAda meeting in August in Los Angeles.
The Requirements should be completed by the TRI-Ada meeting in December.
So up until then, you're going to see these Revision Issues with a lot of
discussion. But the actual Requirements will come out later. And we'll be
soliciting comments from the public all along.
==Tracking the process
And if someone has put in a request, and it shows up and then
disappears, there's going to be a way for them to track them
and find out why they were dropped.
Right, there will be justification for all of that. When they see a
Revision Issue, people will know which Revision Requests are reflected in
it. And finally, with the Requirement, if some were dropped, there'll be
an explanation of why they were not included.
The special meetings that you'll have with the experts, is that by
invitation only?
Yes. I'm trying to find them by the contacts that I know. I'm calling
lots of project offices. I had a very good mix the last time. The only
reason for the "short-cut" soliciting approach is the need to fit these
meetings in during the next few months. I don't have the luxury of a lot
of advertizing.
You're doing a lot with presentations at various conferences. How should
people keep up if they don't get to the conferences?
I think the best thing -- if they don't go to conferences -- is to check
the bulletin boards. All those releases are going to be put on the Ada9X
bulletin board and the AJPO host, and on EUROKOM. I've been working with
some of the European users -- like AdaSweden, AdaUK -- asking them if
perhaps there's an alternate bulletin board they have, to get the word
out.
So if people can't attend one of the conferences to get hardcopies of
documents, they should check the bulletin boards -- we won't be able to
afford to mail copies to everyone -- it's just too big a burden on the
budget!
Anything to emphasize in closing?
I guess the big thing to stress is user input. I'm sincere about that,
and
-- as my briefing schedule will show -- I'm trying to get out, talk to
the
people, and get their feedback. This is really their change to the
language.
Validated Ada Compilers - (as of Feb. 1, 1989)
The following is a list of validated Ada compilers, listed
alphabetically
by vendor.
There are currently 231 validated base Ada compilers
98
derived compilers. This list is updated monthly.
For the most
current
information on validated Ada compilers,
Information
Clearinghouse.
(Key:
Vendor &
Compiler
and
please contact the Ada
* = Derived compiler, base system above / (pending) = Pending Revalidation / (#) = No validation certificate number)
HOST
Machine
TARGET
Machine
AETECH
IntegrAda,
Version 4.1.0
(#890113W1.10024)
EXPIRES: 90-12-01
Compaq Deskpro
286 (under MS DOS
3.1)
Same as Host
AETECH
IntegrAda,
Version 4.1.0
(#890113W1.10025)
EXPIRES: 90-12-01
KayPro 386 (under
MS DOS 3.21)
Same as Host
AETECH
IntegrAda,
Version 4.1.0
(#890113W1.10026)
EXPIRES: 90-12-01
Compaq Deskpro
386/25 (under MS
DOS 3.31)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10160)
EXPIRES: 90-12-01
Unisys 386 (under
MS DOS 3.3)
Same as Host
AETECH, INC.
IntegrAda,
Version 5.2
(#890919W1.10161)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(under SCO Xenix
2.2.2)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10162)
EXPIRES: 90-12-01
IBM PS/2 Model 70
(under MS DOS
3.3)
Same as Host
AETECH, INC.
IntegrAda,
Version 3.2
(#890919W1.10163)
EXPIRES: 90-12-01
Zenith Z-386/25
(under
Interactive Unix
2.1)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10164)
EXPIRES: 90-12-01
Zenith Z-386/25
(under MS DOS
3.3)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10165)
EXPIRES: 90-12-01
Zenith Z-3727-ET
(under
Interactive Unix
2.1)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10166)
EXPIRES: 90-12-01
Zenith Z-3727-ET
(under MS DOS
3.3)
Same as Host
AETECH, INC.
IntegrAda,
Version 4.2
(#890919W1.10167)
EXPIRES: 90-12-01
Zenith ZCV-2322
(under MS DOS
3.3)
Same as Host
Alliant Computer
Systems
Corporation
Alliant FX/Ada
Compiler,
Version 2.2
(#890605W1.10083)
EXPIRES: 90-12-01
Alliant FX/80
(under
Concentrix,
Release 5.0)
Same as Host
FX/80, FX/40,
FX/8, FX/4, FX/1,
FX/82, VFX/80,
VFX/40, VFX/4 &
VFX/82 (under
Concentrix,
Release 5.0)
Each Host,
self-targeted
Zenith Z-248
(under MS/DOS
version 3.2)
Same as Host
PC/AT, Vectra 286
(ES/12) & Compaq
386 (under MS-DOS
v3.2)
Each Host,
self-targeted
Sperry IT (under
MS-DOS v3.2)
Same as Host
*Derived
Alliant Computer
Systems
Corporation
Alliant FX/Ada
Compiler,
Version 2.2
(BASE
#890605W1.10083)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_003
Version 4.1
(#881121A1.10003)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003,
Version 4.2
(BASE
#881121A1.10003)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003,
Version 4.2
(BASE
#881121A1.10003)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003,
v4.2
(BASE
#881121A1.10003)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003
Version 4.3
(BASE
#881121A1.10003)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_003,
Version 4.3
(BASE
#881121A1.10003)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_003
Version 4.1
(#881121A1.10004)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003,
Version 4.2
(BASE
#881121A1.10004)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyComp_003,
v4.2
(BASE
#881121A1.10004)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_003
Version 4.3
(BASE
#881121A1.10004)
EXPIRES: 90-12-01
Zenith Z-248 (all
models) (under
MS-DOS v3.2)
Any Host
Compaq 386, HP
Vectra 286
(ES/12), Sperry
IT & IBM PC/AT
(under MS/DOS
v3.2)
Each Host,
self-targeted
Zenith Z-248 (all
models) (under
MS/DOS v3.2)
Any Host
IBM PS/2 Model 60
(under MS/DOS
version 3.2)
Same as Host
PS/2 Model 80
(under MS-DOS
v3.3)
Same as Host
IBM PS/2 Model 60
(under MS-DOS
version 3.2)
Same as Host
IBM PS/2 Models
60 & 80 (under
MS/DOS v3.2 &
v3.3, resp.)
Each Host,
self-targeted
Alsys
AlsyCOMP_016
Version 4.1
(#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_016
Version 4.2
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyComp_016,
v4.2
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_016,
Version 4.3
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_016,
Version 4.3
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_016,
Version 4.3
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_016,
Version 4.3
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
WANG PC 386
(under MS/DOS
with Pharlap
Extender version
3.2)
Same as Host
Compaq 386 (under
MS-DOS with
Pharlap Extender
Version 3.1)
Same as Host
Wang PC 386
(under MS-DOS
with Pharlap
Extender, version
3.2)
Same as Host
GRiDCASE 386 1500
Series (under
MS/DOS v3.3 with
Pharlap Extender)
Same as Host
Hewlett Packard
Vectra RS/25C &
RS/20 (under
MS/DOS v3.3 with
Pharlap Extender)
Any Host
Compaq 386 (under
MS/DOS v3.1 with
Pharlap Extender)
Any Host
Wang PC 386
(under MS/DOS
v3.2 with Pharlap
Extender)
Any Host
*Derived
Alsys
AlsyCOMP_016
v4.3
(BASE
#881121A1.10005)
EXPIRES: 90-12-01
CompuAdd 316, 320
& 325 (under
MS/DOS v3.3 Phar
Lap DOS Extender)
Any Host
Alsys
AlsyCOMP_016
Version 4.1
(#881121A1.10006)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(under MS/DOS
with Pharlap
Extender version
3.2)
Same as Host
*Derived
Alsys
AlsyComp_016,
v4.2
(BASE
#881121A1.10006)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(under MS-DOS
with Pharlap
Extender, version
3.2)
Same as Host
IBM PS/2 Models
70 & 80 (under
MS/DOS v3.2 with
Pharlap Extender)
Any Host
COMPAQ DESKPRO
386 (under OS/2
version 1.0)
Same as Host
Compaq DeskPro
386 (under OS/2
version 1.0)
Same as Host
*Derived
Alsys
AlsysCOMP_016,
Version 4.3
(BASE
#881121A1.10006)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_032
Version 4.1
(#881121A1.10007)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyComp_032,
v4.2
(BASE
#881121A1.10007)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_032,
Versions 4.2 &
4.3
(BASE
#881121A1.10007)
EXPIRES: 90-12-01
Alsys
IBM PC/AT (under
IBM OS/2 v1.0)
Same as Host
IBM PS/2 Model 60
Same as Host
AlsyCOMP_032
Version 4.1
(#881121A1.10008)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyComp_032,
v4.2
(BASE
#881121A1.10008)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_032,
Versions 4.2 &
4.3
(BASE
#881121A1.10008)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_034
Version 4.1
(#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_034
Version 4.1 &
4.2
(BASE
#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_034
Version 4.2.1
(BASE
#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsysCOMP_034,
Version 4.2
(BASE
(under OS/2
version 1.0)
IBM PS/2 Model 60
(under OS/2
version 1.0)
Same as Host
IBM PS/2 Models
70 & 80 (under
IBM OS/2 v1.0)
Any Host
MULTITECH 1100
(under
Interactive
386/ix release
1.04 (Unix system
V.3))
Same as Host
MULTITECH 1100
(under
INTERACTIVE
386/ix release
1.04); Sun 386i
(under SunOS
v4.0); Prime EXL
320 (under System
V Release 3.0
PRIME EXL)
Each Host,
self-targeted
Compaq 386/20e
(under
Interactive
386/ix v2.01)
Same as Host
IBM PS/2 Models
80 (under IBM AIX
version 1.1)
Same as Host
#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_038,
Version 4.2
(BASE
#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_038,
Version 4.2
(BASE
#881121A1.10009)
EXPIRES: 90-12-01
*Derived
Alsys
AlsyCOMP_038,
Version 4.2
(BASE
#881121A1.10009)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_006
Version 4.1
(#881216N1.10012)
EXPIRES: 90-12-01
Zenith Z-248, all
models (under IBM
Secure Xenix
version 1.1)
Any Host
IBM PC AT (under
IBM Secure Xenix
version 1.1)
Any Host
Wang PC386 (under
SCO Xenix System
V release 2.2.3)
Any Host
IBM 9370 Model 90
(under VM/IS CMS
release 5.1)
Same as Host
Alsys
AlsyCOMP_013
Version 4.1
(#881216N1.10013)
EXPIRES: 90-12-01
IBM PC/AT (under
PC-DOS 3.1)
IBM 370 3084Q
(under MVS 3.2)
Alsys
AlsyCOMP_013
Version 4.1
(#881216N1.10014)
EXPIRES: 90-12-01
IBM PC/AT (under
PC-DOS 3.1)
IBM 9370 Model 90
(under VM/IS CMS
release 5.1)
Alsys
AlsyCOMP_006
Version 4.1
(#881216N1.10015)
EXPIRES: 90-12-01
IBM 9370 Model 90
(under VM/IS CMS
release 5.1)
IBM 370 3984Q
(under MVS 3.2)
Alsys
AlsyCOMP_019,
Version 4.1
Zenith Z-248
Model 50 (under
MS/DOS, Version
Intel iSBC 286/12
single board
computer (bare
(#890119A1.10032)
EXPIRES: 90-12-01
3.2)
machine)
Zenith Z-248
Model 50 (under
MS-DOS v3.2)
Intel iSBC 86/35,
iSBC 186/03 &
iSBC 286/12
Alsys
AlsyCOMP_004,
Version 4.31
(#890314A1.10036)
EXPIRES: 90-12-01
APOLLO DN 4000
(under Domain/OS
SR 10.0)
Same as Host
Alsys
AlsyCOMP_005,
Version 4.3
(#890314A1.10037)
EXPIRES: 90-12-01
SUN 3/260 (under
Sun OS release
3.2)
Same as Host
Alsys
AlsyCOMP_002,
Version 4.3
(#890314A1.10038)
EXPIRES: 90-12-01
HP 9000 S 350
(under HP-UX,
Version 6.2)
Same as Host
Alsys
AlsyCOMP_027,
Version 4.3
(#890314A1.10039)
EXPIRES: 90-12-01
APPLE MACINTOSH
II (under A/UX
release 1.1 Beta
1)
Same as Host
Alsys
AlsyCOMP_035,
Version 4.3
(#890314A1.10040)
EXPIRES: 90-12-01
CETIA UNIGRAPH
6000 (under
Unigraph/X
release 3.0.1)
Same as Host
Alsys
AlsyCOMP_017,
Version 4.0
(#890531N1.10087)
EXPIRES: 90-12-01
MicroVAX II
(under MicroVMS
V4.7)
INMOS T425
transputer
implemented on a
B403 TRAM, using
the Host running
INMOS Iserver
V1.30 for
file-server
support via a
CAPLIN QT0 board
link (bare
machine)
*Derived
Alsys
AlsyCOMP_019,
Version 4.2
(BASE
#890119A1.10032)
EXPIRES: 90-12-01
Alsys
AlsyCOMP_017,
Version 4.0
(#890531N1.10088)
EXPIRES: 90-12-01
MicroVAX II
(under MicroVMS
V4.7)
INMOS T800
transputer
implemented on a
B403 TRAM, using
the Host running
INMOS Iserver
V1.30 for
file-server
support via a
CAPLIN QT0 board
link (bare
machine)
Alsys
AlsyCOMP_037
V4.0
(#890623N1.10107)
EXPIRES: 90-12-01
INMOS T800
transputer on a
B405 TRAM (bare)
with an INMOS
B008
communications
link implemented
in an IBM PC/AT
(under MS-DOS 3.1
and INMOS Iserver
V1.30)
INMOS T800
transputer
implemented on a
B405 TRAM (bare),
using an IBM
PC/AT under
MS-DOS 3.1
running INMOS
Iserver V1.30 for
file-server
support via an
INMOS B008 board
link
Alsys
AlsyCOMP_037
V4.0
(#890623N1.10108)
EXPIRES: 90-12-01
INMOS T800
transputer on a
B405 TRAM (bare)
with an INMOS
B008
communications
link implemented
in an IBM PC/AT
(under MS-DOS 3.1
and INMOS Iserver
V1.30)
INMOS T425
transputer
implemented on a
B403 TRAM (bare),
using an IBM
PC/AT under
MS-DOS 3.1
running INMOS
Iserver V1.30 for
file-server
support via an
INMOS B008 board
link
Alsys
AlsyCOMP_023,
Version 4.2
(#890720N1.10124)
EXPIRES: 90-12-01
IBM 370 3084Q
(under MVS 3.2)
Same as Host
Alsys
AlsyCOMP_028
Version 4.33
(#890926A1.10173)
EXPIRES: 90-12-01
Compaq 386/20
(under Compaq DOS
3.31)
Motorola
MVME130COF
(68020/68881)
with ARTK v4.33
(bare machine)
Alsys
SUN 3/260 (under
Intel iSBC 286/12
AlsyCOMP_031
Version 4.2
(#890927A1.10171)
EXPIRES: 90-12-01
SunOS release
3.2)
with ARTK v4.2
(bare machine)
Sun-3/140 (under
MS/DOS v3.3 Phar
Lap DOS Extender)
Intel iSBC
186/03A, with
ARTK v4.2 (bare
machine)
Alsys
AlsyCOMP_030
Version 4.2
(#890927A1.10172)
EXPIRES: 90-12-01
VAX 6210 (under
VMS 5.0)
Intel iSBC 386/31
with ARTK v4.2
(bare machine)
Alsys
AlsyCOMP_012,
Version 5.1
(#891102A1.10195)
EXPIRES: 90-12-01
HP 9000 S 370
(under HP-UX,
Version 6.5)
Motorola MVME121
(68010), with
ARTK Version 5.1
(bare machine)
Alsys
AlsyCOMP_015,
Version 5.1
(#891102A1.10196)
EXPIRES: 90-12-01
Sun-3/260 (under
SunOS release
3.2)
Motorola
MVME130COF
(68020/68881),
with ARTK Version
5.1 (bare
machine)
Alsys
AlsyCOMP_036,
Version 5.1
(#891121A1.10197)
EXPIRES: 90-12-01
Apollo DN3000
(under DOMAIN/OS
SR 10.1)
Motorola MVME101
(68000), with
ARTK Version 5.1
(bare machine)
Alsys
AlsyCOMP_017
V4.3
(#891124N1.10202)
EXPIRES: 90-12-01
MicroVAX II
(under MicroVMS
4.7)
INMOS T222
transputer
implemented on a
B416 TRAM (bare),
using an IBM
PC/AT under
MS-DOS 3.1
running INMOS
Iserver V1.41 for
file-server
support via a
CAPLIN QT0 board
link
Alsys
AlsyCOMP_011,
VAX 6210 (under
VMS 5.0-2)
Motorola
MVME133A-20
*Derived
Alsys
AlsyCOMP_031
v4.2
(BASE
#890927A1.10171)
EXPIRES: 90-12-01
Version 5.1
(#891129A1.10227)
EXPIRES: 90-12-01
(68020/68881),
with ARTK Version
5.1 (bare
machine)
Alsys
AlsyCOMP_018,
Version 4.32
(#891208A1.10228)
EXPIRES: 90-12-01
VAX 6210 (under
VMS 5.0-2)
Same as Host
Alsys
AlsyCOMP_010,
Version 4.32
(#891208A1.10229)
EXPIRES: 90-12-01
MicroVAX II
(under ULTRIX 32,
Version 3.0)
Same as Host
Alsys
AlsyCOMP_037
V4.3
(#891213N1.10201)
EXPIRES: 90-12-01
INMOS T800
transputer on a
B405 TRAM (bare)
with an INMOS
B008
communications
link implemented
in an IBM PC/AT
(under MS-DOS 3.1
and INMOS Iserver
V1.41)
INMOS T222
transputer
implemented on a
B416 TRAM (bare),
using an IBM
PC/AT under
MS-DOS 3.1
running INMOS
Iserver V1.41 for
file-server
support via an
INMOS B008 board
link
Apollo Computer,
Inc.
Domain/Ada,
V3.0m
(#890719W1.10125)
EXPIRES: 90-12-01
DN3500 (under
Domain/OS,
SR10.1.0.2)
Same as Host
Apollo Computer,
Inc.
Domain/ADA
V3.0.mbx
(#891128S1.10234)
EXPIRES: 90-12-01
DN4000 (under
Domain/OS SR10.2)
Motorola
MVME133A-20
(68020/68881)
(bare machine)
BiiN
BiiN Ada, V2.00
(#881208W1.10010)
EXPIRES: 90-12-01
BiiN 60 (under BiiN/OS
V1.02)
Same as Host
BiiN 60 (under BiiN/OS
V2)
Each Host, self-targeted
*Derived
BiiN
BiiN Ada, V2.01
(BASE
#881208W1.10010)
EXPIRES: 90-12-01
Bull HN
Information
Systems Inc.
GCOS 8 Ada
Compilation
System, Version
2.3
(#890831S1.10146)
EXPIRES: 90-12-01
DPS 9000 (under
GCOS 8 SR 4000)
Same as Host
Bull HN
Information
Systems Inc.
GCOS 8 Ada
Compilation
System, Version
2.3
(#890924S1.10231)
EXPIRES: 90-12-01
DPS 8000 (under
GCOS 8 SR 3000)
Same as Host
Concurrent
Computer
Corporation
C3 Ada, Version
R02-02.00
(#890711W1.10109)
EXPIRES: 90-12-01
Concurrent 3280
MPS (under OS/32,
Version
R08-02.03)
Same as Host
Concurrent
Computer
Corporation
Series 3200:
3200MPS, 3203,
3205, 3210, 3230,
3250, 3230XP,
3250XP, 3230MPS,
3260MPS &
3280MPS; Micro3 &
Micro5 (under
OS/32, Version
R08-02.03)
Each Host,
self-targeted
Concurrent
Computer
Corporation
Series 3200:
3200MPS, 3203,
3205, 3210, 3230,
3250, 3230XP,
Each Host,
self-targeted
*Derived
Concurrent
Computer
Corporation
C3 Ada Version
R02-02
(BASE
#890711W1.10109)
EXPIRES: 90-12-01
*Derived
Concurrent
Computer
Corporation
C3 Ada Version
R02-03
(BASE
#890711W1.10109)
EXPIRES: 90-12-01
3250XP, 3230MPS,
3260MPs &
3280MPS; Micro3 &
Micro5 (under
OS/32, Versions
R08-02.03 &
R08-03)
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(#890818S1.10130)
EXPIRES: 90-12-01
Concurrent 6600
(MC68030)
w/MC68882
Floating Point
(under RTU
Version 5.0)
Same as Host
Concurrent 6000
series (MC68030)
w/MC68882
Floating Point
(under RTU
Version 5.0)
Any Host
Concurrent 5000
series (MC68020)
w/MC68881
Floating Point
(under RTU
Version 5.0)
Any Host
Concurrent 6600
(MC68030)
w/Lightning
Floating Point
(under RTU
Version 5.0)
Same as Host
Concurrent 5000
series (MC68020)
w/Lightning
Floating Point
(under RTU
Version 5.0)
Any Host
*Derived
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(BASE
#890818S1.10130)
EXPIRES: 90-12-01
*Derived
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(BASE
#890818S1.10130)
EXPIRES: 90-12-01
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(#890818S1.10131)
EXPIRES: 90-12-01
*Derived
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(BASE
#890818S1.10131)
EXPIRES: 90-12-01
*Derived
Concurrent
Computer
Corporation
MC-Ada, Version
1.2
(BASE
#890818S1.10131)
EXPIRES: 90-12-01
Concurrent 6000
series (MC68030)
w/Lightning
Floating Point
(under RTU
Version 5.0)
Any Host
Concurrent
Computer
Corporation
C3 Ada, Version
R00-00
(#891103I1.10199)
EXPIRES: 90-12-01
Concurrent
Computer
Corporation 5600
(under RTU
Version 4.0A)
Same as Host
Control Data
Corporation
ADA/VE, Version
1.3
(#890901S1.10147)
EXPIRES: 90-12-01
CYBER 932 (under
NOS/VE level 727)
Same as Host
CONVEX Computer
Corporation
CONVEX Ada
Version 1.1
(#890508W1.10077)
EXPIRES: 90-12-01
CONVEX C210
(under CONVEX
Unix, Version
7.1)
Same as Host
CONVEX C201,
C202, C120, C210,
C220, C230, C240,
C210i, C220i &
C230i (under
CONVEX Unix,
Version 7.1)
Any Host
CRAY X-MP (under
UNICOS Release
5.0)
Same as Host
CRAY X-MP (under
UNICOS Release
4.0)
Same as Host
*Derived
CONVEX Computer
Corporation
CONVEX Ada
Version 1.1
(BASE
#890508W1.10077)
EXPIRES: 90-12-01
Cray Research,
Inc.
Cray Ada
Compiler,
Version 1.1
(#890523W1.10080)
EXPIRES: 90-12-01
*Derived
Cray Research,
Inc.
Cray Ada
Compiler,
Version 1.1
(BASE
#890523W1.10080)
EXPIRES: 90-12-01
Cray Research,
Inc.
Cray Ada
Compiler,
Version 1.1
(#890523W1.10081)
EXPIRES: 90-12-01
CRAY-2 (under
UNICOS Release
5.0)
Same as Host
CRAY-2 (under
UNICOS Release
4.0)
Same as Host
MV 15000 & MV
10000 (under
AOS/VS 7.60 &
AOS/VS II 1.00,
resp.)
Each Host,
self-targeted;
and MV 15000
(under AOS/RT32
5.00)
MV family of
computers (under
AOS/VS 7.60 &
AOS/VS II 1.00)
Any Host; and any
Host (under
AOS/RT32)
DDC International
A/S
DDC-I Ada
Compiler System
Version 4.3
(#881212W1.10011)
EXPIRES: 90-12-01
VAX 8530 (under
VMS 4.5)
Same as Host
DDC International
A/S
DACS for
Sun-3/SunOS,
Version 4.4
(1.1)
(#891027S1.10183)
Sun-3/60 (under
SunOS UNIX,
Version 4.2,
Release
4.0_Export)
Same as Host
*Derived
Cray Research,
Inc.
Cray Ada
Compiler,
Version 1.1
(BASE
#890523W1.10081)
EXPIRES: 90-12-01
Data General
Corporation
ADE Revision
3.01
(#890615S1.10126)
EXPIRES: 90-12-01
*Derived
Data General
Corporation
ADE Revision
3.01
(BASE
#890615S1.10126)
EXPIRES: 90-12-01
EXPIRES: 90-12-01
DDC International
A/S
DACS for Sun-3
-> Lynwood/LynX,
Version 4.4
(1.1)
(#891027S1.10184)
EXPIRES: 90-12-01
Sun-3/50 (SunOS
UNIX, Version
4.2, Release
4.0_Export)
Lynwood j430
(under LynX,
Version 1.4F)
DDC International
A/S
DACS-386/UNIX,
Version 4.4
(#891027S1.10185)
EXPIRES: 90-12-01
ICL DRS300 (under
DRS/NX, Version
3, Level 1)
Same as Host
DDC International
A/S
DACS-386/UNIX,
Version 4.4
(#891027S1.10186)
EXPIRES: 90-12-01
RC900 (under UNIX
V, Release 1.0.4)
Same as Host
DDC-I, Inc.
DACS-80186,
Version 4.3
(#890324S1.10067)
EXPIRES: 90-12-01
MicroVAX II
(under MicroVMS
4.6)
Intel 80186 iSBC
186/03A (bare
machine)
DEC family of
VAX, VAXstation &
MicroVAX
computers (under
MicroVMS 4.6 and
VAX/VMS 4.6 &
5.0)
Intel 8086 iSBC
86/05A (bare
machine)
DEC family of
VAX, VAXstation &
MicroVAX
computers (under
MicroVMS 4.6 and
VAX/VMS 4.6 &
5.0)
Intel 80186 iSBC
186/03A (bare
machine)
DEC family of
VAX, VAXstation &
MicroVAX
computers (under
Intel 80286 iSBC
286/12 (bare
machine)
*Derived
DDC-I, Inc.
DACS-8086,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-80186,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-80286,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
MicroVMS 4.6 and
VAX/VMS 4.6 &
5.0)
*Derived
DDC-I, Inc.
DACS-80186 with
Hard Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel iSBC
186/03A (80186)
(bare machine)
*Derived
DDC-I, Inc.
DACS-8086 with
Hard Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel iSBC 86/05A
(8086) (bare
machine)
*Derived
DDC-I, Inc.
DACS-80286 with
Hard Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel iSBC 286/12
(80286) (bare
machine)
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel iSBC 286/12
(80286) in
Protected Mode
(bare machine)
MicroVAX II
(under MicroVMS
4.6)
Intel Multibus I
80386 iSBC 386/21
(bare machine)
*Derived
DDC-I, Inc.
DACS-80286
Protected Mode
with Hard
Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10067)
EXPIRES: 90-12-01
DDC-I, Inc.
DACS-80386
Protected Mode,
Version 4.3
(#890324S1.10068)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-80386
Protected Mode,
Version 4.3
(BASE
#890324S1.10068)
EXPIRES: 90-12-01
DEC family of
VAX, VAXstation &
MicroVAX
computers (under
MicroVMS 4.6 and
VAX/VMS 4.6 &
5.0)
Intel Multibus I
80386 isBC 386/21
& Intel Multibus
II 80386 iSBC
386/116 (bare
machine)
*Derived
DDC-I, Inc.
DACS-80386 with
Hard Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10068)
EXPIRES: 90-12-01
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel Multibus II
iSBC 386/116
(80386) (bare
machine)
Complete DEC
family of VAX,
VAXstation, and
MicroVAX
computers (under
VMS 4.6, MicroVMS
4.6 & VMS 5.0)
Intel Multibus I
iSBC 386/21
(80386) (bare
machine)
IBM PS/2 Models
70 & 80 (under
AIX 1.1)
Any Host
Compaq Deskpro
386--all models
(under 386/ix
Release 1.0.6)
Any Host
Intel System
302--all models
(under UNIX
System V/386
Release 3.2)
Any Host
*Derived
DDC-I, Inc.
DACS-80386
Protected Mode
with Hard
Deadline
Scheduling RTS,
Version 4.3
(BASE
#890324S1.10068)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-AIX/PS2,
Version 4.4
(BASE
#891027S1.10185)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-386/UNIX,
Version 4.4.1
(BASE
#891027S1.10185)
EXPIRES: 90-12-01
*Derived
DDC-I, Inc.
DACS-386/UNIX,
Version 4.4.1
(BASE
#891027S1.10185)
EXPIRES: 90-12-01
Digital Equipment
Corporation
VAX Ada, Version
2.0
(#890127S1.10033)
EXPIRES: 90-12-01
*Derived
Digital Equipment
Corporation
Vax Ada, Version
2.0
(BASE
#890127S1.10033)
EXPIRES: 90-12-01
Digital Equipment
Corporation
VAX Ada, Version
2.0
(#890127S1.10034)
EXPIRES: 90-12-01
*Derived
Digital Equipment
Corporation
VAX Ada, Version
2.0
(BASE
#890127S1.10034)
EXPIRES: 90-12-01
VAX 8800 (under
VMS, Version 5.0)
Same as Host
MicroVAX I, II,
2000, 3500 &
3600; VAXstation
II, 2000, 3200,
3500 & 8000;
VAXserver 3500,
3600, 3602, 6210
& 6220;
VAX-11/730, 750,
780 & 785; VAX
6210, 6220, 6230,
6240, 8200, 8250,
8300, 8350, 8500,
8530, 8550, 8600,
8650, 8700, 8800,
8810, 8820, 8830,
8840, 8842, 8974
& 8978; and
Raytheon Military
VAX Computer
Model 860 (under
VMS, Version 5.0)
Any Host
VAX 8800 (under
VMS, Version 5.0)
MicroVAX II
(under VAXELN
Toolkit Version
3.2, in
combination with
VAXELN Ada
Version 2.0)
MicroVAX I, II,
2000, 3500 &
3600; VAXstation
II, 2000, 3200,
3500 & 8000;
VAXserver 3500,
3600, 3602, 6210
& 6220;
VAX-11/730, 750,
780 & 785; VAX
6210, 6220, 6230,
6240, 8200, 8250,
8300, 8350, 8500,
8530, 8550, 8600,
MicroVAX I, II,
2000, 3500 &
3600; VAX-11/725,
730 & 750; IVAX
620 & 630; KA620
& 800; rtVAX
1000, 3200, 3500,
3600, 8550 &
8700; and VAX
6210, 6220, 6230,
6240, 8500, 8530,
8550, 8700, 8800,
8810 & 8820
(under VAXELN
8650, 8700, 8800,
8810, 8820, 8830,
8840, 8842, 8974
& 8978; and
Raytheon Military
VAX Computer
Model 860 (under
VMS, Version 5.0)
Toolkit Version
3.2, in
combination with
VAXELN Ada
Version 2.0)
Elxsi
Elxsi VADS
Version 5.6
(#890712W1.10115)
EXPIRES: 90-12-01
Elxsi 6400 (under
ENIX 4.3 BSD
12.1)
Same as Host
Elxsi
Elxsi VADS
Version 5.6
(#890712W1.10116)
EXPIRES: 90-12-01
Elxsi 6400 (under
ENIX SYSTEM V
12.1)
Same as Host
Encore Computer
Corporation
Encore Verdix
Ada Development
System, Version
5.5
(#890727S1.10127)
EXPIRES: 90-12-01
Encore Multimax
320 (under Umax
4.2, Version
R3.3)
Same as Host
Encore Computer
Corporation
Encore Verdix
Ada Development
System, Version
5.5
(#890727S1.10128)
EXPIRES: 90-12-01
Encore Multimax
320 (under Mach,
Version 0.5 Beta)
Same as Host
Encore Computer
Corporation
Encore Verdix
Ada Development
System, Version
5.5
(#890727S1.10129)
EXPIRES: 90-12-01
Encore Multimax
320 (under Umax
V, Version R2.2)
Same as Host
Gould/Computer
Systems Inc.
APLEX Ada
Compiler,
Revision 2.2
(#890418W1.10069)
Gould/Encore
PowerNode Model
9080 (under
UTX/32 Revision
2.1)
Same as Host
EXPIRES: 90-12-01
*Derived
Gould/Computer
Systems Inc.
APLEX Ada
Compiler
Revision 2.2
(BASE
#890418W1.10069)
EXPIRES: 90-12-01
Gould/Computer
Systems Inc.
APLEX Ada
Compiler,
Revision 2.2
(#890418W1.10070)
EXPIRES: 90-12-01
*Derived
Gould/Computer
Systems Inc.
APLEX Ada
Compiler
Revision 2.2
(BASE
#890418W1.10070)
EXPIRES: 90-12-01
Gould/Computer
Systems Inc.
APLEX Ada
Compiler,
Revision 2.2
(#890418W1.10071)
EXPIRES: 90-12-01
*Derived
Gould/Computer
Systems Inc.
APLEX Ada
Compiler
Revision 2.2
(BASE
#890418W1.10071)
EXPIRES: 90-12-01
Gould/Computer
Systems Inc.
APLEX Ada
Compiler,
Revision 2.2
Gould/Encore
PowerNode Models
90xx, 60xx, and
Gould/Encore
CONCEPT/32 Models
67xx (under
UTX/32 Revision
2.1)
Any Host
Gould/Encore
PowerNode Model
9080 (under
UTX/32 Revision
2.1)
Gould/Encore
CONCEPT/32 Model
6744 (bare
machine, with Ada
Real Time
Executive)
Gould/Encore
PowerNode Models
90xx & 60xx, and
Gould/Encore
CONCEPT/32 Models
67xx (under
UTX/32 Revision
2.1)
Gould/Encore
PowerNode Models
90xx & 60xx, and
Gould/Encore
CONCEPT/32 Models
97xx & 67xx (bare
machine, with Ada
Real Time
Executive)
Gould/Encore NP1
Model 4050 (under
UTX/32 Revision
3.1)
Same as Host
Gould/Encore NP1
Models 40xx
(under UTX/32
Revision 3.1)
Any Host
Gould/Encore
CONCEPT/32 Model
9780 (under
MPX-32 Revision
3.4U02)
Same as Host
(#890418W1.10072)
EXPIRES: 90-12-01
*Derived
Gould/Computer
Systems Inc.
APLEX Ada
Compiler
Revision 2.2
(BASE
#890418W1.10072)
EXPIRES: 90-12-01
Harris Corp.
Harris Ada,
Version 5.0
(#890118W1.10016)
EXPIRES: 90-12-01
*Derived
Harris Corp.
Harris Ada,
Version 5.0
(BASE
#890118W1.10016)
EXPIRES: 90-12-01
Harris Corp.
Harris Ada,
Version 5.0
(#890118W1.10017)
EXPIRES: 90-12-01
*Derived
Harris Corp.
Harris Ada,
Version 5.0
(BASE
#890118W1.10017)
EXPIRES: 90-12-01
Harris
Corporation,
Computer Systems
Division
Harris Ada,
Version 5.0
(#890627W1.10103)
EXPIRES: 90-12-01
Gould/Encore
CONCEPT/32 Models
97xx, 67xx & 98xx
(under MPX-32
Revision 3.4U02)
Any Host
Harris NH-3800
(under CX/UX,
4.0)
Same as Host
Harris NH-3800,
NH-3400 & NH-1200
(under CX/UX 4.0,
and under CX/RT
4.0)
Any Host
Harris HCX-9
(under CX/UX,
4.0)
Harris NH-3800
(under CX/UX,
4.0)
Harris HCX-2300,
HCX-2500,
HCX-2550,
HCX-2900,
HCX-7100,
HCX-7201,
HCX-7202; Harris
NH-7100 & NH-7200
(under CX/UX 4.0,
and under CX/RT
4.0)
Harris NH-3800,
NH-3400, NH-1200
(under CX/UX 4.0,
and under CX/RT
4.0)
Harris H1000
(under VOS 8.1)
Same as Host
*Derived
Harris
Corporation,
Computer Systems
Division
Harris Ada,
Version 5.0
(BASE
#890627W1.10103)
EXPIRES: 90-12-01
Harris
Corporation,
Computer Systems
Division
Harris Ada,
Version 5.0
(#890627W1.10104)
EXPIRES: 90-12-01
*Derived
Harris
Corporation,
Computer Systems
Division
Harris Ada,
Verison 5.0
(BASE
#890627W1.10104)
EXPIRES: 90-12-01
Hewlett Packard
Company
HP 9000 Series
300 Ada
Compiler,
Version 4.35
(#890504W1.10078)
EXPIRES: 90-12-01
*Derived
Hewlett Packard
Company
HP 9000 Series
300 Ada
Compiler,
Version 4.35
(BASE
#890504W1.10078)
EXPIRES: 90-12-01
Hewlett Packard
Company
Harris H60, H700,
H800, H900,
H1000, H1100,
H1200, H1500 &
H1600 (under VOS
8.1)
Any Host
Harris HCX-2900
(under CX/UX 4.1)
Same as Host
Harris HCX-2300,
HCX-2500,
HCX-2550 &
HCX-2900 (under
CX/UX 4.1 & CX/RT
4.1)
Any Host
HP 9000 Series
300 Model 350
(under HP-UX,
Version 6.5)
Same as Host
HP 9000 Series
300 Models 350,
332, 330 & 320
(under HP-UX,
Version 7.0)
Each Host,
self-targeted
HP 9000 Series
300 Model 370
Same as Host
HP 9000 Series
300 Ada
Compiler,
Version 4.35
(#890504W1.10079)
EXPIRES: 90-12-01
*Derived
Hewlett Packard
Company
HP 9000 Series
300 Ada
Compiler,
Version 4.35
(BASE
#890504W1.10079)
EXPIRES: 90-12-01
(under HP-UX,
Versin 6.5)
HP 9000 Series
300 Models 370,
360 & 340 (under
HP-UX, Version
7.0)
Each Host,
self-targeted
Hewlett Packard
Company
HP 9000 Series
800 Compiler,
Version 4.35
(#891019W1.10178)
EXPIRES: 90-12-01
HP 9000 Series
800 Model 850
(under HP-UX,
Version A.B3.10
(release 3.1))
Same as Host
INTEL Corporation
Ada386 Version
3.23
(#890602I1.10136)
EXPIRES: 90-12-01
VAX 8350 (under
VMS 5.0-2)
Intel 386-120
(80386/387) board
(bare machine)
Intel Corporation
iPSC/2 Ada,
Release 1.1
(#891116W1.10191)
EXPIRES: 90-12-01
iPSC/2 Parallel
Supercomputer,
System Resource
Manager (under
Unix System V,
Release 3.2)
iPSC/2 Parallel
Supercomputer,
CX-1 nodes (under
NX/2)
InterACT
Corporation
InterACT Ada
1750A Compiler
System Release
3.3
(#891116S1.10232)
EXPIRES: 90-12-01
VAX-11/785 (under
VMS 4.5)
Fairchild
9450/1750A in a
Hewlett Packard
64000 (bare
machine)
InterACT
Corporation
InterACT Ada
MIPS
Cross-Compiler
System Release
MicroVAX 3100
Cluster (under
VMS 5.2)
MIPS R2000 on an
Integrated
Solutions, Inc.,
Advantedge 2000
board (bare
machine)
1.0
(#891116S1.10233)
EXPIRES: 90-12-01
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
AIX/RT Ada
Compiler,
Version 1.1.1
(#890420W1.10066)
EXPIRES: 90-12-01
*Derived
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
AIX/RT Ada
Compiler,
Version 1.2
(BASE
#890420W1.10066)
EXPIRES: 90-12-01
*Derived
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
AIX/RT Ada
Compiler,
Version 1.1.2
(BASE
#890420W1.10066)
EXPIRES: 90-12-01
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
VM/CMS Ada
Compiler,
Version 2.1.1
(#890420W1.10073)
IBM RT PC
6150-125 (under
AIX, Release 2.2)
Same as Host
IBM RT PC
6150-125 (under
AIX, Release 2.2)
Same as Host
IBM RT 6150-125
(under AIX
Release 2.2)
Same as Host
IBM 3083 (under
VM/HPO Release
4.2)
Same as Host
EXPIRES: 90-12-01
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
MVS Ada
Compiler,
Version 2.1.1
(#890420W1.10074)
EXPIRES: 90-12-01
IBM 4381 (under
MVS/XA Release
2.7)
Same as Host
International
Business Machines
Corporation
IBM Development
System for the
Ada Language,
CMS/MVS Ada
Cross Compiler,
Version 2.1.1
(#890420W1.10075)
EXPIRES: 90-12-01
IBM 3083 (under
VM/HPO Release
4.2)
IBM 4381 (under
MVS/XA Release
2.7)
International
Business Machines
Corporation
IBM Development
System for the
Ada Language
AIX/RT
Follow-on,
Version 1.1
(#891129W1.10198)
EXPIRES: 90-12-01
IBM RT Follow-on
(under AIX 3.1)
Same as Host
Irvine Compiler
Corporation
ICC Ada Release
6.0.0
(#891212W1.10203)
EXPIRES: 90-12-01
HP 9000 Model 350
(under HP-UX
Release 6.2)
HP 64000 UX with
68020 Emulation
Pod (bare
machine)
Irvine Compiler
Corporation
ICC Ada Release
6.0.0
(#891212W1.10204)
EXPIRES: 90-12-01
MicroVAX 2000
(under MicroVMS
4.7)
ICC Simulator for
Intel i80960MC,
executing on the
Host (bare
machine)
Irvine Compiler
Corporation
HP 9000 Model 350
(under HP-UX
Same as Host
ICC Ada Release
6.0.0
(#891212W1.10205)
EXPIRES: 90-12-01
Release 6.2)
Irvine Compiler
Corporation
ICC Ada Release
6.0.0
(#891212W1.10206)
EXPIRES: 90-12-01
HP 9000 Model 825
(under HP-UX
Release 2.1)
Same as Host
Irvine Compiler
Corporation
ICC Ada Release
6.0.0
(#891212W1.10207)
EXPIRES: 90-12-01
Sun 3/50 (under
SunOS Release
4.0)
Same as Host
Irvine Compiler
Corporation
ICC Ada Release
6.0.0
(#891212W1.10208)
EXPIRES: 90-12-01
ISI Optimum V
VME-68K30 (under
4.3 BSD UNIX
Release 5.0.3)
Same as Host
KRUPP ATLAS
ELEKTRONIK GMBH
KRUPP ATLAS
ELEKTRONIK Ada
Compiler VVME
1.81
(#891124I1.10235)
EXPIRES: 90-12-01
VAX 6310 (under
VMS 5.1)
KRUPP ATLAS
ELEKTRONIK GMBH
MPR 2300 (under
EOS 2300 Version
1.4)
Loral/Rolm
Mil-Spec
Computers
ADE Revision
3.01
(#890804S1.10141)
EXPIRES: 90-12-01
Data General MV
10000 (under
AOS/VS 7.64)
HAWK/32 (under
AOS/VS 7.64)
Loral/Rolm
Mil-Spec
Computers
ADE Revision
3.01
(#890804S1.10142)
EXPIRES: 90-12-01
Data General MV
10000 (under
AOS/VS 7.64)
HAWK/32 (under
ARTS/32 Revision
2.71)
Meridian Software
Systems, Inc.
AdaVantage,
Apple Macintosh
II (with Floating
Point
Same as Host
Version 4.0
(#890130W1.10237)
EXPIRES: 90-12-01
Co-Processor)
(under System
6.0.3)
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10049)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10049)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10050)
EXPIRES: 90-12-01
IBM PS/2 Model 60
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaGraduate,
Version 3.0
(BASE
#890405W1.10050)
EXPIRES: 90-12-01
IBM PS/2 Model 60
(with
Floating-Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10050)
EXPIRES: 90-12-01
IBM PS/2 Model 60
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10051)
EXPIRES: 90-12-01
IBM PS/2 Model 30
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Same as Host
*Derived
Meridian Software
IBM PS/2 Model 30
Same as Host
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10051)
EXPIRES: 90-12-01
(with Floating
Point
Co-Processor)
(under IBM PC-DOS
3.30)
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10052)
EXPIRES: 90-12-01
ITT XTRA/286
(with Floating
Point
Co-Processor)
(under MS-DOS
3.20)
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10052)
EXPIRES: 90-12-01
ITT XTRA/286
(with Floating
Point
Co-Processor)
(under IBM MS-DOS
3.20)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10053)
EXPIRES: 90-12-01
SCI 302 (with
Floating Point
Co-Processor)
(under MS-DOS
3.30)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10054)
EXPIRES: 90-12-01
SCI 302 (with
Floating Point
Co-Processor)
(under IX 1.0.6)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10055)
EXPIRES: 90-12-01
SCI 303 (with
Floating Point
Co-Processor)
(under IX 1.0.6)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10056)
EXPIRES: 90-12-01
Sun 3/60 (under
SunOS Version
4.1)
Same as Host
Sun 3/60 (under
SunOS Version
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10056)
EXPIRES: 90-12-01
4.1)
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10057)
EXPIRES: 90-12-01
Sun 3/260 (under
SunOS Version
4.1)
Same as Host
Sun 3/260 (under
SunOS Version
4.1)
Same as Host
Zenith Z-248
Model ZW-248-82
(with Floating
Point
Co-Processor)
(under MS-DOS
3.10)
Same as Host
Zenith Z-248
Model ZW-248-82
(with Floating
Point
Co-Processor)
(under IBM MS-DOS
3.10)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10117)
EXPIRES: 90-12-01
Ardent Titan P2
(under
Ardent/Unix,
Version 2.1)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10118)
EXPIRES: 90-12-01
Multiflow Trace
300 (under
Trace/Unix,
Version 4.1.5)
Same as Host
Meridian Software
Apple Macintosh
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10057)
EXPIRES: 90-12-01
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(#890405W1.10058)
EXPIRES: 90-12-01
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890405W1.10058)
EXPIRES: 90-12-01
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10119)
EXPIRES: 90-12-01
II (with Floating
Point
Co-Processor)
(under System
6.0.3)
Meridian Software
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10121)
EXPIRES: 90-12-01
Apple Macintosh
SE 30 (under
System 6.0.3)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10122)
EXPIRES: 90-12-01
DECstation 3100
(under Ultrix,
Version 3.0)
Same as Host
DECstation 3100
(under Ultrix,
Version 3.0)
Same as Host
IBM PS/2 Model 70
(under XENIX,
Version 2.3.2)
Same as Host
IBM PS/2 Model 80
(with
Floating-Point
Co-Processor)
(under XENIX,
Version 2.3.2)
Same as Host
Meridian Software
Systems, Inc.
AdaVantage,
Version 4.0
(#900130W1.10238)
EXPIRES: 90-12-01
Apple Macintosh
SE 30 (under
System 6.0.3)
Same as Host
MIPS Computer
Systems
MIPS M/120 (under
RISC/os 4.0)
Same as Host
*Derived
Meridian Software
Systems, Inc.
AdaVantage
Version 4.0
(BASE
#890719W1.10122)
EXPIRES: 90-12-01
Meridian Software
Systems, Inc.
AdaVantage
Version 3.0
(#890719W1.10123)
EXPIRES: 90-12-01
*Derived
Meridian Software
Systems, Inc.
AdaVantage,
Version 3.0
(BASE
#890719W1.10123)
EXPIRES: 90-12-01
MIPS ADA,
Version 2.10
(#890614W1.10098)
EXPIRES: 90-12-01
*Derived
MIPS Computer
Systems
MIPS ADA,
Version 2.10
(BASE
#890614W1.10098)
EXPIRES: 90-12-01
MIPS M/500,
M/800, M/1000,
M/2000, RC2030 &
RS2030 (under
RISC/os 4.0)
Each Host,
self-targeted
MIPS M/120 (under
RISC/os 4.0)
R3200-6 CPU board
(bare machine)
MIPS M/120,
M/500, M/800,
M/1000, M/2000,
RC2030 & RS2030
(under RISC/os
4.0)
R3200-6, R3200-8,
R2600 (2601),
R2800 (2801) CPU
boards (bare
machines)
Motorola, Inc.
Motorola VME
Delta Series
TeleGen2
Compilation
System Version
1.4
(#890829W1.10144)
EXPIRES: 90-12-01
Motorola Delta
Model 2616
(MVME132XT,
68020/68881)
(under Motorola
SYSTEM V/68
Version V3.5)
Same as Host
Motorola, Inc.
Motorola VME
Delta Series
TeleGen2
Compilation
System Version
1.4
(#890829W1.10145)
EXPIRES: 90-12-01
Motorola Delta
Model 2616
(MVME132XT,
68020/68881)
(under Motorola
SYSTEM V/68
Version V3.5)
Motorola
MVME133A-20
(MC68020) (bare
machine)
New York
University
NYU Ada/Ed,
Version 1.10
Sun-3/60 (under
Sun UNIX 4.2 Rel
3.4)
Same as Host
MIPS Computer
Systems
MIPS ASAPP,
Version 2.10
(#890614W1.10099)
EXPIRES: 90-12-01
*Derived
MIPS Computer
Systems
MIPS ASAPP,
Version 2.10
(BASE
#890614W1.10099)
EXPIRES: 90-12-01
(#890523W1.10085)
EXPIRES: 90-12-01
New York
University
NYU Ada/Ed,
Version 1.10
(#890523W1.10086)
EXPIRES: 90-12-01
VAX-8600 (under
VMS version 4.7)
Same as Host
NIPPON TELEGRAPH
and TELEPHONE
CORPORATION
AdaDIPS, Version
1.0
(#890901S1.10132)
EXPIRES: 90-12-01
NTT DIPS V20
(under DIPS-UX
(V0))
Same as Host
Proprietary
Software Systems,
Inc.
PSS Ada Compiler
VAX/VMS, Version
TV-01.000
(#890710I1.10120)
EXPIRES: 90-12-01
VAX 8350 (under
VMS Version 4.7)
Same as Host
PYRAMID
TECHNOLOGY
CORPORATION
Pyramid Ada,
Version 5.0
(#890926W1.10174)
EXPIRES: 90-12-01
Pyramid 9000
(under Pyramid
OSX 5.0)
Same as Host
PYRAMID
TECHNOLOGY
CORPORATION
Pyramid Ada,
Version 5.0
(#890926W1.10175)
EXPIRES: 90-12-01
Pyramid MIServer
(under Pyramid
OSX 5.0b)
Same as Host
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
(#890113W1.10018)
EXPIRES: 90-12-01
IBM PC XT (under
MS DOS 3.3)
Same as Host
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
Compaq Deskpro
286 (under MS DOS
3.1)
Same as Host
(#890113W1.10019)
EXPIRES: 90-12-01
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
(#890113W1.10020)
EXPIRES: 90-12-01
Compaq Deskpro
386/25 (under MS
DOS 3.31)
Same as Host
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
(#890113W1.10021)
EXPIRES: 90-12-01
PC's Limited 386
(under MS DOS
3.1)
Same as Host
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
(#890113W1.10022)
EXPIRES: 90-12-01
Compaq Deskpro
386/25 (under MS
DOS 3.31/Phar
Lap)
Same as Host
R.R. Software,
Inc.
JANUS/Ada,
Version 2.1.1
(#890113W1.10023)
EXPIRES: 90-12-01
PC's Limited 386
(under MS DOS
3.1/Phar Lap)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10152)
EXPIRES: 90-12-01
IBM PS/2 Model 70
(under MS DOS
3.3/Phar Lap)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10153)
EXPIRES: 90-12-01
Unisys 386 (under
SCO Xenix 2.3.2)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10154)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(under SCO Xenix
2.2.2)
Same as Host
R.R. Software,
Inc.
Zenith
ZFX-0248-50
Same as Host
JANUS/Ada
Version 2.1.3
(#890919W1.10155)
EXPIRES: 90-12-01
(under MS DOS
3.3)
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10156)
EXPIRES: 90-12-01
Zenith Z-386/25
(under
Interactive Unix
2.1)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10157)
EXPIRES: 90-12-01
PC's Limited
386-80386 (under
MS DOS 3.1/Phar
Lap)
PC's Limited
386-8086 (under
MS DOS 3.1)
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10158)
EXPIRES: 90-12-01
IBM PS/2 Model
70-80386 (under
MS DOS 3.3/Phar
Lap)
IBM PS/2 Model
70-8086 (under MS
DOS 3.3)
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10159)
EXPIRES: 90-12-01
Northgate 386
(under MS DOS
4.01)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10168)
EXPIRES: 90-12-01
Northgate 386
(under SCO Unix
3.2)
Same as Host
R.R. Software,
Inc.
JANUS/Ada
Version 2.1.3
(#890919W1.10169)
EXPIRES: 90-12-01
Hewlett Packard
Vectra RS/20C
(under SCO Xenix
2.3.2)
Same as Host
Rational
Rational
Environment,
Version D_12_0_0
(#890601W1.10084)
EXPIRES: 90-12-01
R1000 Series 200
Model 10 (under
Rational
Environment
Version D_12_0_0)
Same as Host
Rational
MIL-STD-1750A
Cross
Development
Facility,
Version 5
(#890712W1.10111)
EXPIRES: 90-12-01
R1000 Series 200
Model 20 (under
Rational
Environment
Version D_11_0_8)
Mikros MKS
1750A/SO (bare
machine)
Rational
MC68020 Family
Cross
Development
Facility,
Version 5
(#890712W1.10112)
EXPIRES: 90-12-01
R1000 Series 200
Model 20 (under
Rational
Environment
Version D_11_0_8)
Motorola MVME135
(MC68020) (bare
machine)
Rational
MC68020/OS-2000
Cross
Development
Facility,
Version 5
(#890712W1.10113)
EXPIRES: 90-12-01
R1000 Series 200
Model 20 (under
Rational
Environment
Version D_11_0_8)
Motorola 68020 in
Philips PG2100
(under OS-2000
Version 2.2)
Rational
VAX/VMS Cross
Development
Facility,
Version 5
(#890712W1.10114)
EXPIRES: 90-12-01
R1000 Series 200
Model 20 (under
Rational
Environment
Version
D_11__0_8)
DEC VAXstation II
(under VMS 4.7)
Rockwell
International
Corporation
DDC-Based
Ada/CAPS
Compiler System,
Version 4.1
(#891101W1.10181)
EXPIRES: 90-12-01
VAX 8700 (under
VMS 5.2)
CAPS/AAMP1 (bare
machine)
Rockwell
International
Corporation
DDC-Based
Ada/CAPS
Compiler System,
Version 4.1
(#891101W1.10182)
EXPIRES: 90-12-01
VAXstation 3100
Model 30 (under
VMS 5.2)
CAPS/AAMP2 (bare
machine)
SD_Scicon plc
XD Ada MC68020
T1.0-02V
(#890321N1.10041)
EXPIRES: 90-12-01
VAX Cluster
(comprising a VAX
8600 and 7
MicroVAX IIs)
(under VMS 5.0)
MC68020 on the
MVME 133 XT board
(bare machine)
*Derived
SD_Scicon plc
XD Ada MC68020
Version 1.0
(BASE
#890321N1.10041)
EXPIRES: 90-12-01
VAX Cluster,
comprising a VAX
8600 & 7 MicroVAX
IIs (under VMS
5.0)
Motorola
MVME133XT
(MC68020)
SD_Scicon plc
XD Ada
MIL-STD-1750A
T1.0-05A
(#890920N1.10170)
EXPIRES: 90-12-01
VAX Cluster
(comprising a VAX
8600 & 7 MicroVAX
IIs) (under VMS
5.1)
Fairchild F9450
on a SBC-50 board
(MIL-STD-1750A)
(bare machine)
Siemens AG
Siemens BS 2000
Ada Compiler
V2.0
(#890306I1.10059)
EXPIRES: 90-12-01
Siemens 7.590G
(under
BS2000/V9.0)
Same as Host
Siemens 7.530,
7.531, 7.536,
7.541, 7.550,
7.551, 7.560,
7.561, 7.570,
7.571, 7.580,
7.590, 7.700
(under
BS2000/V7.5,
/V7.6, /V8.0,
/V8.5, /V9.0,
/V9.2 & /V9.5)
Any Host
Iris-4D/210
(under IRIX
Release 4D-3.2)
Same as Host
Iris-4D/240, /220
& /120 (under
IRIX Release
Each Host,
self-targeted
*Derived
Siemens AG
Siemens BS2000
Ada Compiler
V2.0
(BASE
#890306I1.10059)
EXPIRES: 90-12-01
Silicon Graphics
Computer Systems
4D Ada, Version
2.0
(#890613W1.10100)
EXPIRES: 90-12-01
*Derived
Silicon Graphics
Computer Systems
4D Ada, Version
2.0
(BASE
#890613W1.10100)
EXPIRES: 90-12-01
4D-3.2)
Silicon Graphics
Computer Systems
4D Ada, Version
2.0
(#890613W1.10101)
EXPIRES: 90-12-01
Iris-4D/70 (under
IRIX Release
4D-3.2)
Same as Host
Iris-4D/50 & /80
(under IRIX
Release 4D-3.2)
Each Host,
self-targeted
Silicon Graphics
Computer Systems
4D Ada, Version
2.0
(#890613W1.10102)
EXPIRES: 90-12-01
Iris-4D/20 (under
IRIX Release
4D-3.2)
Same as Host
Software
Leverage, Inc.
ParallelLeveraged Ada,
Version S5.5.2
(#890628W1.10106)
EXPIRES: 90-12-01
Sequent Symmetry
S81 (under Dynix
3.0.12)
Same as Host
Sequent Symmetry
S27 (under Dynix
3.0.12)
Same as Host
Prime EXL 1200
Series; and
UNISYS 6000/70 &
/80 (under Dynix
3.0.12)
Each Host,
self-targeted
*Derived
Silicon Graphics
Computer Systems
4D Ada, Version
2.0
(BASE
#890613W1.10101)
EXPIRES: 90-12-01
*Derived
Software
Leverage, Inc.
ParallelLeveraged Ada,
Version S5.5.2
(BASE
#890628W1.10106)
EXPIRES: 90-12-01
*Derived
Software
Leverage, Inc.
ParallelLeveraged Ada,
Version S5.5.2
(BASE
#890628W1.10106)
EXPIRES: 90-12-01
SYSTEAM KG
SYSTEAM Ada
Compiler
VAX/VMS, Version
V1.81
(#890131I1.10035)
EXPIRES: 90-12-01
VAX 8530 (under
VMS 4.6)
Same as Host
SYSTEAM KG
SYSTEAM Ada
Compiler VAX/VMS
x MC68020/0S-9,
Version 1.81
(#890329I1.10076)
EXPIRES: 90-12-01
VAX 8350 (under
VMS 4.7)
KWS EB68020
(under OS-9/68020
Version 2.1)
SYSTEAM KG
SYSTEAM Ada
Compiler VAX/VMS
x MC68020/BARE
(#890825I1.10176)
EXPIRES: 90-12-01
VAX 8530 (under
VMS, Version 4.7)
Motorola
MVME133XT
(MC68020/68882)
(bare machine)
SYSTEAM KG
SYSTEAM Ada
Compiler
CADMUS/MUNIX
Version 1.81
(#890825I1.10189)
EXPIRES: 90-12-01
Cadmus 9921/4
(under Munix,
Version V.3-3.1)
Same as Host
SYSTEAM KG
SYSTEAM Ada
Compiler
S.7000/BS2000
Version 1.81
(#890831I1.10188)
EXPIRES: 90-12-01
Siemens 7.530-B
(under BS2000,
Version 7.5A)
Same as Host
SYSTEAM KG
SYSTEAM Ada
Compiler
SUN/SUNOS,
Version 1.81
(#891102I1.10200)
EXPIRES: 90-12-01
Sun 3/60 (under
SunOS, Version
4.0.3)
Same as Host
Tandem Computers
Incorporated
Tandem Ada,
Version T9270C30
(#890621W1.10105)
Tandem NonStop
VLX (under
GUARDIAN 90,
Version C20)
Same as Host
EXPIRES: 90-12-01
*Derived
Tandem Computers
Incorporated
Tandem Ada,
Version T9270C30
(BASE
#890621W1.10105)
EXPIRES: 90-12-01
Tandem NonStop
VLX, TXP, II &
CLX (under
GUARDIAN 90,
Version C20)
Any Host
Tartan
Laboratories
Incorporated
Tartan Ada
Sun/Sun, Version
2.1
(#890412I1.10082)
EXPIRES: 90-12-01
Sun 3/60 (under
Sun OS Version
3.5)
Same as Host
Tartan
Laboratories
Incorporated
Tartan Ada
VMS/1750A,
Version 2.11
(#890621I1.10148)
EXPIRES: 90-12-01
VAXstation 3200
(under MicroVMS
4.7)
Fairchild F9450
(MIL-STD-1750A)
(bare machine)
All members of
the VAX family of
computers (under
MicroVMS 4.7, VMS
4.7 & VMS 5.0)
Fairchild F9450
(MIL-STD-1750A)
VAXstation 3200
(under MicroVMS
4.7)
Motorola MVME134
(68020/68881)
(bare machine)
All members of
the VAX family of
computers (under
MicroVMS 4.7, VMS
Motorola MVME134
(68020/68881)
(bare machine)
*Derived
Tartan
Laboratories
Incorporated
Tartan Ada
VMS/1750A
Version 2.11
(BASE
#890621I1.10148)
EXPIRES: 90-12-01
Tartan
Laboratories
Incorporated
Tartan Ada
VMS/68K, Version
2.1
(#890621I1.10149)
EXPIRES: 90-12-01
*Derived
Tartan
Laboratories
Incorporated
Tartan Ada
VMS/68K Version
2.1
(BASE
#890621I1.10149)
EXPIRES: 90-12-01
4.7 & VMS 5.0)
Tartan
Laboratories
Incorporated
VMS Ada960MC
Compiler R1.0
(#890621I1.10150)
EXPIRES: 90-12-01
VAXstation 3200
(under MicroVMS
4.7)
Intel 80960MC on
an Intel
EXV80960MC board
(bare machine)
All members of
the VAX family of
computers (under
MicroVMS 4.7, VMS
4.7 & VMS 5.0)
Intel 80960MC on
an Intel
EXV80960MC board
(bare machine)
Tartan
Laboratories
Incorporated
SUN Ada960MC
Compiler V2.0
(#890621I1.10151)
EXPIRES: 90-12-01
SUN 3/50 (under
SunOS 3.5)
Intel 80960MC on
an Intel
EXV80960MC board
(bare machine)
TELESOFT
TeleGen2 Ada
Development
System for
VAX/VMS, Version
3.23
(#890409W1.10042)
EXPIRES: 90-12-01
VAXserver 3602
(under VAX/VMS
Version 5.0)
Same as Host
All MicroVAX I &
II; all MicroVAX
2000, 3100 (incl.
3100/10 &
3100/20), 3300,
3400, 3500, 3600,
3800 & 3900; all
VAXstation I &
II; all
VAXstation 2000,
3100, 3200, 3500
(incl. 3520 &
Any Host
*Derived
Tartan
Laboratories
Incorporated
VMS Ada960MC
Compiler R1.0
(BASE
#890621I1.10150)
EXPIRES: 90-12-01
*Derived
TELESOFT
TeleGen2 Ada
Development
System for
VAX/VMS Version
3.23
(BASE
#890409W1.10042)
EXPIRES: 90-12-01
3540); all
VAXserver 3100,
3300, 3400, 3500,
3600 (incl.
3602), 3800,
3900, 6000 (incl.
6000-210, 220,
310, 320, 410,
420); all
VAX-11/725,
11/730, 11/750,
11/780, 11/785;
all VAX 6000-200
(incl. 6000-210,
220, 230, 240),
6000-300 (incl.
6000-310, 320,
330, 340, 350,
360), 6000-400
(incl. 6000-410,
420, 430, 440,
450, 460), 8200
(incl. 8250),
8300 (incl. 8350),
8500 (incl. 8530,
8550), 8600 (incl.
8650), 8700, 8800
(incl. 8810, 8820,
8830, 8840, 8842),
8900 (incl. 8974,
8979) (under
VAX/VMS Versions
5.0, 5.1 & 5.2)
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#890409W1.10043)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX Version
4.2 Release 3.5)
Same as Host
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#890409W1.10044)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX Version
4.2 Release 3.5)
Motorola
MVME133A-20
(MC68020) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System, Version
Sun-3/280 (under
Sun UNIX Version
4.2 Release 3.5)
Motorola MVME101
(MC68020) (bare
machine)
1.4
(#890409W1.10060)
EXPIRES: 90-12-01
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#890409W1.10061)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX Version
4.2 Release 3.5)
Motorola MVME117
(MC68010) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System for VAX
to E68K, Version
3.23
(#890409W1.10062)
EXPIRES: 90-12-01
VAXserver 3602
(under VAX/VMS
Version 5.0)
Motorola MVME101
(MC68000) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System for VAX
to E68K, Version
3.23
(#890409W1.10063)
EXPIRES: 90-12-01
VAXserver 3602
(under VAX/VMS
Version 5.0)
Motorola MVME117
(MC68010) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System for VAX
to E68K, Version
3.23
(#890409W1.10064)
EXPIRES: 90-12-01
VAXserver 3602
(under VAX/VMS
Version 5.0)
Motorola
MVME133A-20
(MC68020) (bare
machine)
*Derived
TELESOFT
TeleGen2 Ada
Development
System for VAX
to E68K, Version
3.23
(BASE
#890409W1.10064)
EXPIRES: 90-12-01
MicroVAX I, II,
Motorola
2000, 3500, 3600,
MVME147RF &
3800 & 3900;
MVME147SRF
VAXstation I, II,
(MC68030/MC68881)
2000, 3100, 3200
& 3500; VAXserver
3500, 3600 & 3602;
VAX-11/725, /730, /750,
/780 & /785; VAX 6210,
6220, 6230, 6240, 6310,
6320, 6330 & 6340; VAX 8200,
8250, 8300, 8350,
8500, 8530, 8600,
8650, 8700, 8800,
8810, 8820, 8830,
8840, 8974 & 8978
(under VMS 5.0)
*Derived
TELESOFT
TeleGen2 Ada
Development
System for VAX
to E68K Version
3.23
(BASE
#890409W1.10064)
EXPIRES: 90-12-01
*Derived
TELESOFT
TeleGen2+ Ada
Development
All MicroVAX I &
Motorola
II; all MicroVAX
MVME133*,
2000, 3100 (incl.
MVME135* &
3100/10 &
MVME136*
3100/20), 3300,
(MC68020)
3400, 3500, 3600,
families; and
3800 & 3900; all
Motorola MVME141*
VAXstation I &
& MVME147*
II; all
(MC68030)
VAXstation 2000,
families (bare
3100, 3200, 3500
machines)
(incl. 3520 &
3540); all
VAXserver 3100,
3300, 3400, 3500,
3600 (incl.
3602), 3800,
3900, 6000 (incl.
6000-210, 220,
310, 320, 410,
420); all VAX-11/725,
11/730, 11/750,
11/780, 11/785;
all VAX 6000-200
(incl. 6000-210,
220, 230, 240),
6000-300 (incl.
6000-310, 320,
330, 340, 350,
360), 6000-400
(incl. 6000-410,
420, 430, 440,
450, 460), 8200
(incl. 8250),
8300 (incl. 8350),
8500 (incl. 8530,
8550), 8600 (incl.
8650), 8700, 8800
(incl. 8810, 8820,
8830, 8840, 8842),
8900 (incl. 8974,
8979) (under
VAX/VMS Versions
5.0, 5.1 & 5.2)
All MicroVAX I &
II; all MicroVAX
2000, 3100, 3300,
Motorola
MVME133*,
MVME135*,
System for VAX
to E68K, Version
3.23
(BASE
#890409W1.10064)
EXPIRES: 90-12-01
3400, 3500, 3600,
3800 & 3900; all
VAXstation I &
II; all
VAXstation 2000,
3100, 3200 &
3500; all
VAXserver 3100,
3300, 3400, 3500,
3600, 3800, 3900
& 6000; all
VAX-11/725,
11/730, 11/750,
11/780 & 11/785;
all VAX 6000-200,
6000-300,
6000-400, 8200,
8300, 8500, 8600,
8700, 8800 & 8900
(under VAX/VMS
Versions 5.0, 5.1
& 5.2)
MVME136* (68020
board families);
Motorola MVME141*
& MVME147* (68030
board families)
(bare machines)
TELESOFT
TeleGen2 Ada for
386 Unix V.3
Version 3.23
(#890602I1.10137)
EXPIRES: 90-12-01
Intel 520 (80386)
system with
Multibus II
(under Intel UNIX
sys V.3.0)
Same as Host
TELESOFT
TeleGen2 Ada for
SUN-386i Version
1.4
(#890602I1.10138)
EXPIRES: 90-12-01
SUN-386i (under
SunOS, version
4.0.1)
Same as Host
TELESOFT
TeleGen2 Ada for
386 UNIX V.3
Version 3.23
(#890602I1.10139)
EXPIRES: 90-12-01
Nimbus VX (80386)
system (under
Interactive UNIX
sys V.3.2)
Same as Host
TELESOFT
TeleGen2 Ada for
386 DOS Version
3.23
(#890630I1.10140)
EXPIRES: 90-12-01
Zenith
ABF-3340-EK
(under MS-DOS
Version 3.21)
Same as Host
TeleSoft
TeleGen2
VAX/1750a Cross
MicroVAX II
(under VMS 5.1)
MIL-STD-1750a
ECSPO ITS
Simulator,
Compilation
System, Version
3.23
(#890710W1.10110)
EXPIRES: 90-12-01
Version 4.0
executing on the
Host (bare
machine)
TELESOFT
TeleGen2
Macintosh Ada
Development
System Version
1.4
(#890801W1.10133)
EXPIRES: 90-12-01
Apple Macintosh
IIx (under Apple
A/UX release 1.1)
Same as Host
TELESOFT
TeleGen2 Sun-4
Ada Development
System Version
1.4
(#890801W1.10134)
EXPIRES: 90-12-01
Sun-4/280 (SPARC
Processor) (under
Sun UNIX Version
4.2, Release
4.0.3)
Same as Host
TELESOFT
TeleGen2 Sun-3
Ada Development
System Version
4.0
(#890829W1.10143)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX 4.2
Release 3.5)
Same as Host
Motorola Delta
1000, 2000 & 3000
Series (under
Motorola SYSTEM
V/68, Version
V3.5)
Motorola VME133*,
MVME135*,
MVME136* (68020
board families);
Motorola MVME141*
& MVME147* (68030
board families)
(bare machines)
TeleSoft
TeleGen2 Ada
Development
System for AIX
PS/2, Version
1.0
(#890911I1.10177)
EXPIRES: 90-12-01
IBM PS/2 Model 80
(under AIX,
Release 1.1)
Same as Host
TELESOFT
SysV 386 Ada
Cross
Compilation
Intel 520 (under
UNIX System V.3)
Intel 386-120
(80386/387) board
(bare machine)
*Derived
TELESOFT
TeleGen2+ Ada
Development
System, Version
1.4
(BASE
#890829W1.10145)
EXPIRES: 90-12-01
System, Version
3.23
(#890911I1.10187)
EXPIRES: 90-12-01
TELESOFT
TeleGen2 Ada
Development
System for the
1750A, Version
2.1.0
(#891030W1.10179)
EXPIRES: 90-12-01
IBM 4381 P3
(under MVS/XA,
Version 3.8)
MIL-STD-1750A
ECSPO RAID
Simulator Version
4.0, executing on
a MicroVAX II
(under VMS,
Version 5.2)
(bare machine)
TELESOFT
TeleGen2 Ada
Development
System for the
1750A, Version
2.1.0
(#891030W1.10180)
EXPIRES: 90-12-01
IBM 3083 JX
(under VM/HPO,
Version 4.2)
MIL-STD-1750A
ECSPO RAID
Simulator Version
4.0, executing on
a MicroVAX II
(under VMS,
Version 5.2)
(bare machine)
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#891126I1.10217)
EXPIRES: 90-12-01
Hewlett Packard
9000/370 (under
HP/UX 6.5)
Same as Host
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#891126I1.10221)
EXPIRES: 90-12-01
Hewlett Packard
9000/340 (under
HP/UX 6.5)
Motorola
MVME133A-20
(MC68020) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System, Version
1.4
(#891126I1.10222)
EXPIRES: 90-12-01
Sun-4/260 (SPARC
Processor) (under
Sun UNIX Version
4.2, Release 4.0)
Motorola
MVME133A-20
(MC68020) (bare
machine)
TELESOFT
TeleGen2+ Ada
Development
System, Version
3.23
(#891126I1.10225)
EXPIRES: 90-12-01
VAX 3800 (under
VAX/VMS 5.2)
Motorola
MVME133A-20
(MC68020) (bare
machine)
TELESOFT
TeleGen2 Ada
Development
System, Version
4.0
(#891127I1.10224)
EXPIRES: 90-12-01
VAX 3800 (under
VAX/VMS 5.2)
Motorola MVME181
(MC88100) (bare
machine)
TELESOFT
TeleGen2+ Ada
Development
System, Version
1.4
(#891127I1.10226)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX 4.2
Release 3.5)
Motorola
MVME133A-20
(MC68020) (bare
machine)
TELESOFT
TeleGen2 Sun-3
Ada Development
System, Version
4.0
(#891202I1.10223)
EXPIRES: 90-12-01
Sun-3/280 (under
Sun UNIX 4.2
Release 3.5)
Motorola MVME181
(MC88100) (bare
machine)
THOMSON-CSF,
DIVISION CIMSA
SINTRA
AlsyCOMP_039,
Version 4.23
(#891212A1.10230)
EXPIRES: 90-12-01
CETIA UNIGRAPH
2000 (under
Unigraph/X
release 3.0.6)
THOMSON MLX32/20T
(under MOP MLX
Version 1, with
ARTK Version
4.23)
TLD Systems, Ltd.
TLD VAX/1750A
Ada Compiler
System, Version:
1.3.0
(#880829W1.09156)
EXPIRES: 89-09-02
(pending)
MicroVAX II
(under VMS 4.7)
TLD 1750A
Instruction Level
Simulator
(running on the
Host) (with TLD
1750A Single
Program Kernel,
Version: 1.3.0)
(bare machine)
Tolerant Systems
Tolerant Ada
Development
System, Version
2.3
(#890911W1.10135)
EXPIRES: 90-12-01
Tolerant Eternity
(under TX,
Release 5.4.0)
Same as Host
U.S. NAVY
Ada/M, Version
2.0
VAX 8550 and VAX
11/785 (under
VMS, Version 5.1)
AN/AYK-14 (bare
machine)
(/NO_OPTIMIZE
Option)
(#891130S1.10215)
EXPIRES: 90-12-01
U.S. NAVY
Ada/M, Version
2.0 (/OPTIMIZE
Option)
(#891130S1.10216)
EXPIRES: 90-12-01
VAX 8550 and VAX
11/785 (under
VMS, Version 5.1)
AN/AYK-14 (bare
machine)
U.S. NAVY
Ada/M, Version
2.0
(NO_/OPTIMIZE
Option)
(#891201S1.10213)
EXPIRES: 90-12-01
VAX 8550 and VAX
11/785 (under
VMS, Version 5.1)
AN/UYK-44 (bare
machine)
U.S. NAVY
Ada/M, Version
2.0 (/OPTIMIZE
Option)
(#891201S1.10214)
EXPIRES: 90-12-01
VAX 8550 and VAX
11/785 (under
VMS, Version 5.1)
AN/UYK-44 (bare
machine)
UNISYS
Unisys U Series
Ada Development
System, Version
3.23
(#890409W1.10065)
EXPIRES: 90-12-01
Unisys 5000/95
(MC68020) (under
UNISYS System V,
Release 5.0)
Same as Host
UNISYS 5000/80
(MC68020), /85
(MC68020), /90
(MC68020) & /95
(MC68020) (under
UNISYS System V,
Release 5.0)
Any Host
Verdix
Corporation
VAda-110-1515,
V5.7
(#881118W1.10001)
EXPIRES: 90-12-01
Hewlett Packard
9000/350 (under
HP-UX 6.2 Version
B)
Same as Host
Verdix
Corporation
VAda-110-3434,
SUN 386i (under
SunOS Release
4.0)
Same as Host
*Derived
UNISYS
Unisys TeleGen2
Ada Compiler
Version 3.22
(BASE
#890409W1.10065)
EXPIRES: 90-12-01
V5.7
(#881118W1.10002)
EXPIRES: 90-12-01
Verdix
Corporation
VAda-110-3333,
Version 5.7
(#890216W1.10027)
EXPIRES: 90-12-01
Prime EXL (under
Unix System V /
386, Release 3.0)
Same as Host
Verdix
Corporation
VAda-110-5151,
Version 5.7
(#890216W1.10028)
EXPIRES: 90-12-01
AT&T 3B15 (under
Unix System V,
Release 3.1.1)
Same as Host
AT&T 3B Series
Family: 3B2/400
(under UNIX
System V Release
3.1 & 3.2); 3B15
(under UNIX
System V Release
3.1.1); 3B2/500,
/522 & /600
(under UNIX
System V Release
3.1.1, 3.2.1 &
3.2.2); 3B2/600G
(w/32100, 32200,
or 32200-2MMUs),
/800 & /1000-80
(under UNIX
System V Release
3.2.2); 3B2/700,
/1000-60 &
/1000-70 (under
UNIX System V
Release 3.2.1 &
3.2.2)
Any Host
Verdix
Corporation
VAda-110-2323,
Version 5.5
(#890216W1.10029)
EXPIRES: 90-12-01
Sequent Balance
8000 (under
Sequent Dynix,
Release 3.0.4)
Same as Host
Verdix
Corporation
VAda-110-4040,
Sun-4/260 (under
Sun OS, Release
4.0)
Same as Host
*Derived
Verdix
Corporation
VAda-110-5151
(BASE
#890216W1.10028)
EXPIRES: 90-12-01
Version 6.0
(#890216W1.10030)
EXPIRES: 90-12-01
Verdix
Corporation
VAda-110-15125-1,
Version 5.7
(#890216W1.10031)
EXPIRES: 90-12-01
HP 9000 Series
300 Model 350
(under HP-UX,
Release 6.2B)
MVME-133A-20
(MC68020) (bare
machine)
HP 9000 Series
300 Model 350
(under HP-UX
6.2B)
Motorola MVME-147
(MC68030/68882)
Verdix
Corporation
VADS VAX
UNIX->68K,
Version 5.7
(#890331W1.10045)
EXPIRES: 90-12-01
VAX 11-750 (under
UNIX 4.3 BSD)
Tektronix 8541
emulator (MV68020
Support System),
using TEKDB 5.01
emulation
software (bare
machine)
Verdix
Corporation
Sun4->Sun3,
Version 5.7
(#890331W1.10046)
EXPIRES: 90-12-01
Sun 4/260 (under
SunOS 4.0)
Sun 3/280 (under
SunOS 4.0)
Verdix
Corporation
VADS VAX
VMS->68K,
Version 5.7
(#890331W1.10047)
EXPIRES: 90-12-01
MicroVAX 3600
(under VMS 5.0)
MVME 133A-20
(MC68020) (bare
machine)
Verdix
Corporation
VADS ISI Self,
Version 5.7
(#890331W1.10048)
EXPIRES: 90-12-01
IS68K (Integrated
Solutions) (under
UNIX 4.3 BSD)
Same as Host
Verdix
Corporation
VADS VAX VMS,
Version 6.0
MicroVAX II
(under VMS 5.0)
Same as Host
*Derived
Verdix
Corporation
VAda-110-15125,
Version 5.7
(BASE
#890216W1.10031)
EXPIRES: 90-12-01
(#890610W1.10089)
EXPIRES: 90-12-01
Verdix
Corporation
VADS VAX VMS ->
Intel 80386,
Version 5.7
(#890610W1.10090)
EXPIRES: 90-12-01
MicroVAX 3600
(under VMS 5.0)
Intel iSBC
386/20P (bare
machine)
Verdix
Corporation
VADS Sun3 UNIX,
Version 5.7
(#890610W1.10091)
EXPIRES: 90-12-01
Sun3/280 (under
SunOS 3.5)
Same as Host
Sun-3 family
(Sun-3/52, /75,
/110, /160, /180,
/260 & /280)
(under SunOS 3.5
& 4.0)
Any Host
Verdix
Corporation
VADS Sun3/UNIX
-> 68K (68020),
Version 5.7
(#890610W1.10092)
EXPIRES: 90-12-01
Sun3/280 (under
SunOS 3.5)
Motorola
MVME133A-20 (bare
machine)
Verdix
Corporation
VADS VAX UNIX,
Version 5.5
(#890610W1.10093)
EXPIRES: 90-12-01
VAX-11/750 (under
UNIX 4.3 BSD)
Same as Host
Verdix
Corporation
VADS VAX VMS ->
68K (68000),
Version 5.7
(#890610W1.10094)
EXPIRES: 90-12-01
MicroVAX 3600
(under VMS 5.0)
Microbar GPC68000
(bare machine)
Verdix
Corporation
VADS IBM PS/2,
Version 6.0
IBM PS/2 Model 80
(under AIX 1.1)
Same as Host
*Derived
Verdix
Corporation
VADS Sun3 UNIX,
Version 6.0
(BASE
#890610W1.10091)
EXPIRES: 90-12-01
(#891116W1.10190)
EXPIRES: 90-12-01
Verdix
Corporation
VADS IBM RT,
Version 6.0
(#891116W1.10192)
EXPIRES: 90-12-01
IBM 6150 Model
135 (under AIX
2.2.1)
Same as Host
Verdix
Corporation
VADS
SUN4/UNIX->68K
(68020), Version
6.0
(#891116W1.10193)
EXPIRES: 90-12-01
Sun 4/260 (under
SunOS 4.0)
Motorola MVME147
(68030/68882)
Verdix
Corporation
VADS VMS ->
MIL-STD-1750A,
Version 6.0, MP
(#891116W1.10194)
EXPIRES: 90-12-01
DEC MicroVAX III
(under VMS 5.0)
Tektronix 1750A
Emulator
(Ethernet
Download),
v1.00-00 with
VADS EXEC v6.0
(bare machine)
Wang
Laboratories,
Inc.
Wang VS Ada,
Version 4.1
(#900116W1.10236)
EXPIRES: 90-12-01
Wang VS 8480
(under Wang VS OS
7.29.23)
Same as Host
York Software
Engineering
Limited
York Ada Compiler
Environment
(ACE) Release 4
(#890531N1.10095)
EXPIRES: 90-12-01
DuPont Pixel
Systems bRISC
(under UNIX
System V.3)
Same as Host
York Software
Engineering
Limited
York Ada
Compiler
Environment
(ACE) Release 4
(#890531N1.10096)
EXPIRES: 90-12-01
High Level
Hardware Orion
1/05 (under
Berkeley UNIX
Release 4.2)
Same as Host
York Software
Engineering
Limited
York Ada
Compiler
Environment
(ACE) Release 4
(#890531N1.10097)
EXPIRES: 90-12-01
Intergraph Inter
Pro 340 (under
UNIX System V.3)
Same as Host
Points of Contact For Vendors of Validated Compilers (as
of Feb. 1, 1990)
AETECH
David Dewitt
619/755-1277
Aitech Software EngineeringGabriel Leemor
408/720-9400
Alliant Computer Systems
Dan Palka
508/486-4950
Alsys
Lori Heyman
617/270-0030
Apollo Computer
Mike Ballentine
508/256-6600, ext
4132
BiiN
Support POC Unknown
BULL
Jean Jacques Masson
+33 164 479090
CAP Industry Ltd
Peter Hanson
+44 7 34 55900
CISI Ingenierie
Jean Louis Marro
+33 93 65 21 12
Concurrent Computer Corp. Michael Devlin
201/758-7531
Control Data
Robert Cunius
301/468-8067
CONVEX Computer Corp.
Larry Grossman
214/497-4383
Cray Research
Sylvia Crain
505/988-2468
Data General Corp.
John Doyle
508/366-8911
DDC International
Mike Turner
602/944-1883
Digital Equipment Corp.
Ms. Pat Bernard
603/881-0247
Elxsi
Ankur Saha
408/942-0900
Encore Computer
Gary Beerman
305/587-2900, ext
5866
GEC Software
David Howells
+44 1 953 2030
Gould
Gary Beerman
305/587-2900, ext
5866
Harris
Georgeanne Chitwood
305/977-5573
Hewlett-Packard
Dave Graham
408/725-8111
Honeywell Bull
Milada Williamson
703/827-3010
IBM
James Hamilton (AIX OS) 416/448-2113
IBM Canada Ltd
Antony Niro (VM & MVS OS)
416/448-2031
Intel Corporation
Ellen Deleganes
503/629-7600
InterACT
Stacy Berman
212/696-3700
Intermetrics, Inc.
Burr Tupper
617/661-1840
Irvine Compiler
Jon Hahn
714/250-1366
Krupp Atlas Elektronik GmbHDieter Weigel
49-241/457-3058
MASSCOMP
Michael Devlin
201/758-7531
Meridian Software Systems Eric Olsen
800/221-2522
or 714/727-0700
MIPS Computer Systems
Prakash Chandra
408/991-7747
MOTOROLA, Inc.
Charlene Campo
602/438-3244
Naval Underwater Systems Command
Bill Wilder
202/692-8204
New York University
Bernard Banner
212/998-3480
NIPPON TELEGRAPH & TELEPHONE CORP.Mr. Shigeru Nishiyama +81-3-740-5717
Proprietary Software Systems, Inc. Richard Gilinsky 213/394-5233
Pyramid Technology Corporation Cheryl Archer
415/335-8912
R.R. Software
Paul Fuller
608/244-6436
Rational
Diana Martin
408/496-3990
Ready Systems
Liz Parrish
408/736-2600
Rockwell International
Don Stover
319/395-5648
ROLM Mil-Spec Computers
Jon Elliott
408/432-7701
SD_SCICON plc
George Romanski or Andy Baker 617/499-2000
Siemens AG
Dr. Hoyer
+49-89-63644234
Silicon Graphics
Dave Bagshaw
415/960-1980
SofTech
Mark Moore
617/890-6900
Software Leverage
Glenn Allin
617/648-1414
Straessle Systementwicklung U. Schmitt
+49 6251 51044
SYSTEAM KG
Dr. Winterstein
+49-721-883025
Tandem Computers
Brian Ball
408/725-6000
Tartan Laboratories
Susan Englert
412/856-3600
TeleLOGIC AB
Mr. S. Bjoernson
+46 752 63001
TeleSoft
Tom Dent or Karen Johnson
619/457-2700
THOMSON-CSF, DIVISION CIMSA SINTRA
Alain Kron
+33 1 47 60 30 00
TLD Systems
Terry Dunbar
213/542-5433
Tolerant Systems
Thelma Bataille
408/433-5588
U.S. Navy/SofTech
Mark Moore
617/890-6900
UNISYS Corp
Jack Dobratz
215/542-6209
Verdix
Roger Baker
703/378-7600
York Software Engineering Limited
Prof. I.C. Wand +44 904 432725
Ada Information Clearinghouse Ada Joint Program Office
c/o IIT Research Institute
3E114
4600 Forbes Boulevard
The Pentagon
Lanham, MD 20706-4312 Washington, DC 20301-3081
703/685-1477
202/694-0208
AV 224-0208
The Ada Joint Program Office is responsible for managing DoD's effort to
implement, introduce, and provide lifecycle support for the Ada
programming
language, the DoD's common high-order language.
The Ada Information Clearinghouse facilitates the transfer of timely
information between the Ada Joint Program Office and the Ada user
community. The Clearinghouse coordinates the collection, integration,
and distribution of documentation on all aspects of the Ada language and
associated aspects of DoD's Software Initiative, announces recent
activities and general information on Ada via the Defense Data Network
(DDN) and electronic bulletin boards, and provides recent updates on Ada
conferences, seminars, classes, and textbooks.
For further information on topics covered in this newsletter, the
following
contacts may be helpful:
AdaIc Bulletin Board
Ada Calendar
Ada Usage Database
ARTEWG
Classes & Seminars
Carl Bowman*
Adrain Nimmons-Walls
Robert Peirce
Fred Maymir-Ducharme*
Tracey Williams-Cox
Conferences
DD
Validated Compiler List
Newsletter Editor
* 301/731-8894
Ann S. Eustice
Greg Siegert*
Michele Kee
John Walker
Ada EVENTS CALENDAR
The Ada Events Calendar includes information on upcoming Ada conferences.
The Ada Calendar lists only those programs with fixed dates and does not
include programs, such as classes, that are scheduled on a continuing
basis. This calendar is provided for informational purposes only and does
not represent an endorsement of these events by the Ada Information
Clearinghouse (AdaIC) or the Ada Joint Program Office (AJPO). If your
company is sponsoring an Ada event and would like to have your event
included in future AdaIC Newsletters, contact Adrain Nimmons-Walls at the
AdIC, 703/685-1477.
March 1990
27F-01
Ada Language System/Navy -- ALS/N Users' Group, quarterly
meeting. Location: Virginia Beach, VA. Hosted by Fleet Combat Direction
Systems Support Activity (FCDSSA), Dam Neck, VA. POC: Anyone interested
in
attending or speaking should contact Guy Taylor at 804/433-7230, or Maura
Pineda at 804/433-7290.
05-08
Eighth Annual National Conference on Ada Technology, "Ada
in
the '90s: Software and Systems Engineering". Location: Hyatt Regency,
Atlanta, GA. POC: Eighth Annual National Conference on Ada Technology, US
Army Communications-Electronics Command, ATTN: AM-SEL-RD-SE-CRM (Kay
Trezza), Fort Monmouth, NJ 07703-5000, 201/532-1898; AV: 992-1898,
MILNET:
AMSEL-RD-LC-COM@CECOM-1.arp.
12-15
International Conference on Computer Language. Location:
New
Orleans, LA. POC: Alexander Wolf, AT&T Bell Labs, MH 3C-533, 600 Mountain
Avenue, Murray Hill, NJ 07974, 201/582-6443, wolf@ulysses.att.com
13-15
The Object-Oriented Systems Symposium, (CASE Support for
Object-Oriented Structure Design). Location: outside Washington, DC,
Hyatt
Regency Crystal City. Hotel Information for tutorials & symposium, call
703/418-1234. Registration Information, call 508/470-3880. POC: DCI, 6
Windsor Street, Andover, MA 01810 508/475-6990
19-20
Second Annual Oregon Workshop on Software Metrics.
Location:
Portland, OR. POC: Mr. Warren Harrison, Dept. of Computer Science,
Portland State University, P.O. Box 751, Portland, OR 97207-0751,
503/464-3108, e-mail: warren@cs.pdx.edu.
April 1990
02-03
Fourth SEI Conference on Software Engineering Education.
Location: Pittsburgh, PA. POC: Mr. Leonard Deimel, program chair;
412/268-7638, led@sei.cmu.edu.
02-06
CASExpo-Spring '90. Location: Sheraton Washington,
Washington, DC. POC: Mr. Jim Duchaine, CASExpo, 5230 Leesburg Pike, #1210
, Falls Church, VA 22041-3401, 703/284-7330, FAX 703/820-2570
03-05
Issues of Integrity & Security in an Ada Runtime
Environment.
Location: Orlando, FL. Sponsored by: IIT Research Institute & University
of Houston-Clear Lake. For information: Integrity & Security in Ada, c/o
IIT Research Institute, 4600 Forbes Boulevard, Lanham, MD 20706.
23-26
SIGAda ARTEWG - Spring '90. Location: Boston, MA. POC: Mr.
Mike Victor (Raytheon), 508/858-5942
30-02M
The First International Symposium May on Environment and
Tools for Ada (SETA1). To be co-sponsored by ACM SIGAda and IEEE Computer
Society TC on Computer Languages and in cooperation with ACM SIGSOFT.
Location: The Sheraton at Redondo Beach, Redondo Beach, CA. CALL FOR
PAPERS: Please contact either of the co-program chairs: Mr. Stowe Boyd,
Meridian Software Systems Inc, 23141 Verdugo Drive, #105, Laguna Hills,
CA
92653 714/727-0700, ext 222, sboyd@meridian.com; or Mr. Dewayne E. Perry,
AT&T Bell Laboratories, #3D-454, 600 Mountain Avenue, Murray Hill, NJ
07974, 201/582-2529, dep@allegra.att.com
May 1990
22-25
1990 ACM SIGMETRICS Conference on Measurement and Modeling
of
Computer Systems. Location: Boulder, CO. POC: Prof. Mary K. Vernon,
Computer Sciences Dept., University of Wisconsin-Madison, 1210 West
Dayton
Street, Madison, WI 53706, vernon@cs.wisc.edu
June 1990
11-14
CASExpo-Canada. Location: Metro Toronto Convention Centre,
Toronto, Ontario. POC: Mr. Jim Duchaine, CASExpo, 5230 Leesburg Pike,
#1210, Falls Church, VA 22041-3401, 703/284-7330, FAX 703/820-2570
12-14
Ada-Europe Dublin 1990 Conference & Exhibition, Ada:
Experiences and Prospects. Location: Dublin, Ireland. CALL FOR PAPERS:
POC: Conference Secretariat, Ada-Europe 1990, Northumberland House, 44
Northumberland Road, Ballsbridge, Dublin 4, Ireland, +353-1-688244, FAX:
+353-1-686769
26-28
WADAS '90 -- Seventh Washington Ada Symposium. Location:
McLean Hilton, McLean, VA. CALL FOR PAPERS: Steering Chair: Eileen Quann,
301/498-4601. Program Chair: Christine Braun, 703/818-4475. WADAS '90:
c/o Eileen Quann, Fastrak Training, Inc., 9175 Guilford Road, #300,
Columbia, MD 21046-1802
July 1990
16-20
Fourth International Workshop on Real-time Ada Issues.
Location: Pitlochry, Scotland. Position papers were due no later than
Jan.
29, 1990. POC: Mr. Andy Wellings, Dept. Computer Science, University of
York, Heslington, York Y01 5DD, UK. Inquiries regarding local
arrangements
to Ms. Helen Byard (same address), telephone +44-904-412740
October 1990
22-25
CASExpo-Asia. Location: Hong Kong Convention & Exhibition
Centre, Hong Kong. POC: Mr. Jim Duchaine, CASExpo, 5230 Leesburg Pike,
#1210, Falls Church, VA 22041-3401, 703/284-7330, FAX: 703/820-2570
November 1990
28-29
NASA/GSFC SEL & Ada Symposium. Location: NASA, Greenbelt,
MD. POC: Mr. Ed Seidewitz, NASA, 301/286-7631.
December 1990
03-06
TRI-Ada '90. Location: Baltimore Convention Cntr, Balto,
MD.
Final call for papers: Mar. 19, 90; abstract due May 21, 90. For info,
contact conf. chair: Dr. Dennis Ahern, Aerospace Sftwre, M/S 432,
Westnghse Electrnc Sys Grp, PO Box 746, Balto, MD 21203-0746, 301/9936234,
fax: 765-4400, e-mail: dahern@wsmr-simtel20.army.mil: prgrm chair: Dr.
Erhard Ploedereder, Tartan Labs, 300 Oxford Dr., Monroeville, PA 15146,
412/856-3600, fax: 856-3636, ploedere@tartan.com,
ploedere@ajpo.sei.cmu.edu. Tutorial Co-Chair (Primary Contact): Mr. Steve
Grimaldi, Booz, Allen, Hamilton, Airport Square Eight, #150, 891 Elkridge
Landing Rd., Linthicum, MD 21090, 301/850-5006, fax: 550-4592,
grim@terminus.umd.edu
*************************************************************************
**