COMPSCI 345 S1 C and SoftEng 350 S1 C Discovery: Collection Lecture 6 Chapter 4.1 - 4.2 (Heim)

Slides:



Advertisements
Similar presentations
CHAPTER 9, survey research
Advertisements

Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Discovery Phase Framework Collection Heim, Chapters Lecture 2 Discovery.
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
User Mediation & the Reference Interview IS 530 Fall 2009 Dr. D. Bilal.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Data gathering.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 2 Succeeding as a Systems Analyst
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Research Methods for Business Students
Systems Analysis Requirements determination Requirements structuring
Systems Analysis and Design in a Changing World, Fourth Edition
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Vermelding onderdeel organisatie 1 MKT project 1 & Mens-Machine-Interactie slides chapter 13 Dix et al. Socio-organizational issues and stakeholder requirements.
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Fact-finding Techniques
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
The voyage of discovery is not in seeking new landscapes but in having new eyes. (Proust, 1982) Selections from Heim Chapters 4 Lecture 2 User Requirements.
CSC271 Database Systems Lecture # 20.
Chapter 4: Beginning the Analysis: Investigating System Requirements
What is Business Analysis Planning & Monitoring?
Business and Management Research
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
ITEC224 Database Programming
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
The Marketing Research Process and Proposals
Data gathering. Overview Four key issues of data gathering Data recording Interviews Questionnaires Observation Choosing and combining techniques.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Chapter 4 – Requirements Engineering Lecture 3 1Chapter 4 Requirements engineering.
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
Lecture 7: Requirements Engineering
Overview of Chapters 11 – 13, & 17
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Database Analysis and the DreamHome Case Study
DISCOVERY Textbook: S. Heim, The Resonant Interface: HCI Foundations for Interaction Design [Chapter 4, continued] Addison-Wesley, 2007 March 7, 2011 CS.
INTERACTION DESIGN PROCESS Textbook: S. Heim, The Resonant Interface: HCI Foundations for Interaction Design [Chapter 3] Addison-Wesley, 2007 February.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Chapter 10 Fact-finding Techniques 1 © Pearson Education Limited 1995, 2005.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
Identifying needs and establishing requirements Data gathering for requirements.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
©2011 1www.id-book.com Data Gathering Chapter 7. ©2011 Data Gathering What is data gathering? –The act of gathering data through a study The data can.
Fall 2002CS/PSY Empirical Evaluation Data collection: Subjective data Questionnaires, interviews Gathering data, cont’d Subjective Data Quantitative.
E VALUATING YOUR E - LEARNING COURSE LTU Workshop 11 March 2008.
AVI/Psych 358/IE 340: Human Factors Data Gathering October 3, 2008.
CS223: Software Engineering Lecture 8: Requirement Engineering.
Data gathering (Chapter 7 Interaction Design Text)
Fashion MARKETING TID1131. Types of research Quantitative research Information relating to numbers – quantity. Method - surveys Qualitative research To.
May 22, 2007Mohamad Eid Discovery Chapter 5. May 22, 2007Mohamad Eid Outline  Discovery Phase Framework  Collection  Interpretation  Documentation.
Session 2: Developing a Comprehensive M&E Work Plan.
MScSED Thesis Workshop: Introduction June 12 th, 2015.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
Managing Marketing Information
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Lecture3 Data Gathering 1.
Chapter 5 Determining System Requirements
Requirements Elicitation – 1
Business and Management Research
Managing Marketing Information to Gain Customer Insights
Chapter 7 Determining System Requirements
Presentation transcript:

COMPSCI 345 S1 C and SoftEng 350 S1 C Discovery: Collection Lecture 6 Chapter (Heim)

Discovery The voyage of discovery is not in seeking new landscapes but in having new eyes. (Proust, 1982) Discovery Phase Framework Collection Interpretation Documentation 2 © Heim 2008

Discovery Phase Framework During the discovery phase we must find out what we will need to know about the work that people do –We must understand what data is needed to create the design –We must create the proper tools to gather and interpret that data 3 © Heim 2008

