Draft
1. Why bother?
Because this is expenssive to us, especially for consultants: very time consuming, detailed, and with RIA's increacingly complex to tell a good compellng story.
Heuristics are changing. (Which is a nother story all together).
Ability to seperate the tree from the forest, prioratize and consider recommandations.
I used Filemaker as a database to store screen level comments, and there was some ability to create simple interaction flows and document navigation and workflow issues
But with RIA's it does not scale.
Using Word or other word processing tools is also a possibility, but, Word does not handle such ducuments gracefully and you. can loose valuable time on fixing formmating issues.
A presentation tool such as Power point may be another option but is does not handle tabular data very well, nor extended details
So, in looking to increace the value of the excerise - why are we conducting this, what are the expectations, how can we provide most value and finally - reduce the pain and yes, increace profitability of the chore - one option for those who are using a simulation too
Create sets of annotations and fields (show screen)
What heuristics to capture? Glossary I sometimes find a need to respond to the particularities of the application and modify the heuristics I'm covering because they a more relevant to the work.
Making such changes can be fairly simple
2 Creating the file
Take screen captures useing Snagit or similar. naming convention - effort to maintain the flow - example here
Importing to axure
Liinking. - when this is done, we end up with a simulation of the the screens -- as they were at the time of evaluation
(In some fast paced organization the ui may change while you are still laboring on the report.)
