Newsgroups: comp.object,comp.lang.beta,comp.lang.c++,comp.lang.eiffel,comp.lang.python,comp.lang.sather,comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news4.ner.bbnplanet.net!news3.near.net!paperboy.wellfleet.com!news-feed-1.peachnet.edu!gatech!news.sprintlink.net!news.wwa.com!rcm!rmartin
From: rmartin@rcmcon.com (Robert Martin)
Subject: Re: Rapid Prototyping + statically-typed OOPLs?
References: <805548287snz@galacta.demon.co.uk>
Organization: R. C. M. Consulting Inc. 708-918-1004
Date: Thu, 13 Jul 1995 15:46:20 GMT
Message-ID: <1995Jul13.154620.4333@rcmcon.com>
Lines: 45
Xref: glinda.oz.cs.cmu.edu comp.object:34987 comp.lang.beta:464 comp.lang.c++:138234 comp.lang.eiffel:9572 comp.lang.python:5052 comp.lang.sather:1985 comp.lang.smalltalk:25834

"Dr. Rich Artym" <rartym@galacta.demon.co.uk> writes:


>For example, has anyone developed a genuine prototype in C++ using a very
>coarse or minimally-specific class organization, and then repeatedly changed
>it, and how did this work out?  Was there an important negative impact when
>major internal class surgery was needed?  Do you have any specific advice
>for others that may wish to carry out R.P. using (say) C++ or Eiffel?

I and my associates have been embroiled in a significant project for
the last couple of years.  Prototyping is an important part of this
project because the customers does not have precise functional
specifications.  They work out what the programs ought to do by
looking at our prototypes and then adjusting.

There may be better languages than C++ for operating in this kind of
environment, but we currently have no complaints.  We are using
Borland C++ and OWL.  We have developed a framework of classes that
allows us to put a prototype together if very short order, and then go
through a number of iterations in an economical fashion.

The critical aspect of this ability to rapidly prototype is the afore
mentioned framework.  This was a large effort on our part.  It has
evloved and grown over the last couple of years to the point where the
prototypes can now be generated very quickly.  However, at the outset,
when the framework did not exist, prototyping was very slow.
Purposely slow.  We were investing more effort into the creation of
the framework, than we were into the prototypes.  

Another issue regarding the prototypes is that they all use the same
overall design.  This design is provided by the framework.  Thus, the
prototype is not so much a design experiment as it is an *interface*
experiment. 

This has worked very well for us.  Our client is happy, and we have
had a very gratifying C++ experience.  I feel safe in recommending the
approach.



-- 
Robert Martin       | Design Consulting   | Training courses offered:
Object Mentor Assoc.| rmartin@oma.com     |   OOA/D, C++, Advanced OO
2080 Cranbrook Rd.  | Tel: (708) 918-1004 |   Mgt. Overview of OOT
Green Oaks IL 60048 | Fax: (708) 918-1023 | Development Contracts.
