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,9b8c5fefd3f42c8d
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1994-09-28 02:19:37 PST
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!vixen.cso.uiuc.edu!sdd.hp.com!svc.portal.com!portal!cup.portal.com!Lee_Robert_Willis
From: Lee_Robert_Willis@cup.portal.com
Newsgroups: comp.lang.ada
Subject: Re: DoD STD-2167A?
Message-ID: <123699@cup.portal.com>
Date: Tue, 27 Sep 94 19:20:58 PDT
Organization: The Portal System (TM)
References: <35mqdo$gqt@theopolis.orl.mmc.com> <85BA3244E26@annwfn.com>
  <rodc.780554008@hawk>
Date: 1994-09-27T19:20:58-07:00
List-Id: <comp.lang.ada>

>merlin@annwfn.com (Fred McCall) writes:
>
>>In <35mqdo$gqt@theopolis.orl.mmc.com> dennison@romulus23.DAB.GE.COM Ted Denni
s
>on writes:
>
>>>Of course, being an Adaphile, I believe 2167A's emphasis on quality IMPLIES
>>>a use of Ada.
>
>>Not to mention its insistence on reams of meaningless verbosity in the
>>way of documentation. 

>Not to mention those who blindly follow 2167A and fail to relize that
>it can be tailored to meet _THEIR__ needs.

Usually the tailoring must be done way in advance, i.e. if you're going
to tailor the requirements docs, you must get the customer to sign off
on it before the requirements analysis of the contract.  If your going
to tailor the design docs, it must be done before the design phase of 
the contract is entered....  

It has been my unfortunate experience that the people involved before 
phase X don't know or give a damn about the 2167A docs for phase X, and 
thus very little tailoring happens. :-(

   -lee     Lee_Robert_Willis@cup.portal.com