From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: *
X-Spam-Status: No, score=1.9 required=5.0 tests=BAYES_50,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!ucla-cs!zen!ucbvax!SIMTEL20.ARPA!RCONN
From: RCONN@SIMTEL20.ARPA (Rick Conn)
Newsgroups: comp.lang.ada
Subject: Re: new project
Message-ID: <12324047453.8.RCONN@SIMTEL20.ARPA>
Date: Wed, 5-Aug-87 08:14:34 EDT
Article-I.D.: SIMTEL20.12324047453.8.RCONN
Posted: Wed Aug  5 08:14:34 1987
Date-Received: Sat, 8-Aug-87 00:46:44 EDT
References: <870803204629.533451@DOCKMASTER.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

Scott,
	Re your question about using Ada as the design language and the
implementation language for a new project, you might be interested in
getting a copy of "Ada Adoption Handbook: A Program Manager's Guide", Version
1.0, SEI Technical Report CMU/SEI-87-TR-9, ESD-TR-87-110, May 1987
by John Foreman and John Goodenough of the Software Engineering
Institute.  Contact the SEI JPO at 412/268-7630 for details (this document
is free).
	The PMG, while distinctly biased toward the DoD Ada effort,
contains many reasonable answers to questions commonly raised about adopting
Ada for use on a project.  I feel that the PMG does a good job in
identifying the issues, providing possible answers to the questions
commonly raised (altho I may take issue with some of the answers, the
SEI should be commended for making the effort to create the PMG and
going on the line with their opinions), and providing pointers to
help you in answering your questions to your own satisfaction.
	An outline of the PMG:
		1. Introduction
		2. Program Manager Considerations (costs, Technical
			issues, program control, getting help)
		3. The Need for Ada
		4. Software Production Technology (terms, Ada compilers,
			programming support environments, forecast)
		5. Ada Maturity and Applicability (action plans for
			various situations, use of Ada on embedded
			processors, use of Ada for real-time systems,
			use of Ada for distriubted systems)
		6. Special-purpose languages
		7. Mixing Ada with other languages
		8. Software Reuse and Ada
		9. Learning Ada: Training Implications
		I. Ada Working Groups and Agencies
		II. Programs Using Ada (Army, Navy, Air Force, commercial, IR&D)
		III. Ada Textbooks
		IV. Ada Compilers for target processors

	You may also want to look at some of the documentation in the
Ada Software Repository, particularly the files in PD:<ADA.EDUCATION>
on Ada programming notes (PNOTE*.DOC), common Ada programming errors
(PROGERRS.DOC), technical reports from live Ada projects with productivity
information and "lessons learned" (ADASOFTR.DOC and TITR.DOC), the lists
of Ada texts (TEXTBOOKS.DOC and TEXTS.DOC), and the files in PD:<ADA.POINTERS>
(which contains lists of validated Ada compilers, planned Ada compilers,
and information on various DoD and SIGAda programs/projects).

		Rick
-------