I am seeking some advice on how to document our design requirements for
our business stakeholders to review and to hand off to an external
We are conducting a redesign of some major elements on our website. We
have an internal user experience team, but we do not have enough
resources to complete the project internally, so we're hiring an
external design firm.
I've been coordinating usability research to inform the design, and I
have very solid thinking about the design direction.
Anyone use a Form and Behavior spec in their workplace?
If so, do you have a doc you could share? Am just looking for the
content and format of the doc that would serve as a deliverable to the
Where could I find good examples of web application system documentation? Are there best practices and standards that I could rely upon?
We are customizing a web ordering (which we are proprietary) for a client and just delivered its system documentation (site maps, processes flows with notifications, high level interactions between web servers and databases, system structure description, and main screens descriptions not at the object level but with emphasis on main functionalities).
I am in the process of creating a document that a UI designer/information
architect would ideally extract from and record in his first few meetings
with the clients/development team. It should also serve as a document that
the team can go back to and refer in case of doubts emerging in course of
development. At the least, the document should act as a base for the UI
designer to design the information flow and user interaction.
Can anybody help me with that? Is there such a document ready? Or some such
material in place? Any kind of help is appreciated.