Requirements, cont. …along with Ethics. Agenda Questions? Data gathering techniques Requirements expressing Ethics.

Slides:



Advertisements
Similar presentations
Use Case Diagrams Damian Gordon.
Advertisements

Collaborating By: Mandi Schumacher.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
How to Develop a Science Fair Project
Banking Your Money: Keeping it Safe and Secure. Who’s Who in Financial Services When it comes to taking care of your basic financial needs, the first.
CS305: HCI in SW Development Evaluation (Return to…)
Requirements Gathering & Task Analysis – Part 2 of 5 Why, What and How – Methods This material has been developed by Georgia Tech HCI faculty, and continues.
IAT 334 Interface Design Task Analysis
Substitute FAQs SubFinder Overview. FAQs Do I have to have touch-tone service to use SubFinder? No, but you do need a telephone that can be switched from.
User-Interface Design Process Lecture # 6 1Gabriel Spitz.
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)
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Requirements Gathering and Expressing. Agenda Questions? Project update Requirements continued Project group formation.
Requirements Gathering & Expressing
Requirements and Task Analysis
Requirements: Gathering. Why  To understand what we are going to be doing  We build systems for others, not for ourselves  Requirements definition:
Requirements - Expressing Requirements analysis & its outcomes.
User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo FJK 2005.
Task Analysis Analyzing and representing the activities of your users.
An evaluation framework
Design process.
Requirements and Task Analysis. Please attend!! Duke Hutchings: “Window interfaces for multiple monitor systems”: next Monday 2/6, 9:30-11, room 154 student.
Requirements Gathering
Requirements Gathering Methods for Requirements Gathering and Requirements Gathering.
Check It Out 1. 2 Introductions Instructor and student introductions Module overview.
1 © 2009 University of Wisconsin-Extension, Cooperative Extension, Program Development and Evaluation Getting started with evaluation.
Study Skills and Strategies. About Me Name:Mauricio Najarro College:Williams College SAT Score:2400 Has a rich and diverse teaching background, starting.
Evaluation IMD07101: Introduction to Human Computer Interaction Brian Davison 2010/11.
Spring break survey how much will your plans suck? how long are your plans? how many people are involved? how much did you overpay? what’s your name? how.
Requirements, cont. …and a word on Ethics. Project Part 1: Requirements Gather data using one or more techniques Learn about environment, users, tasks,
The Writing Process Introduction Prewriting Writing Revising
User Modeling Lecture # 5 Gabriel Spitz 1. User-Interface design - Steps/Goals.
Fall 2002CS/PSY Task Analysis Analyzing and describing how people do their jobs/work  -> Go to their environment Examine users’ tasks to better.
Evaluation Framework Prevention vs. Intervention CHONG POH WAN 21 JUNE 2011.
Requirements Gathering. Why are requirements important? To understand what we are going to be doing We build systems for others, not for ourselves Requirements.
1www.id-book.com Identifying needs and establishing requirements Chapter 10.
Chapter 11: An Evaluation Framework Group 4: Tony Masi, Sam Esswein, Brian Rood, & Chris Troisi.
By Edward Lim 8.7.  What?  Today we started the Cornerstone Piece and we were given a few tasks to complete. The tasks were to watch the Kurt Fearnly.
Science Fair Information. The purpose of the Science Fair is to offer students the opportunity to think deeply about science as it applies to everyday.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
R ESTAURANT M ANAGEMENT (HM 432) CHAPTER 5 Planning and Conducting Effective Meetings.
Human Computer Interaction
Usability Evaluation June 8, Why do we need to do usability evaluation?
Requirements Gathering …along with Ethics. Agenda Questions? Project part 0 Requirements gathering Ethics.
Objectives By the end of the class, you will be able to… Describe typical users by using “personas” Write detailed task descriptions to inform design.
Requirements I Gathering Data with Users. Objectives By the end of this class you should be able to… Explain the importance of involving users in requirements.
Task Analysis …and we’ll really get to Ethics this time.
1 Chapter 5 Modeling System Requirements Finding the Use Cases Page
Task Analysis Overview, utility Types of task analysis Sources and use.
Design Process … and some design inspiration. Course ReCap To make you notice interfaces, good and bad – You’ll never look at doors the same way again.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Requirements Gathering CS 561. Where do Requirements Come From? Handed to you (?) Dialogue with – Customer – User Are these always the same? Are these.
EVALUATION PROfessional network of Master’s degrees in Informatics as a Second Competence – PROMIS ( TEMPUS FR-TEMPUS-JPCR)
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
Working with People & Project Overview “Doing right by your participants”
AVI/Psych 358/IE 340: Human Factors Data Gathering October 3, 2008.
Requirements Gathering & Task Analysis – Part 2 of 5 Why, What and How – Methods This material has been developed by Georgia Tech HCI faculty, and continues.
User Modeling Lecture # 7 Gabriel Spitz 1. User Interface Design Process Gabriel Spitz 2 Needs Assessment Competitive Analysis Persona Develop Task Analysis/
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Meetings Managers are people who do things right, while leaders are people who do the right thing. Warren Bennis, Ph.D. “On Becoming a Leader”
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Data gathering (Chapter 7 Interaction Design Text)
Lecture 4/2/16. Learning Objective Establishing requirements Define requirements Requirements discovery vs requirements gathering Classifying Requirements.
GROUP ROLES. GROUP LEADER Should be kind, not put anybody or their ideas down Works well with others Guides the discussion; Asks questions Helps the group.
Requirements in the product life cycle Chapter 7.
COMMUNICATION ENGLISH III October 11/12 th Today Interview discussion.
GATHERING DATA Supplementary Note. What are requirements? A requirement is a statement about an intended product that specifies what it should do or how.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
ITM 734 Requirements Gathering & Task Analysis – Part 2 of 5 Cindy Corritore This material has been adapted from Georgia Tech HCI faculty,
FORGE AHEAD Program Transformation of Indigenous Primary Healthcare Delivery : Community-driven Innovations and Strategic Scale-up Toolkits Module.
Presentation transcript:

