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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,c59f452174bd555
X-Google-Attributes: gidfac41,public
X-Google-Thread: 103376,c59f452174bd555
X-Google-Attributes: gid103376,public
From: leew@micrologic.com (Lee Webber)
Subject: Re: Use of DBC as "executable SRS": scaling problems
Date: 1997/08/13
Message-ID: <33f1d19d.8551657@wizard.pn.com>#1/1
X-Deja-AN: 263945497
References: <870354811.9948@dejanews.com>
Organization: Pioneer Global
Newsgroups: comp.lang.ada,comp.lang.eiffel
Date: 1997-08-13T00:00:00+00:00
List-Id: <comp.lang.ada>


On Thu, 31 Jul 1997 08:41:32 -0600, card@syr.lmco.com wrote:

>In my initial post, I said that I thought it would be unwise
>to try to "code" the software requirements specification for a
>complex software component as a set of assertions (boolean
>expressions) due to problems of scale.... When that
>requirement is changed, the impact of the change could be
>significant since "dual maintenance" is required- that is, the
>assertions must be checked and changed as necessary as well as
>the method bodies.

Note that the same criticism could be levelled at
double-entry bookeeping.