functional specs are important to all stakeholders. i can't imagine a ux/interaction designer not provide functional specs with a finished wireframe.
Especially if you are not the actual front-end developer, functional specs is the communication medium between the designer, prototyper, engineers, and QA. Without it, everyone will interpret the interactions, scenarios in different ways. I think the better question is when to provide functional specs. If you are just doing concept designs/sketches, I think it's better to keep it high-level and allow stakeholders to review the design without specs so the use cases are open to interpretation. However, once you start to work on a UI design/wireframe where it will resembles the finish product, you should also spec it out so engineers/prototypers can develop the application based on the spec and the design, and QA can use the spec to test scenarios and use cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46833 ________________________________________________________________ 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
