TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"W. Wesley Groleau x4923" <[log in to unmask]>
Reply To:
W. Wesley Groleau x4923
Fri, 5 Sep 1997 13:34:11 -0500
text/plain (75 lines)
----- Begin Included Message -----

Subject: ADA policy & 3rd Generation Prog Languages

     FYI.  Today I received the below ODISC4 e-mail on a document signed by
     Mr. Borland, ODISC4 Vice Director, not revising or extending the Ada
     policy, but establishing language for the use of 3d/4th Generation
     Programming Languages.  If you have seen this e-mail or letter, I
     apologize for your inconvenience.


     Selection of Third Generation Programming Languages

     On July 28, 1997 above memorandum was signed by Mr. David Borland,
     Vice Director.

     Reference HQDA Letter 25-91, July 17, 1995, subject:  Implementation
     of the Ada Programming Language.

     The referenced Army policy on implementation of the Ada programming
     language expired on July 17, 1997 and will not be revised or extended.
      The Army Technical Architecture (ATA) designates approved programming
     language standards relating to the utilization of Third Generation
     Language (3GL). Army Program Managers and organizations responsible
     for software acquisition, development and maintenance should adhere to
     the 3GL standards set forth in the most current version of the ATA.
     Unless specifically addressed in the ATA, there are no restrictions on
     the use of Fourth Generation Languages (4GLs) or advanced software

     Programming language selections should be made in the context of the
     system and software engineering factors that influence overall
     life-cycle costs, risks, and potential for interoperability.  The
     selection factors should be reviewed by the program Integrated Product
     Team (IPT).  Among the factors the IPT should considered are:

     . extent of compliance with/incorporation or other related direction
     (e.g., ATA, open systems, and commericial-off-the-shelf software) and
     the impact hereof;

     . long-term maintenance implications, including evolvability,
     supportability and lowest life-cycle operations and sustainment (O&S)

     . software reuse;

     . system/software requirements, including performance,
     interoperability, reliability, safety, and security requirements;

     . system/software architecture, including partioning into components;

     . selection of software development and support methodologies and

     . use of software development and support tools and generators;

     . integration of software issues and decisions with other planning
     considerations to include cost, schedule, acquisition strategy and

     The ODISC4 action officer for this action is Ms. Helen Letmanyi, DSN
     225-0259, commercial 703-695-0259.

     (Ms. Helen Letmanyi/DISC4/DSN 2225-0259)

----- End Included Message -----