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-13 22:13:26 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!news2.near.net!news.delphi.com!BIX.com!mcriley From: mcriley@BIX.com (mcriley on BIX) Newsgroups: comp.lang.ada Subject: Re: What to use when 2167A is too much Date: 13 Oct 94 00:10:05 GMT Organization: Delphi Internet Services Corporation Message-ID: References: NNTP-Posting-Host: bix.com Date: 1994-10-13T00:10:05+00:00 List-Id: 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 Flight Simulation