I am planning on entering the Interaction '10 student competition,
which requires submissions in the form of a process book. However, I
am not familiar with the documentation style of process books. Can
anyone recommend any good examples or guidelines to follow when
creating one? I can speculate about what should be included but would
like to be sure that I am on the right track.
Thanks in advance!
MSI Candidate 2010
School of Information
The University of Michigan www.yellowbreeze.com
The post is well articulated, to me at least. But there was only one
response. So I am reposting this thread because, frankly, there is a
fundamental question that hasn't been answered and that I feel
deserves attention from the community.
Im an advocate for writing functional specs. Here are 3 reasons why I
believe specs facilitate development of Websites and applications:
1) Specs serve as the blueprint for the developer, which enables them
to review the project and start coding without delay. Would you build
a house without a written plan?
2) Specs that are reviewed/approved by project stakeholders help
ensure that the finished product meets expectations.
Looking for a extremely detail-oriented (nearly OCD) UX designer with
3-5 years experience in mobile user experience requirements
documentation - wireframes, workflows, etc. for a 6 week contract in
NYC. Must be able to collaborate from our offices in Hudson Square
area for a majority of the engagement. This is a fast and intense
schedule and we can only entertain rock star level designers.
There¹s been a fair amount of discussion here about documentation formats
and software used to produce wireframes, prototypes, and so on. But how do
people manage an entire specification? I have been using a hand-coded
intranet site, controlled via subversion; but my team is growing and I¹m
considering other ways to manage the information. Web access and formats
(not, for instance, Word documents) and some sort of version control are my
main requirements, along with relative ease of editing. What do people use?
I'm not sure if this is the correct use of Axure, but I like to create flows and link the objects to various wireframes. I could use specifications but you lose the interactivity between the flow and wireframe.
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.