In association with the
Quick Links: Articles MA Blog Community Blog Templates Books BA Humor Events Jobs Interview Questions RSS Feeds
It depends on how you're planning to use the UI designs created by this process. If your only goal is to communicate the changes but not maintain "live" specs for these UIs then go with option 2. It's efficient and effective. You could also add these screenshots in a PowerPoint presentation and put the screenshot on the right side and the annotations with arrows on the left side (or next to) - almost like a storyboard.
If your goal is to create functional specs which you're planning to maintain in the future then you might want do the above plus create the new To-Be screens in a tool which allows you to easily modify them later. For example: Dreamweaver for web-based screens, Visio for windows mockups or a visualization tool such as iRise.
Hope this helps!
- Adrian
Go with option 2,
Why? Users can then see the changes that you envisage. They can also more readily realte to "their" screens as they have some knowledge of them. Some users are concrete thinkers and they do have difficulty conceptualising "new" screens, especially if the interface is very different.
Adrians suggestion has merit; and option 2 is professional.
warm regards,
K
Craig Brown -General Analysis -Project & Personnel Management View Posts View Expert's Biography
Guy Beauchamp -Data Analysis & Modeling -Structured Systems Analysis View Posts View Expert's Biography
Jarett Hailes -Agile Methods View Posts View Expert's Biography
Kieran Creaton -Requirements Gathering & Facilitation Techniques View Posts View Expert's Biography
Perry McLeod -UML Modeling -Project & Personnel Management View Posts View Expert's Biography
The Community Expert is just one way that Project Members volunteer their time to help the Modern Analyst Community. Want to become a Community Expert in one of the following areas? Submit yourself to be selected as a Project Member.
Available topics include:
Advertising Opportunities | Contact Us