Thursday, September 02, 2010

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

Business Analyst Forums & Systems Analyst Forums


AddThis Feed Button

AddThis Social Bookmark Button

Forums
 
  Modern Analyst Forums  Business and Sy...  Usability and U...  ScreenShots for Change Request Document
Previous Previous
 
Next Next
New Post 4/16/2009 3: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 5:06 PM
User is offline adrian
615 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
Modern Analyst Blog - Featured Business Analyst Blog
Business Analyst Community Blog - Post your thoughts!
 
New Post 4/16/2009 9:59 PM
User is offline kmajoos
127 posts
7th 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
  





Subject Matter Experts

Modern Analyst Community Expert

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:

  • General Analysis
  • Data Analysis & Modeling
  • Structured Systems Analysis
  • BPMN Modeling
  • UML Modeling
  • Rational Unified Process
  • Six Sigma
  • QA/Testing
  • Project & Personnel Management
  • User Interface Design
 


Privacy Statement  |  Terms Of Use
Copyright 2006-2010 by Modern Analyst Media LLC