Though I do not have any research to backup your question, I do have a lot
of experience with handing off my designs/code to developers.

Rule #1: Be as specific as possible! :)

Our team typically goes through many iterations of design with the business
clients and project manager before handing anything to developers. With
this audience, we are presenting "glossy" mockups of the application along
with any necessary large-print diagrams. We are doing everything possible
to sell the design to the clients.

At the point of handing off to developers, we repackage the designs into
something more relevent to the developers. We call this converted document
a User Interface Specification Document. This document has a screenshot of
the mockup with numbers next to all of the screen components (fields,
labels, images, widgets, etc). Later in the document we list the numbers
along with all the necessary data that a developer cares about: field
length, validation, onblur, onfocus, onload, size, height, width, etc...

In this way, we hand off a high-fidelity mockup with a detailed document
explaining how everything works on the screen.

Does that help?
Rob




On Tue, 4 Mar 2008 15:15:33 -0500, "Celeste 'seele' Paul"
<[EMAIL PROTECTED]> wrote:
> 
> Does anyone know of studies or other research that explicitly looks at
how
> developers are using design deliverables in practice?  Particularly
> integrating things such as wireframes in to functional specifications. 
Or
> even if developers "get" the wireframes and mockups we give them.  I've
> found
> that developers prefer annotated slides or a big numbered list of issues
> to
> having to read anything big, but those types of things don't look as nice
> as
> a fully written final report for the project manager.
> 
> Thoughts?
> 
> ~ Celeste


________________________________________________________________
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

Reply via email to