I prefer to stick with 'prototype' for discussion within the community, but I often use 'front-end' or 'user interface' when talking with the client. You can even tailor your jargon to the client's domain knowledge. When working for an auto repair company, I called the prototype "the tool box" (that's what they work with); when I working for an aircraft instrumentation firm, I called it "the cockpit".
The problem with changing terminology within the community is the inertia of existing documentation, instruction, and discussion. The next newbie that drops by after a terminology change says, "I've read all of fusebox.org; what happened to prototypes? Doesn't Fusebox use them anymore?" - Jeff On 10 Jun 2002 at 16:38, Mark Evely wrote: > How about something based around modeling/process modeling/ > analyses/Prototype/storyboard > > Protomodel > > Storymodel > > Protoanalysis > > Storyboard-analyses > > Proto-storyboard > > or does any one know any latin? > > > > -----Original Message----- > From: Steve Nelson [mailto:[EMAIL PROTECTED]] > Sent: Sunday, June 09, 2002 7:11 PM > To: [EMAIL PROTECTED] > Subject: Re: Prototype or what? > > > 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 ==^================================================================