Discovery During the collection portion you will formally identify: –The people who are involved with the work –The things they use to do the work –The processes that are involved in the work –The information required to do the work –The constraints imposed on the work –The inputs required by the work –The outputs created by the work 4 © Heim 2008

Exploring the Work Domain Consider –What solutions competitors are using –Design projects can be very diverse –Work domains are diverse –Who are the stakeholders? Identify all stakeholders –The people that are involved either directly or indirectly in the work flow –A new system that is not designed to be integrated with the work that other people in the company do may cause needless disruptions 5 © Heim 2008

Exploring the Work Domain There are four types of stakeholders: –Primary—The person who uses the design directly –Secondary—The person who either supplies input or receives output from the design –Facilitator—The person who maintains or develops the design –Indirect/Tertiary—The person who is affected by the use of the design but has no contact with it, such as the user’s superior or coworkers and the client who is paying for the project (the client may or may not also be the primary stakeholder) The primary stakeholders should have the most impact on the eventual design. All stakeholders should be considered during the design 6 © Heim 2008

Example: Who are the Stakeholders? 7 An airline booking system An international airline is considering introducing a new booking system for use by associated travel agents to sell flights directly to the public. Primary stakeholders: travel agency staff, airline booking staff Secondary stakeholders: customers, airline management Indirect/Tertiary stakeholders: competitors, civil aviation authorities, customers’ travelling companions, airline shareholders Facilitating stakeholders: design team, IT department staff © 2004 Dix et al.

Organising the Discovery Process Use 5W+H heuristic for data collection –What/How—What activities are involved and how are they accomplished? This will include the documentation of the various computer-based and non–computer-based activities and deliverables. –Where/When—We need to understand the impact of physical location on the work flow. Our design may involve changes to the physical location of the people who do the work We also need to understand the temporal aspects of the work. –Are there any prerequisite activities, and, if so, in what order must they be completed? –Who/Why—We must understand: Who is involved Why they are involved Their role in the present work flow How they may respond to any changes implemented (These people are the stakeholders in the project) 8 © Heim 2008

Organising the Discovery Process Filters –Physical—We can describe the physical aspects of the activity. Where is it done? What objects are involved? –Cultural—We can look at the activity in terms of the relationships among the people involved. Are some people in a position to orchestrate and evaluate the performance of other people? –Functional—We can also look at these activities in terms of what actually happens. Do some people create things? Do other people document procedures and communications? –Informational—We can look at these activities in terms of the information that is involved. What information is necessary to perform a task? How does the information flow from one person to another? How is the information generated/consumed? 9 © Heim 2008

Collection - Methods of Collection 10 Research © Heim 2008

Observation Direct —Ethnographic methods involve going to the work site and observing the people and the infrastructure that supports the work flow –Concerns are that your presence will affect the people you observe (positive and negative) and/or your presence can become annoying. Indirect —You can use indirect methods of observation by setting up recording devices in the work place –Can be impersonal and make people feel they are being spied on. When observing be aware of Distributed Cognition –the tendency to off-load cognitive tasks to objects in the environment or to distribute them among team members or coworkers 11 © Heim 2008

Elicitation Tools for eliciting information from the various stakeholders: –Direct Interviews Focus groups –Indirect Corporate documentation Logs and notes Questionnaires 12 © Heim 2008

Elicitation - Direct Direct methods of elicitation involve face-to-face communication –Physical aspects –Cultural aspects –Neutral linguistic approach –Individual communication styles –Tangents 13 © Heim 2008

Elicitation – Direct - Interviews Open-ended questions –can be used to explore issues and elicit rich information about complex topics Closed-ended questions –can generally be answered with a polar yes/no response or a simple description. Unstructured Interviews/Open-Ended Questions –Early in the design process interviews are generally loosely structured. Structured Interviews/Closed-Ended Questions –As the design process proceeds, interviews can become more structured and focused on specific details and areas of the design. 14 © Heim 2008

