It seems to me Wireframes are on the same level of design as a quick
Mindmap or other outline (Steve's white board system?) of the pages needed
for the web site, not a detailed spec or prototype.
You need a) something for the client to put their hands on, and get them
involved in the project (ie, give you a check) and visualize the process b)
a way of getting some kind of rough estimate of the scope and costs involved.
At 12:31 AM 2/23/01, Hal Helms wrote:
>Normally, Ken, I would leave this for DevNotes and prototyping. Typically,
>the people involved in the wireframe stage aren't going to be very helpful
>in this regards. Do you find otherwise?
>
>Hal Helms
>== See ColdFusionTraining.com for info on "Best Practices with ColdFusion &
>Fusebox" training ==
>
>
>-----Original Message-----
>From: Ken Beard [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, February 22, 2001 8:02 PM
>To: Fusebox
>Subject: RE: WireFrame Demo Online
>
>
>I dunno if this is already part of the discussion.. but is there a way to
>spec out what fields will be needed (exact text descriptions)?
>Seems like it might be nice to get this information all down in the spec
>phase rather than changing it in the design phase (devnotes).
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
