Your SlideShare is downloading. ×
Prototyping for Usability Testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Prototyping for Usability Testing

4,045
views

Published on

A practitioners guide to the prototyping process and how it plays a part in an audience centered design lifecycle. This presentation features Axure 5.5. This presentation was originally presented to …

A practitioners guide to the prototyping process and how it plays a part in an audience centered design lifecycle. This presentation features Axure 5.5. This presentation was originally presented to the New Jersey Chapter of the Usability Professional Association on 01/20/2008 at Rutgers University, Busch Campus.


0 Comments
6 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,045
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
6
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
  • iRise – Power at a cost Pros: Corporate standards Data Simulation is far superior to any other prototyping tool Integration with a suite of other business analysis (requirements gathering & management) tools Cons: Integration with a suite of other business analysis (requirements gathering & management) tools Cost prohibitive Requires iRise Player Learning Curve
  • iRise – Power at a cost Pros: Corporate standards Data Simulation is far superior to any other prototyping tool Integration with a suite of other business analysis (requirements gathering & management) tools Cons: Integration with a suite of other business analysis (requirements gathering & management) tools Cost prohibitive Requires iRise Player Learning Curve
  • Visio - Flat Engineering Tool > Overkill for Wireframes Print based Some basic interaction (linkage)
  • Visio - Flat Engineering Tool > Overkill for Wireframes Print based Some basic interaction (linkage)
  • Dreamweaver - Development tool for creating production ready applications Creates HTML (but why are we worrying about HTML during the design phase?) Requires experienced user to be rapid and iterative No Annotations
  • Dreamweaver - Development tool for creating production ready applications Creates HTML (but why are we worrying about HTML during the design phase?) Requires experienced user to be rapid and iterative No Annotations
  • Transcript

    • 1. Prototyping with Axure Jan 20, 2008
    • 2. Agenda
      • Prototyping
      • What is Axure?
      • Why Axure?
      • Where Does Axure Fit into the UX Process?
      • How-to’s
        • Wireframes
        • Sitemaps
        • Simple Interactions
        • Complex Interactions
        • High Fidelity Prototypes
        • Pre-built Widgets
      • Prototyping Tips
      • Q&A
    • 3. Mark DiSciullo
      • MISI - User Experience Strategist Clients: Merck, Pfizer, AstraZeneca, D&B, PriceWaterhouseCoopers, Merrill Lynch
      • Established a User Centered Practice at TD Waterhouse Now TD Ameritrade
      • Interactive Design background working with clients such as: Nike, Kodak, IBM, Ellis Island Foundation, Microsoft, Chicago Symphony Orchestra
    • 4. Prototyping
    • 5. Prototyping Seeing is Believing!
    • 6. This is a prototype…
    • 7. This is a prototype…
    • 8. This is a prototype…
    • 9. These are prototypes…
    • 10. Why Prototype?
      • Prototyping makes it easy to perform user testing early
      • Provides support through the entire design lifecycle
        • It’s a communication tool!
        • Better Client Approvals/Buy-in
        • Developer Walk-Thru’s
        • Living Document
      • Saves $$ and reduces risk
    • 11. What is Axure?
    • 12. What is Axure? Axure RP is one of the leading tools for rapidly creating wireframes, HTML prototypes and specifications for applications and web sites.
    • 13. Why Axure?
      • Axure Pros:
      • No Coding Required
      • Quickly Renders Functional HTML Prototypes
      • Support High and Low Fidelity Prototyping
      • Drop and Drag Interface
      • Site Map Creation
      • Supports Basic to Advanced Logic
      • Data Simulation
      • Collaborative Workspaces w/Version Control
      • Cost $589 (discounts start at 5 users)
      • Axure Cons:
      • HTML prototype doesn’t produce code that can be easily reused for development
    • 14. Axure vs iRise
    • 15. Axure vs iRise
      • iRise Pros:
      • Corporate Standards
      • Superior Data Simulation
      • Easy to use
      • Integration with a suite of other Business Requirements Management tools
      • iRise Cons:
      • Integration with a suite of other Business Requirements Management tools
      • Must use iRise Player to view prototype
      • Power comes at a cost … 6000k + per seat
    • 16. Axure vs Visio
    • 17. Axure vs Visio
      • Visio Pros:
      • Readily Available (MS Office)
      • Loads of Stencils
      • Huge User Base
      • Annotations Well Supported
      • Visio Cons:
      • Designed as an Engineering Tool - Overkill for Wireframing
      • Flat Presentation Approach - Print-Based
      • Interaction is Very Basic - Link from page-to-page
    • 18. Axure vs Dreamweaver
    • 19. Axure vs Dreamweaver
      • Dreamweaver Pros:
      • Very Powerful
      • Code Can Be Handed Off to a Developer
      • Dreamweaver Cons:
      • Dreamweaver is a Production Tool
      • Beyond Basic Logic, Requires Experienced HTML (Front-End) Coder In Order to be Rapid and Iterative
      • No Support for Annotations
    • 20. Where does prototyping fit into a UX process?
    • 21. Prototype Requirements Document CareerMatch 2.0 Where does prototyping fit into a UX process? Develop a Prototype Requirements Document!
    • 22. How To’s
    • 23. Prototyping Tips
      • Only prototype what you need
        • Know what you will be testing first
        • Create a prototype requirements document to map out the details of what needs to be simulated
      • Resist the temptation to prototype everything
        • Participants will understand that they are using a prototype and some features and functions won’t work
      • Test your test
        • Make sure you’ve covered alternate scenarios and pathways
      • Plan to iterate
        • Build in time to your test plan to revise your prototype and re-test your design with users