Click here to enter Asset Directory/transfer Asset File(s): ../../ase02_01/docs/advocacy
Click here to enter Asset Directory/transfer Asset File(s): ../../ase02_01/docs/whyada
Follow path to see directory
The Ada Advocacy Package
Making the Business Case for Ada
SIGAda, the Ada Resources Association (ARA), the Ada Joint Program
Office (AJPO), the AJPO's agent (the Ada Information Clearinghouse
(AdaIC)), and many others in the Ada community have identified as one
impediment to the widespread use of Ada a previously-unfulfilled need to
make widely available a package containing a small number of refined,
tested, best-of-breed materials usable by anyone who is trying to
convince an organization or project to use Ada. The "Ada Advocacy
Package" has been created to help address this shortcoming - all of
these organizations have initiated focused efforts to collect, create,
and refine the appropriate Ada advocacy materials. Materials in this
- management/business briefings (documented productivity benefits,
cost/schedule results, risk mitigation effects, availability of
trained Ada programmers, and other topics)
- technical briefings (features of Ada that support improved
software engineering and development)
- a concise monograph (equivalent to the briefings)
- a catalog of vendors providing Ada products and services
- a set of Ada "success stories" in various domains (especially
commercial software domains)
- frequently asked questions about Ada, its availability, and
results of its usage
- resource lists (including education/training materials and
providers) and Web pointers
- tailoring and selection guidelines for using the package's
- comparing Ada and C++
- transitioning the Ada Joint Program Office, the evolution of
Ada from a project to a product
Contents of Files:
- CACI1 - A collection of independent briefing slides (ammunition) and
an extensive bibliography presenting various Ada success "bullets"
prepared by CACI for the AJPO. This collection is entitled "Published
Results of Using Ada."
- Colbert1 -- "Ada in Open Systems" by Edward Colbert. Updated in
- Colbert2 -- "Technical Comparison of the Ada and C++ Languages"
by Edward Colbert.
- Colbert3 -- "Report on the Portability and Performance of a Real
Time Ada Application Prototype" by Edward Colbert.
- Engle1 - Dr. Charles Engle's "Why Ada" brief in Powerpoint 4.0 and
HTML. These files are unpacked in the whyada directory.
- Engle2 - "Transitioning the AJPO" by Dr. Charles Engle.
- Masters1 -- contains a file sent specifically to put up on the
Web (see note below) by Mike Masters for his briefing to the NRC
on the use of Ada in the Navy (Spring 1996) entitled "Programming
Languages and Life Cycle Cost." Requires Powerpoint 4.0.
- Mathis1 -- a presentation given at a European Space Agency
symposium by Bob Mathis on "The Challenge of Ada95"
- Mathis2 -- a presentation to the NRC study committee by Bob Mathis
on "The Future of Ada"
- Mathis3 -- a presentation at STC'96 by Bob Mathis on "Making Ada
an Even Better Choice for the DoD and Others, Too"
- Mathis4 -- a presentation at AdaEurope'96 by Bob Mathis on "Making
the Business Case for Ada"
- Mathis5 -- contains an FAQ style document entitled Fallacies and Red
Herrings. It attempts to answer the non-technical issues that come up
with regard to Ada use.
The files in the advocacy directory are stored in their original
formats (Powerpoint 4.0, Word 6.0). Postscript versions of the files
November 1996 from Hal Hart et al Initial Release to SW-ENG and PAL
November 1996 from Bob Mathis et al 2nd Release to PAL
January 1997 from Rick Conn HTML Why Ada and minor update
January 1997 from Ed Colbert et al 4th Release - several updates
January 1997 from Brad Balfour 5th Release - CACI collection
January 1997 from Rick Conn 6th Release - more updates
February 1998 from Ed Colbert 7th Release - colbert1 updated
This prologue must be included in all copies of this software.
Restrictions on use or distribution: NONE
This documentation is provided "AS IS" and without any expressed or
implied warranties whatsoever. No warranties as to performance,
merchantability, or fitness for a particular purpose exist.
The user must assume the entire risk and liability of using this
document. In no event shall any person or organization of people be
held responsible for any direct, indirect, consequential or
inconsequential damages or lost profits.