Thought I'd de-lurk to share that what John wrote below is loudly seconded
by my husband who's a Software Process (CBA-IPI_type) expert. In his words,
John just described the risk of blurring "requirements gathering" with
"design"
That was a *great* analysis John - thanks for taking the time to write it.
- - - Jeanne
>From: "John Quarto-vonTivadar" <[EMAIL PROTECTED]>
[snip]
....
>First off, I think the difference in opinion relates directly to your
>comment above that "wireframes could be used as a tool during development".
>I believe that is in error since no development should be done until
>wireframing is complete. They are two temporally distinct processes and
>development cannot and should not be attempted during specification phase.
>I'll go out on a minor limb and suggest, without proof herein, that anytime
>any of us have ever gotten screwed on a project was a project in which the
>distinction between specification phase and development phase was not
>observed.
....
[snip]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
