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-15 22:08:42 PST Path: bga.com!news.sprintlink.net!coyote.rain.org!coyote.rain.org!not-for-mail From: haltarac@coyote.rain.org (Henri Altarac) Newsgroups: comp.lang.ada Subject: Re: What to use when 2167A is too much Date: 14 Oct 1994 00:47:29 -0700 Organization: RAIN Network Message-ID: <37ld2h$pp6@coyote.rain.org> References: NNTP-Posting-Host: rain.org X-Newsreader: TIN [version 1.2 PL2] Date: 1994-10-14T00:47:29-07:00 List-Id: 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