My understanding is in line with Eugeo. A functional spec is that, functional, it describes what the app is to do, ie tasks. The design does not feature in that document. That is a separate document and separate requirement. Sure, wireframes can help the spec but it has nothing to do with how it works.
I use functional specs (or story writing in agile) so the developers can start programming immediately while the designers can start on the wireframes and ui. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46482 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
