Responding to Usability Issues Mary Chant, Certified Usability Analyst

Slides:



Advertisements
Similar presentations
User problems, scenarios and storyboards
Advertisements

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Chapter 1 Introducing User Interface Design. UIDE Chapter 1 Why the User Interface Matters Why the User Interface Matters Computers Are Ubiquitous Computers.
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
GAI Proprietary Information
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Semester in review. The Final May 7, 6:30pm – 9:45 pm Closed book, ONE PAGE OF NOTES Cumulative Similar format to midterm (probably about 25% longer)
UI Standards & Tools Khushroo Shaikh.
Usability presented by the OSU Libraries’ u-team.
The Soft Topics in Software Engineering Mark Ardis Stephen Chenoweth Frank Young.
Lesson 17 Requirements Discovery
Part 4: Evaluation Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what, where, and when Chapter.
User Engineering | Sept 2004 | Dave Roberts © 2004 IBM Corporation Coping With Complexity Creating a solution with User Engineering.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Part 2: Requirements Days 7, 9, 11, 13 Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Instructional Design Amal Alelait ET500. Instructional Design  instructional design is the systematic process by which instructional materials are designed,
Usability Driven GUI Design Portal as a Gateway to Intranet Resources Matthew Winkel Usability Analyst.
User Interface Design Process Gabriel Spitz. User-Interface design Steps/Goals Understand who are the users and what do they do Articulate how will users.
User Centered Design The Process Information Business – UCD Robert Press (718)
© 2014 Fair Isaac Corporation. Confidential. This presentation is provided for the recipient only and cannot be reproduced or shared without Fair Isaac.
User Centered Design April 1-3, 2009 Joshua Ganderson Laura Baalman Jay Trimble.
ICELW, New York, June PROJECT USABILITY : SCHMOOSABILITY …what does it matter?
UX Research Team Kelley Howell, Manager Nicole Glover, UX Analyst.
Requirements Analysis
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Setting up a Hyperion Center of Excellence Case Study at Plantronics By
ITEC224 Database Programming
CIS 321—IS Analysis & Design Chapter 4: Analysis— Investigating System Requirements.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Product design portfolio.  September 2008 – present.
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
Innovation insight Peter H. Jones, Ph.D. Dayton, Toronto redesignresearch.com designdialogues.net A Bag of Tricks: What is the Right Mix of Methods?
Sakai Tools Designing a User-Centered Sakai Tool Sakai Tools Team Rob Lowden, Daphne Ogle.
Conducting Usability Tests 4 Step Process. Step 1 – Plan and Prep Step 2 – Find Participants Step 3 – Conduct the Session Step 4 – Analyze Data and Make.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Information Gathering Prototypes Structured Walkthrough.
1 6 C H A P T E R REQUIREMENTS DISCOVERY. 2 Chapter Six Requirements Discovery Define system requirements and differentiate between functional and nonfunctional.
2 nd Knowledge Area : Project Scope Management. Importance of Good Project Scope Management 1995 CHAOS study cited user involvement, a clear project mission,
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
1  [company] Inc. [year] Girl Scouts of the USA Secure Site Project Kickoff [date]
RHS Tech Ed The Engineering Design Process. What Is Design?
Usability Lab 2002 Cascade Kick-Off Meeting User Requirements - Web Site Design Multimedia Interface to Material Databases Flavio Fontana (Ulab)
In the news. Taxonomy Organizing Information Observation The Organization Project Scope Start the project Stakeholder Interviews Gather goals Focus groups.
User-Centered Design (UCD) Overview
Requirements in the product life cycle Chapter 7.
William H. Bowers – Requirements Torres 9.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
1. TESTING with users... client dinners focus groups usability centers surveys web analytics beta testing pre-release TESTING with users...
Designing as a Team Designing as a Team A Collaborative Approach to Web Development Jeffrey Veen
How Software Projects Start SW projects start with a need. We need to keep better data on the students in the CSCE Dept. I heard that one of our competitors.
Requirements Management with Use Cases Module 0: About this course Requirements Management with Use Cases Module 0: About this course.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
1 Pengembangan Sistem Informasi Williams, B.K, Stacy C. Sawyer (2007). Using Information Technology: A Practical Introduction to Computers & Communications.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Requirements Determination
CIS 376 Bruce R. Maxim UM-Dearborn
Requirements Elicitation and Elaboration
SKILL ASSESSMENT OF SOFTWARE TESTERS Case Study
Informatics 121 Software Design I
Market problems & opport‘ies
Presentation transcript:

Responding to Usability Issues Mary Chant, Certified Usability Analyst PORTFOLIO Responding to Usability Issues Mary Chant, Certified Usability Analyst

Process Issue How to add user centered design (UCD) to the development process? Response Evangelize/Advocate Visualize Create a Road Map Map the addition of UCD activities into the Product Development Life Cycle.

Presentation Issue How to inform stakeholders about research and best practices? Response Create a presentation Build an intranet site Create an overview presentation. Provide examples and discussion points. Build and intranet site about usability to disseminate information.

Research Issue How to define users/user roles? Response Gather data/ask questions Surveys Interviews Observations Knowledge Base Personae Issue How to justify a user interface design project? Write a Business Case Issue How to document user interface requirements? Validate requirements with product management, business analysts, and end users Write a Definition/UI Requirements Doc Business Case defines the problem to be addressed. Definition document defines the design and user requirements at a high level, encourages consensus building and buy-in prior to prototyping.

Workflow Issue How to identify and communicate the workflow for a complex and/or high risk task? Solution Create an activity diagram Validate scenario(s) Write a use case Activity diagram can prevent “churning” by providing visual representation of the expected workflow.

Design Issue How to design a consistent interface? Response Adhere to UI Standards Use and reuse UI patterns when possible Issue How to design an efficient interface for a critical recurring activity? Review current design (if applicable) Research Best Practices Create a prototype Test Refine prototype Test again Submit for approval Deliver prototype and functional spec Using design patterns ensures consistency for end-users and promotes reuse for developers. Iterative design and testing supports an Agile process.

Testing Issue How to explore the usability of existing interfaces and new designs? Response Identify high-risk features Create test plan Create test script Perform testing Report results Make recommendations Creating templates for test plans, surveys and reporting decreases turnaround time for testing. Appropriate tests can be formal or informal, in-person or remote.

Review Issue How to offer helpful, high-level advice on short notice? Response Outline Issues/Questions/Suggestions Submit UI Review Sometimes a project timeline only allows for minimal changes to the interface. An issue/suggestion review document provides a quick vehicle for communicating usability concerns and recommendations.