* Re: What to use when 2167A is too much [not found] <CxHo6K.4Ln@news.cis.umn.edu> @ 1994-10-13 0:10 ` mcriley on BIX 1994-10-13 12:15 ` Robert Firth ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: mcriley on BIX @ 1994-10-13 0:10 UTC (permalink / raw) 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 >coding of an app, and since grad students come and go, I want >others later on to have sufficient documentaion (i.e. more that >in line comments!) of the program. I also want some help in >requirements, specs, testing strategies etc., but there is no way >I can get through 2167A in time, and I don't need something >that huge. Since I am customer, coder, maintainer, tester, >designer and documenter, and I have little experience in some of >the above areas, I just need some help to guide me through those >areas where I don't know any good techniques, and some >suggestions to improve what I am already doing. >-- >//////////////////////////////////////////////////////////////////// >Michael Coyle coyl0022@gold.tc.umn.edu For the level of documentation you're requiring I would suggest a paper by Dave Parnas titled "A Rational Design Process: How and Why to Fake It." Seriously! That paper distills everything I've come across regarding requirements, design, implementation, maintenance, and life cycle issues into an understandable and manageable process. I don't have the publishing info, but it was reprinted in "Software State of the Art: Selected Papers", editing by DeMarco & Lister, published by Dorset House. I'd give you the ISBN, except the book is at work. Anyhow, I highly recommend it. Marc A. Criley Sr. Systems Engineer CAE-Link Fligh\x7ft Simulation ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: What to use when 2167A is too much 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 1994-10-14 7:47 ` Henri Altarac 2 siblings, 0 replies; 4+ messages in thread From: Robert Firth @ 1994-10-13 12:15 UTC (permalink / raw) In article <mcriley.782007005@BIX.com> mcriley@BIX.com (mcriley on BIX) writes: >I don't have the publishing info ... David Parnas & Paul Clements: Rational Design Process - How and Why to Fake it IEEE Software Engineering, 1986 February, p 251. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: What to use when 2167A is too much 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 1994-10-14 7:47 ` Henri Altarac 2 siblings, 0 replies; 4+ messages in thread From: Larry Kahn @ 1994-10-13 18:09 UTC (permalink / raw) 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. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: What to use when 2167A is too much 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 @ 1994-10-14 7:47 ` Henri Altarac 2 siblings, 0 replies; 4+ messages in thread From: Henri Altarac @ 1994-10-14 7:47 UTC (permalink / raw) mcriley on BIX (mcriley@BIX.com) wrote: : For the level of documentation you're requiring I would suggest a paper : by Dave Parnas titled "A Rational Design Process: How and Why to : Fake It." Seriously! That paper distills everything I've come across This article was published in the February 1986 IEEE Transactions on Software Engineering. page 251. Henri Altarac ----- haltarac@rain.org (805)683-3045 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1994-10-14 7:47 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [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 1994-10-14 7:47 ` Henri Altarac
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox