PMYERS@ADA20.ISI.EDU.UUCP (04/07/87)
Here is DoDD 3405.2. Electronic facsimiles of this
Directive are also available on our bulletin boards:
On the DDN Ada20 host the file is called "<ada-info>3405-2.hlp"
On the PC Bulletin board the file is called "3405-2.hlp".
The phone number for the PC bulletin board is (202) 694-0215.
Please feel free to disseminate this directive to the widest
possible audience.
================================================================
DEPARTMENT OF DEFENSE
DIRECTIVE
March 30, 1987
NUMBER 3405.2
USD(A)
SUBJECT: Use of Ada(tm) in Weapon Systems
References: (a) MIL-STD-1815A, "Ada Programming
Language," February 17, 1983*
(b) DoD Federal Acquisition Regulation Supplement
(DFARS) 70.400(d), "Integral Part of a Weapons
System," April 30, 1984
(c) DoD Standard 2167, "Defense System Software
Development," June 4, 1985 (and subsequent
revisions)
(d) DoD Handbook 281, "Defense System Software
Development Handbook," October 22, 1984* (and
subsequent revisions)
A. PURPOSE
-------
This Directive establishes DoD policy and prescribes procedures for
using the Ada programming language, as defined by reference (a), in
computers integral to weapon systems.
B. APPLICABILITY AND SCOPE
-----------------------
This Directive:
1. Applies to the Office of the Secretary of Defense (OSD), the
Military Departments, the Organization of the Joint Chiefs of Staff
(OJCS), the Defense Agencies, and the Unified and Specified Commands
(hereafter referred to collectively as "DoD Components").
2. Applies to all computers that are integral to weapon systems.
Such computers, as defined by DFARS (reference (b)), are described as
follows:
a. Physically a part of, dedicated to, or essential in real time
to a performance of the mission of weapon systems.
b. Used for specialized training, diagnostic testing and
maintenance, simulation, or calibration of weapon systems.
c. Used for research and development of weapon systems.
3. Applies to all new weapons system during all phases of the life
cycle and to major software upgrades of existing weapon systems. A major
upgrade, as it applies to a specific system or subsystem, is the redesign
or addition of more than one-third of the software.
________________
*These publications may be obtained at the Naval Publications and Forms
Center, 5801 Tabor Avenue, Philadelphia, PA 19120.
(tm) Ada is a Registered Trademark of the U.S. Government (Ada Joint
Program Office).
C. POLICY
------
1. Ada shall be the single, common, high order programming
language, effective immediately.
2. Use of validated Ada compilers is required.
3. Software engineering principles that facilitate the use of the Ada
language and that are described in DoD Standard 2167 and DoD Handbook 281
(references (c) and (d)) shall be fully exploited to ensure realization of
Ada's potential to reduce costs, shorten schedules, and improve the
quality of defense software.
4. An Ada-based program design language (PDL) shall be used during
the designing of the software. Use of a PDL that can be successfully
compiled by a validated Ada compiler is encouraged in order to facilitate
the portability of the design.
D. RESPONSIBILITIES
----------------
1. The Under Secretary of Defense (Acquisition) (USD(A)) shall:
----------------------------------------
a. Be the senior DoD official for all activities related to
this Directive.
b. Oversee, coordinate, and implement DoD policies and
procedures under this Directive.
c. Designate additional Ada validation facilities as required.
d. Periodically review documented justifications for granted
waivers.
e. Advise the Secretary of Defense on all matters related to
this Directive.
2. The Heads of DoD Components shall, where applicable:
-----------------------
a. Ensure that this Directive is implemented in the respective
organization.
b. Designate an Ada executive official who shall monitor
programs relative to the use of Ada, support the Ada program activities in
the DoD Component, and serve as a focal point in the DoD Component for all
Ada program activities.
c. Designate an Ada waiver control officer who shall have
responsibility for implementing the DoD waiver provisions and procedures
in this Directive for the Component, and who shall maintain close liaison
with the Ada Joint Program Office (AJPO) to keep abreast of the latest
technology and developments in the Ada program.
d. Develop a comprehensive Ada implementation plan that covers
the transition to and implementation of Ada in the DoD Component as
required by this Directive. This plan shall be forwarded to the USD(A)
150 days from the effective date of this Directive. Periodic updates to
this plan shall be submitted when requested by the USD(A) or as Component
plans change.
E. PROCEDURES
----------
1. Control Agent
-------------
Ada, as a military standard, is controlled within the DoD by the
AJPO in OSD. The Air Force is responsible for providing an Ada validation
facility to validate conformance of compilers as stated in MIL-STD-1815A
(reference (a)), using procedures established by the AJPO. Ada is also
controlled outside of the DoD by the American National Standards Institute,
a nongovernment organization.
2. Exceptions
----------
a. If a programming language other than Ada was being used in the
full-scale development of a weapon system on the effective date of this
Directive, that language may continue to be used through deployment and
software maintenance unless the system is undergoing a major software
upgrade as defined in subsection B.3., above, of this Directive.
b. Ada is preferred, but not required as a test language to be
used solely for hardware Unit Under Test equipment.
c. Ada is preferred, but not required for commercially
available, off-the-shelf software that will not be modified by, or for, the
DoD.
3. Waivers
-------
Authority for issuing waivers from using Ada, as required by this
Directive, is delegated to each DoD Component, only on a specific system or
subsystem basis. For each proposed waiver, a full justification shall be
prepared and shall include the following as a minimum: a developmental
risk analysis, including technical performance, cost and schedule impact,
and a complete life cycle-cost analysis. The life-cycle cost analysis
shall include an impact assessment on both the long-term costs of future
upgrades and the operation of software support centers.
F. EFFECTIVE DATE AND IMPLEMENTATION
---------------------------------
This Directive is effective immediately. Forward three copies of
implementing documents to the USD(A) within 120 days.
William H. Taft, IV
Deputy Secretary of Defense