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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6acdccb9185c93b0 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-14 13:59:33 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!swrinde!sgiblab!uhog.mit.edu!news.kei.com!ddsw1!redstone.interpath.net!usenet From: kahn@kahn.pdial.interpath.net (Larry Kahn) Newsgroups: comp.lang.ada Subject: Re: What to use when 2167A is too much Date: 13 Oct 1994 18:09:15 GMT Organization: Dynamics Research Corp. Message-ID: <37jt4b$atl@redstone.interpath.net> References: NNTP-Posting-Host: kahn.pdial.interpath.net X-Newsreader: WinVN 0.92.6 Date: 1994-10-13T18:09:15+00:00 List-Id: In article , mcriley@BIX.com (mcriley on BIX) says: > >coyl0022@gold.tc.umn.edu (Michael Coyle ) writes: > >> I have seen references to Yourdon, Smith, Marko, Freeman, >>MIL-STD-SDD and DOD-STD-2167A. All I need is somewhere to start, >>or a simple subset of 2167A. I am working on the design and > 2167 and 2167A are designed to be tailored ... that is part of the application process. Basically you use only the documents that are required/needed for your program.. Of course the government contracting office overseeing your project has final say on what you have tailored out for your program. Laurence G. Kahn Senior Software Engineer Dynamics Research Corp.