Functional spec is a summary of the functional analysis I make. It contains all possible features description, the screen flow for all interactions (regular flows, errors, alternative flows).
I use UML diagrams to describe features in use cases and show how the process looks like. Wireframes or screenshots of working prototypes are used to better explain the UI. If needed or required I am putting there some usability/accessibility guidelines and remarks. This helps avoid missing pages/views. Designers know which functionalities should be on the screen, developers know how to build the site (what is going where and how). A very handy stuff if written short and precisely (no one wants to ready another encyklopedia). In general, the doc has probably the same structure as Siegy Adler described. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46618 ________________________________________________________________ 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
