TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
X-To: "W. Wesley Groleau x4923" <[log in to unmask]>
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Hal Hart <[log in to unmask]>
Date: Fri, 5 Sep 1997 13:54:03 -0700
In-Reply-To: Your message of Fri, 05 Sep 97 13:34:11 CDT. <[log in to unmask]>
Comments: RFC822 error: <W> CC field duplicated. Last occurrence was retained.
Reply-To: Hal Hart <[log in to unmask]>
Parts/Attachments: text/plain (13 lines)
 FYI, The Army programming language policy statement Wesley just
distributed identifies essentially the SAME high-leverage front-end
decision factors which the 1996 NRC report recommended addressing in
an integrated decision process in what that report called the Software
Engineering Plan Review (SEPR).  The wording of the Army statement is
lifted almost directly from ASD Paige's April 29 policy memorandum
(doing a little Army tailoring, e.g., JPA -> ATA, adding "O&S" and
"reuse" I think [which was on the NRC list], and introducing a little
misspelling :-).  Paige's memo did not use the term "SEPR" but
established a major, early milestone for these same concurrent
decisions.  If you took Paige's surrounding statements and context as positive
for Ada in the DoD, this statement has the same effect within the Army. -- hh