Your SlideShare is downloading. ×
  • Like
8220 sad inquiry
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

8220 sad inquiry



Published in Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Usability and User Acceptance Testing ISQA 8220: Brad Bass
  • 2. Why is it important? ● Understanding the difference between usability and user acceptance ● Testing is one of the most important disciplines ● Knowledge of when testing should be performed and how to develop a plan
  • 3. Usability Testing ● Scenario based testing performed by real users. These users test functional use cases provided by the system.
  • 4. Usability Testing What does it accomplish? ● Can users successfully complete tasks ● Identify errors and complaints from real users ● How do user’s actions differ from expected flow ● User satisfaction ● Do user’s need more/less information to successfully complete tasks
  • 5. Usability test plans ● ● ● ● ● Goals are very flexible Define scope - what use cases/features to test Create test scenarios Session length Find desired users to adhere to testing goals ○ ○ managers, customers, suppliers, etc. "It takes only five users to uncover 80 percent of high-level usability problems" Jakob Nielsen
  • 6. User Acceptance Testing ● Testing performed by end business experts to ensure the system meets the needs of the business ● Often interchangeable with beta testing ● Requires signoff by business experts before system goes live
  • 7. User Acceptance Testing What does it accomplish? ● Decreases cost of development. Defining good test plans early helps solidify requirements ● Proves the system work in the real business environment ● Significantly reduces risk of project failure after rollout
  • 8. When to test Begin documenting user acceptance signoff requirements Perform user acceptance testing
  • 9. What’s the difference? Usability: ● Test effectiveness of the system through a user’s experience ● Tests are performed as early as possible and as often as necessary ● Verify system can perform certain tasks ● Results can lead to design changes ● Test plans created in each iteration ● Typically goal or task driven - should not be a system implemented beta test User Acceptance: ● Business user and stakeholder sign off and approval ● Only performed toward the end of a project ● Verify business requirements have been met ● Results are typically only minor code enhancements or bug fixes ● Test plans created early (Right after requirements are fully defined) ● Not intended to find system errors or verify task level activities
  • 10. Does it work? Usability: ● Make tests objective by quantifying results ○ How long does it take to perform a task? ○ On average how many clicks did a user take to find a function. ● Use adequate number and diverse set of users ● ● User Acceptance: ● User acceptance test plan should be tightly coupled with requirement documentation ● Signoff actors should be highly qualified and have the following skills: ○ Background ○ Skill ○ Independence ○ Attitude Compare metrics to other industry systems Compare metrics to user expectations
  • 11. References University of Texas, 26 Jul 2006. Web. 11 Nov 2013. <>. Bordo, Vince. Web. 11 Nov 2013. <>. Web. 11 Nov 2013. <>. Web. 12 Nov 2013. <>. Nielsen, Jakob., 26 Jun 2006. Web. 12 Nov 2013. <>. Web. 11 Nov 2013. <>. Goldsborough, Justin. N.p., 7 Jun 2012. Web. 12 Nov 2013. <>.