Requirements, cont. …along with Ethics

Agenda Questions? Data gathering techniques Requirements expressing Ethics

Reminder: requirements Overall goals, success criteria User characteristics Task analysis Environment – physical, social, technical Constraints Usability goals, criteria Functional requirements

(Not All) Requirements Gathering Methods 1. Observation 2. Thinking Out Loud & Cooperative Evaluation 3. Interviews 4. Questionnaires 5. Focus groups 6. Study Documentation 7. Look at competitive products

Formative & Summative Evaluation Formative evaluation – Conducting this process to help guide the formation (ie, design) of a UI Summative Evaluation – Conducting this process to help summarize (sum up) the effectiveness of an existing or developmental UI Many techniques can be used for both formative and summative evaluation – Our focus right now is on formative evaluation – Will revisit some of the methods again later

Observation Watch user(s) doing activity of interest to you Possibly video or audio record (with permission) Swap cell phones and observe each other – Look up most recently called and return call – Add your name to the phone book

Impressions? What was surprising? What problems did you observe? How would this be different in real world? How did you feel about being observed?

Think out loud Problem: how do you know WHY someone does what they do? Think out loud - encourage user to verbalize what they are thinking – Not everyone is good at this – Hard to keep it up for long time while also doing something; need breaks

Cooperative (Participative) Evaluation Sit with user doing activity of interest to you Talk with user as the do their activity – Ask questions Why are you doing that? How did you know the result was what you wanted? Are there other ways to achieve the same goal? How did you decide to do things this way? Relaxed version of thinking out loud – Observer and participant can ask each other questions

Observing Tips Carefully observe everything about users and their environment Think of describing it to someone who has never seen this activity before What users say is important, so are non- verbal details

Example: airport check-in kiosk What could you observe? How could you use think aloud?

Interview Users Semi-structured: predetermine sets of questions Example question types How do you perform task x? Why do you perform task x? Under what conditions do you perform task x? What do you do before you perform…? What information do you need to…? Whom do you need to communicate with to …? What do you use to…? What happens after you…? What is the result or consequence of…? What is the result or consequence of NOT…? See ID 7.4 for more tips and discussion

Domain Expert Interviews Expert describes how it should be done (not necessarily how it is done)

Focus Groups Interview groups of users – 3 to 10 at a time – Use several different groups with different roles or perspectives Relatively low cost, quick way to learn a lot Use structured set of questions – More specific at beginning, more open as progresses – Allow digressions before coming back on track More challenging to lead than single interview – Some people quiet, some dominating – Easier to get off track

Questionnaires (or Surveys) Easier to give to broader audience Shorter, more focused than interview General criteria – Make questions clear and specific – Ask some closed questions with range of answers Sometimes also have a no opinion option, or other answer option – Do test run with one or two people

