Path: news.daimi.aau.dk!news.uni-c.dk!sunic!sunic.sunet.se!news.sprintlink.net!gatech!EU.net!uunet!in1.uu.net!news1.digital.com!nntp-hub2.barrnet.net!nntp-sc.barrnet.net!tss.com!news From: Brian Strelioff Newsgroups: comp.object,comp.lang.beta,comp.lang.c++,comp.lang.eiffel,comp.lang.python,comp.lang.sather,comp.lang.smalltalk Subject: Re: Rapid Prototyping + statically-typed OOPLs? Date: 13 Jul 1995 18:48:46 GMT Organization: BKS Systems, Inc. Lines: 29 Distribution: world Message-ID: <3u3pqe$olp@newsflash.tss.com> References: <805548287snz@galacta.demon.co.uk> NNTP-Posting-Host: 160.101.81.107 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (X11; I; SunOS 4.1.3_U1 sun4m) X-URL: news:DBMALy.6p@aldur.demon.co.uk Xref: news.daimi.aau.dk comp.object:33476 comp.lang.beta:460 comp.lang.c++:128916 comp.lang.eiffel:9231 comp.lang.python:5010 comp.lang.sather:1932 comp.lang.smalltalk:24362 Neil Wilson wrote: >Why oh why do people insist on using the term Prototyping in conjunction >with Information System development? Do you intend to mass-produce it >afterwards? (Congratulations on mastering the 'cp' command). Are you >going to write a new system afterwards that is the same but on a larger >scale? (don't forget to change that bubblesort will you). Prototyping is >a horrible 'Humpty-Dumpty' word. .. >If you're going to develop a system then set out to develop one. Use the >same control/feedback techniques and methods at the beginning as you >would use at the end. I'm afraid that you have to handle problem space >and solution space symbiotically throughout development. One is never >without the other. .. To me, prototypes are components developed for alternative evaluation purposes, particularly when there is no clear choice about which approach is best. For example, many application level features/enhancements involve some degreee of space/time tradeoff, and without "prototyping" and analyzing the alternative approaches no competent decision can be made. >Requirements and design are never fully known. They always continue to >evolve. Hopefully the rate of change will decrease over time, but don't >bank on it. Development never ends until the system is obsoleted. Like art: Never finished, just abandoned.