Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Usability and U...  ScreenShots for Change Request Document
Previous Previous
 
Next Next
New Post 4/16/2009 4:03 AM
User is offline aivern
1 posts
No Ranking


ScreenShots for Change Request Document 
I am doing a UI Change Request Spec and have two options in mind currently... 1) Create sketches of the as is system and sketches of the to be system 2) Do some screen shots of the as is system and annotate it with some editor. Option 1 will take forever and it is more trouble than the document will give back... Option 2 feels rather unprofessional... What would you do?
 
New Post 4/16/2009 6:06 PM
User is offline Adrian M.
741 posts
3rd Level Poster




Re: ScreenShots for Change Request Document 

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


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 4/16/2009 10:59 PM
User is offline KJ
243 posts
6th Level Poster


Re: ScreenShots for Change Request Document 

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

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Usability and U...  ScreenShots for Change Request Document

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...

 



Upcoming Live Webinars




 

Copyright 2006-2021 by Modern Analyst Media LLC