Numerical scales: On a scale of 1 to 7, how comfortable are you… Could also use just words – Strongly agree, agree, neutral, disagree, strongly disagree Questionnaires - Example See ID 7.5 for more tips

Other Typical Questions Rank the importance of each of these tasks (give a list of tasks) List the four most important tasks that you perform (this is an open question) List the pieces of information you need to have before making a decision about X, in order of importance Are there any other points you would like to make? (open-ended opinion question; good way to end)

Example: airport check-in Who to interview? What questions? Who to give questionnaire to? What questions? What about focus group? What are differences between methods?

Study Documentation Similar in some ways to the expert interview Often describe how things should be done rather than how they are done – Try to understand why not done “by the book”

Look at Competitive Products Looking for both good and bad ideas – Functionality – UI style Do user task performance metrics to establish bounds on your system

Which Methods to Use? Depends on – Resources – Current knowledge of tasks and users – Context Difficult to use talking out loud in public – Essential to use some methods – Not likely you will use all methods See pg. 343 in ID

Which Methods to Use? Self-service filling and payment system for a gas station On-board ship data analysis system for geologists searching for oil Fashion website for buying clothes at large department store

Process Gather data – Interviews, observation, surveys/questionnaires, documentation, immersion Organize data – Notes, cards, brainstorming, computer tools Represent data – Lists, outlines, matrices – Narratives – Hierarchies, Networks, Flow charts

Describing requirements activities Narratives Personas Scenarios Task Analysis & other task descriptions – …next lecture

Scenario Describe tasks and context in sentences Natural way of describing general idea Not effective for – details – branching tasks – parallel tasks GREAT as introduction to diagrams or outlines

Scenario: Example 1 Its Friday afternoon and John just got paid. He wants to deposit his check immediately so he can pay his rent. He stops at one branch of his bank on the way home from work. He waits in his car while another person finishes using the ATM in front of the bank since it is drizzling outside. He walks up to the ATM to deposit his check. Only, as he is about to put the check into the envelope at the ATM, he realizes that he has not signed the back of it, and he has no pen and can not find one on or near the ATM machine. He cancels the transaction on the ATM, and enters the bank, which luckily is still open for 5 more minutes. He goes to the counter, finds a pen, and signs his check. He also fills out a deposit slip. He then waits to see a teller in person to deposit his check, and get money for the weekend.

Scenario: Example 2 Annie walks up to the ATM to deposit her weekly pay check. She puts her ATM card into the slot in the machine. She then enters her PIN number quickly, trying to block the person waiting behind her from viewing the keypad, and knows that she does not have to press “Enter” at this particular machine. She then chooses “Deposit” and “Check.” She enters the amount of the check using the keypad, then takes an envelope from the ATM machine, puts her check inside, seals the envelope and writes the amount of the check on the outside. She feeds the envelope into the slot into the ATM machine. She then selects “No other transactions” to finish, and waits to receive her receipt and ATM card.

Example Register for classes What kinds of activities could we write a scenario about? Let’s write one together

Exercise: Movie Ticket Kiosk What data gathering techniques would you use? Who would you interact with? Who are the stakeholders? What are typical user characteristics? What is physical/social/technical environment? What is a typical scenario of use? What is an atypical or problem scenario?

Next Assignments Create a scenario of CURRENT activity Due next Monday Think about your project topic Confer with teammates DO NOT write a story about your new interface, stick with what currently happens, even if no technology is involved.

Working with People Issues of rights, respect, ethics YOU will be observing and talking to people to: – Gather requirements – Get initial design feedback – Perform evaluations of your design Important to be professional with any interaction with potential users

Why an issue? Usability testing can be arduous; privacy is important Each person should know and understand what they are participating in: – what to expect, time commitments – what the potential risks are – how their information will be used Must be able to stop without danger or penalty All participants to be treated with respect

Consent Why important? – People can be sensitive about this process and issues – Errors will likely be made, participant may feel inadequate – May be mentally or physically strenuous What are the potential risks (there are always risks)? – Examples? “Vulnerable” populations need special care & consideration – Children; disabled; pregnant; students (why?)

IRB, Participants, & Ethics Institutional Review Board (IRB) Federal law governs procedures Reviews all research involving human (or animal) participants Safeguarding the participants, and thereby the researcher and university Not a science review (i.e., not to asess your research ideas); only safety & ethics

UNCC On-line tutorial Guidelines Consent procedures and template forms Protocol application forms Ethics certification – Standardized training to ensure everyone understands the issues