[Sigia-l] Axure

[Jamie Foggon]

Matthew Hodgson:

"I then use it as a tool to communicate to developers the _intent_ of
the design. The last thing I want to do is to get into an argument
with developers about how to create the thing."

I'm interested to know how you handle changing scope throughout the
course of a project. I find it quite a hassle even keeping wireframes
up to date throughout a project, as requirements change and as a
result so do business rules - dependent on whats in scope / out of
scope. In our projects the IA document is used by testers to validate
functionality so it *has* to be correct.

The ability to demonstrate functionality quickly is great, but do you
have a separate detailed specification once the concept is approved?
or does the prototype evolve and have to keep pace with the final
product?

Jamie Foggon