Steve

The example of check box vs. radio button doesn't convince me. Normally 
i would have checkboxes for "I want this, and this, and this and this." 
Radio buttons for "I have a 28k modem, or I am super groovy connected". 
These things relate directly to the DB/Business model. If this sort of 
thing has not been ironed out at what I call the "wireframing/functional 
spec stage" then I would consider that we had missed something

Cheers

Richard

Steve Nelson wrote:
> Hmmm.
> 
> I have had this conversation with a Hal a few times.
> 
> I think prototype is the wrong word for what we're building. It's really 
> the
> "Front-End".
> 
> Essentially our use of the word "Prototype" is a full scale model of the
> application without the engine inside.
> 
> You have to build the front end at some point. FLiP suggests building 
> the
> front-end first instead of last. That way when the change requests come 
> in (they
> will guaranteed!) you can mold the front end without affecting the 
> backend.
> 
> These change requests ensure the client gets what they want, so the less 
> you
> need to change the cheaper it will be. For example, it's easier to 
> change
> type="radio" to type="checkbox" than to change the entire database 
> structure
> plus the SQL queries, plus the associated CF plus the HTML.
> 
> The word prototype is bad because it makes you feel like you're going to 
> throw
> it away, which is not correct. The code for the front end will be used 
> in the
> final application.
> 
> Steve Nelson
> 
> 
> Richard Tugwell wrote:
> 
> > This topic spins out of the Flip/protoyping thread which has been
> > running for a bit now.
> >
> > I'm interested in what people consider a prototype.
> >
> > To take an analogy from other industries, there was a prototype of the
> > Comet airliner of the 1950/60's and there was also a "mock-up". The
> > difference was that the prototype could fly, and the mockup was made of
> > balsa wood and plasticene. (could be wrong on the details) Does anyone
> > see any similarities between this, and the model(s) of software
> > development that we are talking about?
> >
> > Cheers
> >
> > Richard
> >
> 
> 
> 

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to