Elicitation – Direct - Interviews Interviews –Predefined Scenarios: The interviewer can use predefined scenarios to stimulate conversation and gain insight –Focus of Interview: It is important that the purpose of the interview is clearly defined –Wrap-Up: It is important to share your thoughts about the results of the interview –Advanced Organizers: Advanced organizers can be helpful in setting the frame of the design process 15 © Heim 2008

Elicitation – Direct – Focus Groups Focus Groups –Require a moderator/facilitator to keep discussion on track –Maintain spontaneity –Have clearly defined outcomes –Provide participants with a context for the project Advantages –They are relatively inexpensive and easy to set up. –They can be used early in the design process to help to identify and prioritize features. –They help you to gain insight into people’s attitudes and motivations. Disadvantages –They only represent the views of one particular group. –They are not statistically significant. –They do not provide information about usability. 16 © Heim 2008

Elicitation – Indirect Corporate Documentation—Information can be collected indirectly through corporate documents that reference policies and procedures. Logs and Notes—Indirect methods can also include user participation; –Ask people to keep a log of specific activities –Collect the notes people make to remind them of procedures and policies sticky notes tacked onto a computer reminders stuck on a corkboard 17 © Heim 2008

Elicitation – Indirect - Questionnaires Questionnaires are familiar Questionnaires can contain open and closed questions Questionnaires can include the following: –Mutually exclusive choices (radio buttons) –Non–mutually exclusive choices (checkboxes) –Ranges (overlapping, open-ended) –Scales (Likert scales, semantic differential scales) –Short-answer fill-ins –Comments 18 © Heim 2008

Elicitation – Indirect - Questionnaires The following are guidelines for defining scales: –Identify the scale and the significance of the units –Use the most intuitive order –You can use positive or negative scales or a combination of the two –Use odd numbers when you want to allow neutral responses. –Use even numbers when you want to force a choice of positive or negative. –Provide a not applicable (NA) response when appropriate. –Do not use too many degrees within the scale; seven is considered a general limit. 19 Likert scale. © Heim 2008

Elicitation – Indirect - Questionnaires Advantages of questionnaires: –They do not involve face-to-face contact and can be administered remotely. –They can be used to supply information for primary stakeholder profiles. –They can be used to ascertain whether proposed solutions will meet with acceptance as well as to elicit new ideas. –They can also be used to double-check the feedback obtained from one-on-one interviews. –They can reach a large audience with relatively little expense. Disadvantages of questionnaires: –Vague questions will return ambiguous responses that will serve no useful purpose or the design. –People do not like to fill out long questionnaires. –Closed-ended questions can restrict responses. –Open-ended questions can be hard to quantify. 20 © Heim 2008

Elicitation – Indirect - Questionnaires Guidelines for questionnaires: –Be consistent. –Phrase instructions clearly. –Speak the user’s language. –Avoid jargon or technical terms. –Order the questions beginning with the easy or less controversial ones. –Use logical grouping. –Avoid compound questions. –Use appropriate form elements, for example, radio buttons, checkboxes, and so on. –Use an appropriate scales for questions with discrete responses. –Avoid overlapping ranges. –Include a “None of the above” when appropriate. –Be sensitive to the balance of positive and negative questions 21 © Heim 2008

Research Read up on recent literature in that area to gain background knowledge –I.e. If we were designing a drawing tool for children under 5 years from literature we could find out about: computer skills of children under 5 years the types of drawings these children would typically want to draw You will need to do some research for Assign 1 Use digital libraries/search engines –You can access many online databases e.g. ACM, IEEE etc. through the library interface: mp/comp.htm?FROM_REF=rt mp/comp.htm?FROM_REF=rt –Google Scholar 22

Summary We have looked at the first part of discovery –methods of collection Next lecture: Interpretation & Documentation (Heim ch ) 23

Questions Describe some aspects of distributed cognition in your own life. Design a short questionnaire (i.e approx 10 questions) to find out about what word processors people use and what they like/dislike about them. 24