From: kahn@kahn.pdial.interpath.net (Larry Kahn)
Subject: Re: What to use when 2167A is too much
Date: 13 Oct 1994 18:09:15 GMT
Date: 1994-10-13T18:09:15+00:00 [thread overview]
Message-ID: <37jt4b$atl@redstone.interpath.net> (raw)
In-Reply-To: mcriley.782007005@BIX.com
In article <mcriley.782007005@BIX.com>, 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.
next prev parent reply other threads:[~1994-10-13 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CxHo6K.4Ln@news.cis.umn.edu>
1994-10-13 0:10 ` What to use when 2167A is too much mcriley on BIX
1994-10-13 12:15 ` Robert Firth
1994-10-13 18:09 ` Larry Kahn [this message]
1994-10-14 7:47 ` Henri Altarac
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox