Navy Counters Ada Mandate?

Navy Counters Ada Mandate?

[Walter Dence]

     A supervisor here recently attended a high-level navy
conference.  He now claims that he heard at the conference
that the US Navy is going to issue a policy this Spring that
eliminates the effect of the Ada Mandate.

     He is now using this rumor to require that our work become
standardized to ANSI-C. 

     Others here are now trying to assemble standards for 
contracting using ANSI-C.  

     Can anyone shed any light on this?



=====================================================================
                       WALTER E. DENCE, JR.
                   Data Acquisition Specialist
                 Influence Mechanisms Branch, G95

Commander, Dahlgren Division                        
Naval Surface Warfare Center     Office:          (301) 394-1707/1960
Dahlgren Division Detachment     Fax:             (301) 394-4510/4727
White Oak, G95 (W. Dence)        DSN (AutoVoN):         290-1707/1960
10901 New Hampshire Ave.         MilNet: wdence@nswc-wo.nswc.navy.mil
Silver Spring, MD 20903-5000     Home:                 (301) 229-7394

         (This is personal opinion, not official opinion.)
=====================================================================

Re: Navy Counters Ada Mandate?

[Currie Colket]

 
Reference to wdence@nswc-wo.nswc.navy.mil message:
 
>     A supervisor here recently attended a high-level navy
> conference. He now claims that he heard at the conference 
> that the US Navy is going to issue a policy this spring that 
> eliminates the effect of the Ada Mandate.
 
>     He is now using this rumor to require that our work become
> standardized to ANSI-C.
 
>     Others here are now trying to assemble standards for
> contracting using ANSI-C.
 
>     Can anyone shed any light on this?
 
The rumor is neither based on current DoD policy nor on pending 
Department of Navy (DON) policy.
 
The current DoD policy was established in the 17 April 1992 ASD Letter 
signed by the Honorable Duane P. Andrews, subject: Delegations of Authority
and Clarifying Guidance on Waivers from the use of the Ada Programming 
Language. This document identifies guidelines such as:
 
	The use of Ada is presumed cost effective for all new development;
 
	The use of Ada is presumed cost effective for modification of more 
	than one-third of a functional component of DoD software;
 
	Waivers from the non-use of Ada are required. 
 
A copy of the full text of this letter can be obtained through the Ada
Information Clearing House at (703) 685-1477 or (800) ADAIC11.
 
According to Ms. Toni Stuart, from the Department of the Navy Information 
Systems Management Center (NISMC), there will soon be a DON policy letter 
based on this ASD Letter. The new policy for the Department of Navy (DON) 
will establish the use of Ada for new systems development and for major 
software upgrades of existing systems regardless of size, cost, or
functional application. The new policy will require a waiver for the non-use
of Ada. Waivers are intended to document the fact that an alternative 
approach is cost effective over the life cycle of the application. 
There are no blanket domains where a language such as ANSI-C
can be used under the new DON policy. Ada is the language for the DON and is
presumed cost effective for all new development and major system upgrades.
Ms. Stuart can be reached at (202) 433-4903 should you have any additional 
questions.
 
The technical Ada base supports this policy. Currently there are over 500
validated Ada compilers covering a wide range of host and target computers.
For a list, please contact the Ada Information Clearinghouse at 
(703) 685-1477 or (800) AdaIC11. Ada bindings are available in commercial 
products to a wide range of Open System Architecture (OSA) / Open System
Environment (OSE) interfaces. The Report, Available Ada Bindings, just
updated in November identifies those currently available. It is also 
available through the Ada Information Clearinghouse. 
 
It should be noted that should Commercial-Off-The-Shelf (COTS) Software
satisfy the DOD or DON requirements, then procurement of the COTS software
is generally more cost effective than developing the application regardless
of language used. The language used in COTS software procurements is 
"don't care" and generally not known. In order to qualify, the COTS software
must not be modified or maintained by the DON. 
 
 
For other questions, please contact the undersigned at (703) 614-0209.
 
 
Currie Colket
Navy Deputy Director, Ada Joint Program Office (AJPO)
 

Re: Navy Counters Ada Mandate?

[Gregory Aharonian]

>It should be noted that should Commerical-Off-The-Shelf (COTS) Software
>satisfy the DoD or DoN requirements, then procurement of the COTS software
>is generally more cost effective than developing the application regardless
>of language used.  The language used in COTS software procurements is
>"don't care" and generally not known.  In order to qualify, the COTS software
>must not be modified or maintained by the DoN.

Talk about a nice big loophole for circumventing the Ada mandate, given the
uncertainty about how to define when something is COTS (i.e. how many copies
do I have to sell 1 - 10 - 100?).  For example, for a big telecommunications
project for the Navy, could ATT make a bid based on the millions and millions
of lines of C/C++ code it uses in its commercial networks?

Greg Aharonian
Source Translation & Optimization
-- 
**************************************************************************
Greg Aharonian
Source Translation & Optimiztion
P.O. Box 404, Belmont, MA 02178

Re: Navy Counters Ada Mandate?

[Robert I. Eachus]

In article <SRCTRAN.92Dec11150428@world.std.com> srctran@world.std.com (Gregory
 Aharonian) writes:

   Talk about a nice big loophole for circumventing the Ada mandate,
   given the uncertainty about how to define when something is COTS
   (i.e. how many copies do I have to sell 1 - 10 - 100?).  For
   example, for a big telecommunications project for the Navy, could
   ATT make a bid based on the millions and millions of lines of C/C++
   code it uses in its commercial networks?

   Sure it could.  If, for example, they bid an ESS4 switch with the
software as an NDI (non-development item) and software support
guarenteed for some number of years at a fixed price per year.  The
number of copies of the product that ATT sells it part of the overall
risk assesment.

   Now if ATT says, "We are going to use our existing software but
modify it to meet your requirements.  The code development will cost
$X million dollars, and take N months."  Now the Ada mandate kicks
in...

--

					Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...