From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=1.0 required=3.0 tests=BAYES_40,TO_NO_BRKTS_PCNT
	autolearn=no autolearn_force=no version=3.4.5-pre1
Date: 28 Aug 91 11:28:00 EDT
From: "Paul Byrley" <byrley@ntsc-rd.navy.mil>
Subject: Re-write in Ada regs
Message-ID: <9108281532.AA24280@ajpo.sei.cmu.edu>
List-Id: <comp.lang.ada>

Re: Rules on converting to Ada in major upgrades
Requested by John Sims in V91 #254

John Sims,
There are several levels of regulations which do require the 
re-write into Ada if a modification exceeds 1/3 (not 30%) of the 
["software" per DOD Directive 3405.1 encl 2] ...or the 
["existing code over the system life cycle" per  Army 
headquarters letter 25-90-1, dtd 16 July 1990 from 
office SAIS-ADO] ...or 
["software for a specific system or subsystem" per SECNAVINST 5234.2, 
dtd 3 Nov 1988].  As you can see, DOD directed and then Army, Navy (and, I'm
sure, USAF) followed.  None of them ever really said what software
to multiply by 1/3 to determine if a re-write is required and people
have even added lines of commercial operating system or databases 
so 1/3 of it was a really big number and therefore not exceeded.  
I believe that things are now more strictly enforced so don't plan 
on skipping Ada on major upgrades.

Paul Byrley
(407) 380-8341