From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b47867a1bfd03e88 X-Google-Attributes: gid103376,public From: Ken Garlington Subject: Re: DOD-STD-2167A issue. Date: 1996/12/09 Message-ID: <32AC6D72.47AA@lmtas.lmco.com>#1/1 X-Deja-AN: 203185724 references: <00001a73+00003a4e@msn.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin Tactical Aircraft Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; I) Date: 1996-12-09T00:00:00+00:00 List-Id: Kenneth Mays wrote: > > Anyhow, update your people on the newer MIL-STD-498. There is no need > to refer anyone the older DOD-STD-2167A, unless they just don't keep > up with the latest issues in software engineering. That could be a > problem. Well, sorta... We have one project that is still required to use DoD-STD-2167A, since it started before 1994. We have another project that doesn't require _either_ standard, because it started just this year, _after_ acquisition reform and the block change process. So, the bottom line is that "keeping up with the latest issues in software engineering" is a lot harder than it sounds :) > > Ken Mays > Software Design Manager > kmays@msn.com -- LMTAS - The Fighter Enterprise - "Our Brand Means Quality" See http://www.lmtas.com for more information (job listings now available)