|
 |
|
|---|---|
 |
|
|
|
Tutorial #14: User Requirements: Collection, Data Interpretation, and PresentationTuesday, July 9th, 8:30 AM - 5:00 PMKeywords:Data collection, Product lifecycle and usability, User requirements gatheringAudience:BeginnerAbstract:This tutorial will provide participants with the skills to conduct a Wants and Needs Analysis, Group Task Analysis and Card Sort. Participants will learn how to interpret the data from these techniques and present the results to development teams. The tutorial will consist of hands-on exercises, group discussion, and lecture.Length of Tutorial:Full DaySystem, Product, or Project Focus:No specific system, product, or project orientationLearning objectives:
How tutorial will be conducted:The tutorial will consist of hands-on exercises, group discussion, case studies, and lectures. The lecture components will provide background, purpose, and origins of each of the methodologies. Photos, screen shots, and examples will be provided to demonstrate each of the techniques and their value. In addition, there will be an emphasis on hands-on exercises. Hands-on experience will be offered to participants via a mock Wants and Needs Analysis, Group Task Analysis, and Group Card Sort. They will also have the opportunity to analyze the data and interpret the results to form a meaningful picture.DETAILED DESCRIPTION OF MATERIAL COVERED BY TUTORIAL AND A SCHEDULE OF EVENTS WITH TIME ALLOCATIONIntroduction to Tutorial and Instructors (15 minutes)During this time the instructors will be introduced and their backgrounds will be discussed. In addition, time will be allotted for each attendee to briefly introduce themselves. This will allow the instructors to get a sense of the job roles, the industries, and usability experience of the attendees.Wants and Needs Discussion ( 20 minutes)The first technique we will cover is the Wants and Needs Analysis. This technique was created by the Turtle Bay Institute. The Wants and Needs Analysis is a methodology that facilitates the collection of users' needs, wants, and desires, for a particular product. Tutorial attendees will be given an introduction to the origins, purpose and method of this technique. In addition, they will learn about the participants, materials, and facilities needed for this activity.Wants and Needs Hands-on (25 minutes)Participants in the tutorial will take part in a mock Wants and Needs Analysis to learn how to facilitate the session, collect the data, and analyze the results. The mock session will be facilitated by the tutorial leaders and the attendees will act as the participants. An ice breaker activity is used to open the conversation and get creativity flowing. Next participants will be introduced to the rules of the session and asked to brainstorm their wants and needs for an ideal system (e.g., a system that allows them to find and buy books on the web). Participants will be questioned after they state a want or need to be sure the true want and need is captured and understood.Wants and Needs Data Analysis and Presentation (25 minutes)Attendees will next switch from the role of the participant to usability engineer and share in the data analysis. In this section of the tutorial, the attendees will learn how to analyze the data from a Wants and Needs Analysis. In addition, they will learn how to interpret these results and relay them to the development team in a meaningful way. Tutorial attendees will take home guidelines for conducting the session, instructions for analyzing the data, and sample materials.Wants and Needs Analysis Design Discussion (15 minutes)The results of a Wants and Needs Analysis should be fed into a product's functional specification. This document in turn will be used to drive the product's design. We will discuss creating functional specifications based on the Wants and Needs Analysis results. Attendees will receive a sample functional specification for future reference.Group Task Analysis Discussion (25 minutes)Tutorial participants will be taught a second user requirements technique: the Group Task Analysis. This method is based, in part, on a modification of The Bridge (Bertus, Dayton, Kramer, and Tournat) as it was presented at HFES 2000. In the Group Task Analysis, a group of four to six end users is brought together to develop task flows for functionality supported by the product in question. These flows detail the steps users take to accomplish the task as well as the sequence of steps. This information is very important because it enables development teams to comprehend how users accomplish their primary tasks. This in turn guides the development of the interaction architecture. Tutorial attendees will be given an introduction to origins, purpose and method of this technique. In addition, they will learn about the participants, materials, facilities needed for this activity.Group Task Analysis Hands-on (45 minutes)Participants in the workshop will take part in a mock Group Task Analysis and practice group facilitation. Participants will be asked to outline the steps involved in a task such as, finding and buying a book. Next, they will be asked to identify a trigger and end point and arrange some steps provided (e.g., locate a book, purchase a book, etc.). They will be encouraged to remove steps that do not belong and add any that are missing.Group Task Analysis Data Analysis and Presentation (20 minutes)Participants will next switch from the role of the participant to usability engineer and share in the data analysis. In this section of the tutorial, the attendees will learn how to analyze the data from a Group Task Analysis. In addition, they will learn how to interpret these results and relay them to the development team in a meaningful way. Instructions for conducting a session, as well as sample materials, will be provided for attendees to take home.Group Task Analysis Design Activity (40 minutes)The results of a Group Task Analysis can be used to influence flow and individual screen designs of the product. Working in pairs, attendees will translate the task flow into a set of screen designs that represent a logical task sequence.Group Card Sort Discussion (15 minutes)The third technique the attendees will be taught is the Group Card Sort. In a Group Card Sort users are asked to group or order concepts on cards These orderings and groupings correspond to the users' model of the domain. Therefore, the Card Sort methodology enables a usability engineer or designer to determine the high-level information architecture for the product's proposed functions. Tutorial attendees will be given an introduction to purpose and method of this technique. In addition, they will learn about the participants, materials, facilities needed for this activity.Group Card Sort Hands-on (20 minutes)Participants in the workshop will take part in a mock Group Card Sort. Each participant will act as a user and individually sort items an e-commerce site. Participants can remove cards that do not apply or add cards that they feel are missing. After successfully sorting all of the cards into piles, participants will be asked to give each pile a meaningful name. Group Card Sort Analysis and Presentation (30 minutes) In this section of the tutorial, we will discuss data analysis. Participants will be introduced to cluster analysis software and we will discuss the output of the cluster analysis in detail. Instructions for conducting a session, as well as sample materials, will be provided for attendees to take home.Group Card Sort Design Activity (35 minutes)The results of a Card Sort can be used to design the information architecture of a product. Attendees will work in pairs to translate the results of the card sort they just completed into the information architecture for their product.OriginThis tutorial was given at the Human Factors and Ergonomics Society 45th Annual Meeting, 2001 and was received with much enthusiasm. In addition, it will be given as a BayCHI tutorial in January 2002. The tutorial has been modified for UPA 2002 to appeal to the UPA audience. The examples and case studies provided throughout the tutorial will focus on software requirements gathering, but can also be applied to hardware. In addition, we will discuss the activities from the perspective of a usability engineer who is a part of a diverse product team. A design component has also been added to enhance usability engineers' design skills and appeal to other audience members such as designers and product managers.DESCRIPTION OF MATERIALS (HANDOUTS)Tutorial participants will be given copies of our slides to follow along with the presentation. In addition, they will be given samples of the materials they will need in order to complete a Wants and Needs Analysis, Group Task Analysis and Group Card Sort on their own. These include worksheets, sample materials, sample results, and sample designs for all three techniques.Maximum number of participants30 participants maximumBACKGROUND OF PRESENTERSCatherine CourageUsability Engineer Oracle Corporation Voice: 650-506-1457 Fax: 650-506-7430 catherine.courage@oracle.com Catherine is a usability engineer in the Usability and Interface Design Group at Oracle Corporation. She works within the Enterprise Resource Planning (ERP) division of the group and provides usability support to Human Resources and Financial applications. She conducts usability activities for web-based applications for the desktop, personal digital assistants, and web-enabled phones. Before joining Oracle, Catherine received a Masters of Applied Science degree specializing in Human Factors from the University of Toronto's Department of Mechanical and Industrial Engineering. Catherine is an active member of the Usability Professionals Association (UPA), Human Factor and Ergonomics Association (HFES), and Computer Human Interaction (CHI) special interest group of the Association for Computing Machinery. Over the past 3 years she presented a variety of papers and tutorials to the Usability and Human Computer Interaction community. Kathy Baxter Usability Engineer Oracle Corporation Voice: 650-633-8640 Fax: 650-506-7430 kathy.baxter@oracle.com Kathy Baxter has been a usability engineer in Oracle Corporation's Usability and Interface Design Group in Redwood Shores, CA since 1998. She supports desktop and mobile manufacturing applications within the Enterprise Resource Planning (ERP) division. In addition, she supports products within Healthcare and Public Sector. She received her Masters of Science in Engineering Psychology with an emphasis on Human Computer Interaction from the Georgia Institute of Technology in 1998. Kathy is an active member of the Usability Professionals Association (UPA), Human Factors and Ergonomics Society (HFES), Computer Human Interaction (CHI) special interest group of the Association for Computing Machinery, and BayCHI. She has presented posters, papers, and tutorials to the Human Factors and Usability Community for the past five years. |
|
|
|---|---|
|
|
|
|
|
