comp.lang.ada
 help / color / mirror / Atom feed
From: jsheriff@mitre.org (Jack Sheriff)
Subject: Re: DOD-STD-2167a
Date: Tue, 24 Jan 1995 14:30:31
Date: 1995-01-24T14:30:31+00:00	[thread overview]
Message-ID: <jsheriff.2.000E82A9@mitre.org> (raw)
In-Reply-To: 3g0i9d$6hj@cliffy.lfwc.lockheed.com

In article <3g0i9d$6hj@cliffy.lfwc.lockheed.com> l107353@cliffy.lfwc.lockheed.com (Garlington KE) writes:
>David O'Brien (dobrien@seas.gwu.edu) wrote:

>: Poking around, I found ajpo.sei.cmu.edu:/public/mil-std-sdd/*
>: The README file said the "Miliary Standard Defense System Software
>: Development release" replaces DOD-STD-2167A, DOD-STD-7935A, and
>: DOD-STD-1703NS.  It comes in postscript and MS-Word for Windows 2.0.

>Beware! There is not an _official_ replacement for any of these standards, yet!
>MIL-STD-SDD was _intended_ to replace these, but was sidetracked by the Perry
>memo. There is now an effort to make MIL-STD-SDD a commercial standard, at
>which time it _may_ replace the current standards.

This is mostly right, but may be a little misleading.

The Perry memo requires a program office to get a waiver in order to include a 
MIL or DOD standard in a contract.  I have heard that the Air Force and 
the Navy are both processing service-wide waivers for MIL-STD-498 (the 
replacement for the three standards mentioned above).  Once these service-wide 
waivers are in place, any Air Force or Navy office will be able to use the new 
standard without needing to get an individual waiver.

MIL-STD-498 is supposed to have a lifetime of two years.  At the end of the 
two years, it is supposed to be replaced by a commercial standard.  My 
understanding is that it will be an IEEE standard and will look remarkably 
like MIL-STD-498.

Jack Sheriff




  reply	other threads:[~1995-01-24 14:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-01-18  3:36 DOD-STD-2167a Spencer Laird
1995-01-21 21:46 ` DOD-STD-2167a David O'Brien
1995-01-22 18:29   ` DOD-STD-2167a David Weller
1995-01-23 15:34   ` DOD-STD-2167a Garlington KE
1995-01-24 14:30     ` Jack Sheriff [this message]
1995-01-25 19:34       ` DOD-STD-2167a Oliver Kellogg
1995-01-24  5:25   ` DOD-STD-2167a Howard Verne
1995-01-26  2:03     ` DOD-STD-2167a Oliver Kellogg
1995-01-30 16:11     ` DOD-STD-2167a Scott . Smart CDR
     [not found]   ` <3 <3g693a$5sb@salyko.cube.net>
1995-01-27 12:36     ` Electronic Availability of MIL-STD-498 (wasDOD-STD-2167A) Doc Elliott
1995-01-29 14:32       ` Brad Balfour
     [not found]   ` <B <49686@suned1.Nswses.Navy.MIL>
1995-02-08 20:17     ` DOD-STD-2167a Doc Elliott
1995-01-24 17:51 ` DOD-STD-2167a Theodore E. Dennison
  -- strict thread matches above, loose matches on Subject: below --
1995-01-23 20:23 DOD-STD-2167a Doc Elliott
1995-01-24 14:58 ` DOD-STD-2167a David Weller
1995-01-24 16:42 ` DOD-STD-2167a Garlington KE
1995-01-25 22:22 ` DOD-STD-2167a Chris Warack <sys mgr>
     [not found] <INFO-ADA%95012615321114@VM1.NODAK.EDU>
1995-01-27 12:42 ` DOD-STD-2167a Doc Elliott
     [not found] ` <3gqspo$n3l@usafa2.usafa.af.mil>
1995-02-06 16:23   ` DOD-STD-2167a Kevin Weise
1995-01-30 15:34 DOD-STD-2167a CONDIC
1995-01-30 19:32 ` DOD-STD-2167a Garlington KE
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox