Your SlideShare is downloading. ×

UPA 2011 - Better Usability Through Visualization

958

Published on

Better Usability Through Visualization …

Better Usability Through Visualization

Visualization is a requirements elicitation and documentation technique which significantly reduces or eliminates the common problems of software definition.

Practitioners of this technique can expect improved usability, increased innovation, lower development costs and faster project time lines. This workshop provides attendees with the ingredients for successful use of visualization.

Published in: Business, Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
958
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. UPA  –  Be(er  Usability  Through   Visualiza8on  Chuck  Konfrst,  Senior  Visualiza8on  Designer  /   Director  of  Branding  &  Communica8ons  
  • 2. Welcome!   Agenda   • Introduc8ons     • What  Is  Visualiza8on?     • Visualiza8on  Demonstra8on   • Group  Breakout     • Mock  Project  Requirement  Sessions   • Ques8ons  &  Answers   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 3. Introduc8ons   • Name   • Company   • Role   • What  you’d  like  to  get  out  of  the  workshop   • Favorite  Cartoon  Character  &  Why   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 4. Visualiza8on   What  Is  Visualiza8on?   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 5. “68% of projects fail, run late, or are OVER budget.”! - The Standish Group, 2009 Chaos Summary Report“70% of REWORK is attributed to correcting requirements errors.” ! - Meta Group “30% of project costs are REWORK .”! - Forrester Research ©  2011  OneSpring®    All  Rights  Reserved.  
  • 6. Visualiza8on  for  So]ware  Defini8on  Today, the ability to pre-visualize a softwareapplication has become areality.Using scenarios as the initial“sketches” of a storyboard,visualization tools allowsoftware definition teams tomodel entire applicationsbefore writing a single line ofcode. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 7. Visualiza8on  for  So]ware  Defini8on  AutoCAD/CAMtechnologies thatrevolutionized theautomotive, aeronautical,and constructionindustries.Now, softwarevisualization tools cansimulate applications andhelp stakeholders trulyunderstand process flow,behaviors, look and feel,and other aspects of theapplication before it isbuilt. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 8. The key benefit to visualization is the ability to validate your requirements from the start with stakeholders This, in turn, leads to the realization of the following benefits: •  Reduction of Requirements Cycles by at least 30% •  Reduction of Requirements Defects by at least 80% •  Reduction of Project Delivery Times by at least 35% •  Improved User Experience •  Increased Innovation© 2010 OneSpring, LLC. All Rights Reserved. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 9. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 10. Most SDLC methods define requirements late in the lifecycle. These requirementstypically lack any experiential aspect. They represent only functionality, notexperience. Traditional ©  2011  OneSpring®    All  Rights  Reserved.  
  • 11. The  New  Approach  Visualization occurs at the beginning of the lifecycle and provides stakeholders theability to experience and validate requirements from the start. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 12. The  New  Approach  Visualization is a framework for how to better innovate and collaborate ©  2011  OneSpring®    All  Rights  Reserved.  
  • 13. The  Benefit   Accelerating the time to understanding and consensus provides a far greater return on investment. Visualization100%50% Traditional 0% ©  2011  OneSpring®    All  Rights  Reserved.  
  • 14. Visualiza8on   Visualiza8on  Tools   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 15. Caveats -  The Tools aren’t as important as ‣  The People ‣  The Process ‣  The Culture ©  2011  OneSpring®    All  Rights  Reserved.  
  • 16. Tools •  iRise •  Axure •  Balsamiq •  Blueprint •  Flairbuilder •  JustInMind •  IBM Rational Composer •  Visual Studio 2010 Ultimate •  Adobe Flash Catalyst •  Visio/Omnigraffle •  Microsoft PowerPoint ©  2011  OneSpring®    All  Rights  Reserved.  
  • 17. Visualiza8on   Demonstra8on   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 18. Visualiza8on   Previsualiza8on   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 19. The  Paradox  While the software definitionprocess and its artifactshave multiplied over theyears, with the rise ofmethods such as Waterfall,Rational Unified Process,Agile, and more – thesurprising fact is thatprojects are failing at ahigher rate than everbefore. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 20. Increased  Complexity  and  Costs  This failure occurred becausesoftware applications wererapidly increasing in both sizeand complexity, outstrippingmethodologies fordevelopment.While traditional processesand artifacts were helping,more efficient, effectivecommunication and elicitationwas needed to ensure projectsuccess. The shortfall left byestablished methods wassignificant. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 21. Consumer  Demand  The motion picture industrywas experiencing the samedilemma.Audiences were more savvyand demanding more fromentertainment. With the barraised, filmmakers alsoneeded to improve theirprocess and tools to moreeffectively create their art. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 22. Previsualization•  is a collaborative process that generates preliminary versions of applicationfeatures, functionality and process flows in a low-resolution format•  enables the project stakeholders to more effectively communicate a !shared vision and understanding of a project through visual exploration ©  2011  OneSpring®    All  Rights  Reserved.  
  • 23. Previsualiza8on  •  Enables true cross-functional collaboration•  Provides a preliminary project experience, from concept to use•  Includes application features, functionality, and process flows in a low- resolution format•  Provides stakeholders with a source for a single, shared vision•  Enables rapid visual exploration of project goals and alternate solutions! ©  2011  OneSpring®    All  Rights  Reserved.  
  • 24. Previsualiza8on  •  For the first time, a director, cast, and crew could envision every shot, sequence, and f/x in a movie before actual production was underway.•  Every aspect of a movie could be planned and analyzed before shooting began—and nuances, special effects, and point of view could be thoroughly explored.•  Director, cast, and ! crew could complete! many takes on a scene! or sequence, all before! filming started. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 25. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 26. Previsualiza8on   Live  Website   Header  Hotel  Name  Progress  Bar  Reserva8on  Process   Hotel  Photo  Check-­‐In  Date   Personaliza8on  Content  Slots  Check-­‐Out  Date  Rate  Preferences  Group/Corporate  Numbers  Number  of  Rooms  Number  of  Adults  Number  of  Children  Smoking  Preference  IATA  Number   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 27. Low  Resolu8on   Live  Website   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 28. Medium  Resolu8on   Live  Website   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 29. High  Resolu8on   Live  Website   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 30. Levels  of  Fidelity  Fidelity  Level   Visual   Func1onal   Requirements  Previsualized   •  Text  descrip8on  of  key  page   •  Basic  descrip8ons  provided   •  Ini8al  concepts  and  ideas   areas   •  Text  or  placeholders  describing   •  Vision  statements   behavior   •  High  level  business  goals  Low   •  Basic  elements  present  at  level  of   •  Sta8c  pages  lacking  dynamic   •  High  level  requirements  only   detail  sufficient  for  basic   behavior   •  Documenta8on  of  what  is  not   comprehension,  but  no  more   •  Text  descrip8on  or  blocked  in   necessarily  shown  in   •  Not  polished   areas   visualiza8on   •  Simple,  linear  naviga8on  Medium   •  Blocked-­‐in  text  and  objects,   •  Blocked  in  elements  like  ac8ve   •  Special  condi8ons  included   lorem-­‐ipsum   form  fields     •  Business  process  scenarios  and   •  Interac8ve  wireframes  and   •  Deeper  linking  between  page-­‐ basic  traceability   advanced  onionskinning   level  elements,  allowing  user  to   •  Ini8al  business  rules   •  Usability/UX  elements   interact  with  visualiza8on   •  Ini8al  func8onal  requirements,   introduced  and  testable   par8cularly  those  not  visualized   •  Selected  branding  elements  may   •  Ini8al  field  level  defini8ons   be  applied  High   •  Full  visual  skinning   •  Behaves  like  “the  real  thing”   •  Con8nued  field  level  defini8ons   •  Realis8c/highly  evolved  design   •  System  inputs  opera8onal  and   •  Full  traceability   accurate   •  Capture  of  func8onal   specifica8on  elements   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 31. Visualiza8on   Joint  Applica8on  Modeling®   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 32. JAM  Session®  The session is comprised of these essential “ingredients”… +   +   +   Small  Group   Rapid   Visualiza8on   Flow   Collabora8on   Itera8ve   Design   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 33. Collaboration in small groups provides an effective means of problem solving within a structured environmentSmall  Group   Complex problems that go beyond the routineCollabora8on   require the communication of shared knowledge to create viable solutions/approaches ©  2011  OneSpring®    All  Rights  Reserved.  
  • 34. The roles “match” the work environment and support the task flow… Documentation Screen Visualization ScreenAnalyst “Left Brain” Producer Designer “Right Brain” Facilitates Flow Business IT SME on SME on “How?” “What?” ©  2011  OneSpring®    All  Rights  Reserved.  
  • 35. Insight – observation to gain valuable knowledge and context on the business, customer and technologies Clarity - design activities that crystallize the gathered insights to form a model of the experience Focus – socialization and measurement of the experience model to provide continuous improvement and validation©  2011  OneSpring®    All  Rights  Reserved.  
  • 36. Pairing documentation with visualization means that the requirements written by the Visualization Analyst:" •  Reflects the wishes, wants, and needs of the stakeholders 
 Documentation" •  Aligns (traces) directly to visualized pages of the future system 
 •  Coincides with a rich, interactive vision of the future system" •  Eliminates ambiguity of verbally elicited requirements" • 
© 2010 OneSpring, LLC. All Rights Reserved. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 37. ”Flow also happens when a person’s skills are fully involved in overcoming a challenge that is just about manageable, so it acts as a magnet for learning new skills and increasing challenges. If challenges are too low, one gets back to flow by increasing them. If challenges are too great, one can return to the flowFlow state by learning new skills.” - Mihaly Csikszentmihalvi (July. 1997) Psychology Today ©  2011  OneSpring®    All  Rights  Reserved.  
  • 38. A key aspect to generating the Flow includes both the environment in which the JAM Session takes place and the mental investment by the stakeholders Goals are clear Feedback is immediate Balance between opportunity & capacityFlow Concentration deepens The present is what matters Control is no problem Sense of time is altered Loss of ego ©  2011  OneSpring®    All  Rights  Reserved.  
  • 39. Visualiza8on   Mock  Session   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 40. © 2010 OneSpring, LLC. All Rights Reserved. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 41. Session  •   Descrip8on  of  the  Project    •   Introduc8on  of  Stakeholders  •   Introduc8on  of  the  Requirements  Team  •   Visualiza8on  of  Project  Requirements   ©  2011  OneSpring®    All  Rights  Reserved.  
  • 42. What Can You Do? •  Use visualization as a tool during requirements elicitation •  Partner with a Business Analyst •  Don’t worry about the tool, focus on the people & process© 2010 OneSpring, LLC. All Rights Reserved. ©  2011  OneSpring®    All  Rights  Reserved.  
  • 43. Visualiza8on   Now  It’s  Your  Turn!   ©  2011  OneSpring®    All  Rights  Reserved.  

×