Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!ncar!ncar.ucar.EDU!ftower
From: ftower@ncar.ucar.EDU (Francis Tower)
Newsgroups: comp.software-eng
Subject: Re: Modifiability
Message-ID: <11754@ncar.ucar.edu>
Date: 10 Jun 91 15:24:25 GMT
References: <11714@ncar.ucar.edu> <1991Jun7.165928.1903@weyrich.UUCP> <1849@uqcspe.cs.uq.oz.au> <1991Jun10.122656.18795@zip.eecs.umich.edu>
Sender: news@ncar.ucar.edu
Reply-To: ftower@ncar.ucar.EDU (Francis Tower)
Distribution: comp.software-eng
Organization: Climate and Global Dynamics Division, NCAR
Lines: 25

We are a long way from being able to generate code from specification languages
but we have also come a long way from hand coding in machine language.

It is possible to take a specification language and (with the help of a
domain-specific automated assistant) produce a prototype program.  This
prototype can then be deconflicted with the user.   Certainly, such a program
wouldn't be able to meet performance requirements in time and space, but it
would function.

As I mentioned before, specification languages are being used to do just this
and to gain insight into changes in the specification.  The emphasis of Formal
Methods has shifted to the area of specification because there demonstrable
progress is being made which can be transitioned to the corporate & government
world quickly (also there is more funding).

Much remains to be done in terms of going from a formal spec to an executable
program.  But the worth of using formal spec languages is being demonstrated
daily.  However, there is always a natural resistance to change, not just in
the fear of a new paradigm but also in finding/making the time to learn the
language, techniques, implementation, training of programmers,....  The old
ways work well enough and there is someone to ask questions.

True.  Software apprentices and prototypers in general do not yet exist.  But!
Specification Languages do and their use in maintanance/modification can
prevent the premature aging of code.