Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!uunet!dynsim1!litwin!jto
From: jto@litwin.com (John O'Beck)
Newsgroups: comp.software-eng
Subject: Re: Modifiability
Message-ID: <1991Jun10.130548.13815@litwin.com>
Date: 10 Jun 91 13:05:48 GMT
References: <1991Jun5.201807.13286@netcom.COM> <62683@siemens.siemens.com> <11714@ncar.ucar.edu> <1991Jun7.165928.1903@weyrich.UUCP>
Distribution: comp.software-eng
Organization: Litwin Process Automation
Lines: 13

orville@weyrich.UUCP (Orville R. Weyrich) writes:

> ...>2) The amount of work done prior to beginning coding should be minimized.
>   [At first blush, this is contrary to conventional wisdom. But it is not
>   really, if the coding environment supports stepwise refinement and 
>   consistency checks along the way. Consider the use of Ada as a PDL as
>   movement in this direction.]
>   

    How dows such a methodology allow communication between *many* programmers
    on a large project?  How are changes to be communicated to and/or
    approved by management?  Do all the bean counters need to learn Ada?
    Stepwise refinement of what?  Consistency with what?