Todd wrote: > Fortunately, instead of having a functional spec written before our > behavior design specs, we're finding more and more of our clients are > trying to do them in tandem with each other.
I'm doing my wireframes side-by-side with functional specs now: I'm in the middle of a project where the implementors will be using a commercial e-commerce package, so they are trying to only document non-standard functionality. They started by using screenshots from a demo-store to illustrate their work, but after we delivered the first iterations of wireframes they are replacing the screens with ours. (I am not satisfied with what they're documenting though; half of it is a rewrite of our specs. When we say "the 'edit' link takes the user to the page where she edits the relevant items" I'd expect them to document what software function is called and what the parameters are, not repeat our message.) Peter -- Peter Boersma | Senior Interaction Designer | Info.nl http://www.peterboersma.com/blog | http://www.info.nl ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
