[Sigia-l] Axure and Development Specification

For any Axure fans out there who are helping to develop digital
applications, could you please share how you use Axure to specify
development requirements? Tips, tricks, personal experiences and war
stories are greatly appreciated.

I'll share with you my own experience. Initially I have tried to use the
specification output from Axure, but just found it too inflexible and too
unwieldy. I ended up importing the spec in Google Docs and then a colleague
and I manually annotated the document, which was easier than specifying in
Axure, but still isn't the method I would recommend.

I have heard of others who specify a use case for every interaction and
then publish the use case to the clickable prototype. I have not tried this
but am curious what others think.

I have also heard of others who create sticky notes as dynamic panels that
can be turned off and on as needed in the clickable prototype to describe
behaviors.

What are your thoughts? In this day and age when building digital products,
is a massive spec document still needed? Is just a clickable prototype
enough with some annotation?

Of course nothing replaces face to face communication and that will always
be part of the development process, but what I'm trying to get a better
sense of is the level of specification needed for distributed teams and the
best form of that specification and how it's maintained specifically when
using Axure.

Best,

-- 
-Tom
------------
2015  IA Summit
April 22-26, 2015
Minneapolis, MN
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: [email protected]
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l