For web apps we've used similar documentation to what Paul has described. Sometimes we have a customer requirement to write use cases that trace to the requirements document. In some cases we get a rough requirements document from the customer and then add to it as needs are uncovered through user interviews and testing, and in other cases we write it. We roughly sort everything into 3 groups of documents:
User interviews, survey results and test results Requirements document, use cases, concept wireframes Design document which includes design style info, functional specifications, navigation and site structure, general info about the purpose and audience of the app For our purposes we presented the usability interviews and test feedback in a summary to the customer. The requirements related documentation is packaged for the customer and archived for developers who may work on it in the future. The design document is what the interaction designer turns over to the app developer. The web app and desktop app documentation for us is about the same just adjusted slightly to fit the medium. Like web navigation might lead to a site diagram, but if we're on a desktop app this might be a series of task flow charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46048 ________________________________________________________________ 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
