1 © 2004-5 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license.

Slides:



Advertisements
Similar presentations
Techniques For Leading Group Discussions
Advertisements

Qualitative and Observational Research
Objective Knowledge Elicitation Interview Case Study Answers Questions Domain Expert Knowledge Engineer Results Knowledge Expert System.
© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Copyright © 2014 by The University of Kansas Qualitative Methods to Assess Community Issues.
Research methods – Deductive / quantitative
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Topics: Interviewing Question Type Interviewing techniques
Knowledge Acquisition. Knowledge Aquisition Definition – The process of acquiring, organising, & studying knowledge. Identified by many researchers and.
Requirement Engineering – A Roadmap
© 2010 Cengage Learning. Atomic Dog is a trademark used herein under license. All rights reserved. Chapter 4 Analyzing Jobs.
Data collection methods Questionnaires Interviews Focus groups Observation –Incl. automatic data collection User journals –Arbitron –Random alarm mechanisms.
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 7 Determining System Requirements 7.1.
Principles of Marketing
Chapter 5 Determining System Requirements
Requirements Modeling
Chapter 3 Needs Assessment
Ways of Collecting Information Interviews Questionnaires Ethnography Joint Application Design Books and leaflets in the organization Prototypes.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Preparing for Data Collection Need to recognize that data collection is a high level activity that cannot be just passed off to graduate assistant Need.
5-1 © Prentice Hall, 2007 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
S/W Project Management
Determining System Requirements Classes 9,10. SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical.
Copyright © 2014 by The University of Kansas Techniques For Leading Group Discussions.
Research methodology Data Collection tools and Techniques.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
3.2.1 The role of Market Research and Methods Used:
Requirements Engineering
BIS 360 – Lecture Five Ch. 7: Determining System Requirements.
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
Qualitative Methods to Assess Community Issues. What are qualitative methods of assessment? Qualitative methods of assessment are those whose results.
Human Computer Interaction
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
CS2003 Usability Engineering Usability Evaluation Dr Steve Love.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Facilitating Multi Stakeholder Processes and Social Learning Herman Brouwer / Karèn Verhoosel Centre for Development Innovation Semi structured.
Dr. Engr. Sami ur Rahman Assistant Professor Department of Computer Science University of Malakand Research Methods in Computer Science Lecture: Data Generation.
Research Methods in Psychology (Pp 32-44)
University of Sunderland Professionalism and Personal Skills Unit 9 Professionalism and Personal Skills Lecture Data Collection.
Ways of Collecting Information Interviews Questionnaires Ethnography Books and leaflets in the organization Joint Application Design Prototyping.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
1 Learning Objectives: 1.Understand data collection principles and practices. 2.Describe the differences between collecting qualitative and quantitative.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Information Gathering: Interactive Methods
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Strategic Research. 6-2 Chapter Outline I.Chapter Key Points II.Research: The Quest for Intelligence and Insight III.The Uses of Research IV.Research.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
Identifying needs and establishing requirements Data gathering for requirements.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 4 Systems Requirements Determination.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Introduction. Steve Semler The Session in a Nutshell Figure out the business purpose and learning intent. Determine what actions or decisions the learners.
SOCIAL SCIENCE RESEARCH METHODS. The Scientific Method  Need a set of procedures that show not only how findings have been arrived at but are also clear.
Requirements Elicitation Requirements Engineering (CI 2323) Daniel Siahaan.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
NEEDS ASSESSMET Primary Data for Needs Assessment.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Fact Finding (Capturing Requirements) Systems Development.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
Requirements Engineering
Exploratory Research: Qualitative Research
Chapter 7 Determining System Requirements
User Studies Basic principles, methods, and examples
Presentation transcript:

1 © Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license.

2 Lecture 5: Eliciting Requirements Ü Basics of elicitation  Why info collection is hard  Dealing with Bias Ü A large collection of elicitation techniques:  Background Reading  Hard data collection  Interviews  Questionnaires  Group Techniques  Participant Observation  Ethnomethodology  Knowledge Elicitation Techniques

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 3 Difficulties of Elicitation Ü Thin spread of domain knowledge  The knowledge might be distributed across many sources  It is rarely available in an explicit form (I.e. not written down)  There will be conflicts between knowledge from different sources  Remember the principle of complementarity! Ü Tacit knowledge (The “say-do” problem)  People find it hard to describe knowledge they regularly use Ü Limited Observability  The problem owners often too busy coping with the current system  Presence of an observer may change the problem  E.g. Probe Effect Ü Bias  People may not be free to tell you what you need to know  People may not want to tell you what you need to know  Outcome will affect them, so they may try to influence you

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 4 Example Ü Loan approval department in a large bank  The analyst is trying to elicit the rules and procedures for approving a loan Ü Why this might be difficult:  Implicit knowledge:  There is no document in which the rules for approving loans are written down  Conflicting information:  Different bank staff have different ideas about what the rules are  Say-do problem:  The loan approval process described to you by the loan approval officers is quite different from your observations of what they actually do  Probe effect:  The loan approval process used by the officers while you are observing is different from the one they normally use  Bias:  The loan approval officers fear that your job is to computerize their jobs out of existence, so they are deliberately emphasizing the need for case-by-case discretion (to convince you it has to be done by a human!)

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 5 Bias Ü What is bias?  Bias only exists in relation to some reference point  can there ever be “no bias”?  All views of reality are filtered  All decision making is based partly on personal values. Ü Types of bias:  Motivational bias  expert makes accommodations to please the interviewer or some other audience  Observational bias  Limitations on our ability to accurately observe the world  Cognitive bias  Mistakes in use of statistics, estimation, memory, etc.  Notational bias  Terms used to describe a problem may affect our understanding of it Examples of Bias  Social pressure response to verbal and non-verbal cues from interviewer  Group think response to reactions of other experts  Impression management response to imagined reactions of managers, clients,…  Wishful thinking response to hopes or possible gains.  Appropriation Selective interpretation to support current beliefs.  Misrepresentation expert cannot accurately fit a response into the requested response mode  Anchoring contradictory data ignored once initial solution is available  Inconsistency assumptions made earlier are forgotten  Availability some data are easier to recall than others  Underestimation of uncertainty tendency to underestimate by a factor of 2 or 3. Examples of Bias  Social pressure response to verbal and non-verbal cues from interviewer  Group think response to reactions of other experts  Impression management response to imagined reactions of managers, clients,…  Wishful thinking response to hopes or possible gains.  Appropriation Selective interpretation to support current beliefs.  Misrepresentation expert cannot accurately fit a response into the requested response mode  Anchoring contradictory data ignored once initial solution is available  Inconsistency assumptions made earlier are forgotten  Availability some data are easier to recall than others  Underestimation of uncertainty tendency to underestimate by a factor of 2 or 3.

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 6 Elicitation Techniques Ü Traditional techniques  Introspection  Reading existing documents  Analyzing hard data  Interviews  Open-ended  Structured  Surveys / Questionnaires  Meetings Ü Collaborative techniques  Focus Groups  Brainstorming  JAD/RAD workshops  Prototyping  Participatory Design Ü Contextual (social) approaches  Ethnographic techniques  Participant Observation  Enthnomethodology  Discourse Analysis  Conversation Analysis  Speech Act Analysis  Sociotechnical Methods  Soft Systems Analysis Ü Cognitive techniques  Task analysis  Protocol analysis  Knowledge Acquisition Techniques  Card Sorting  Laddering  Repertory Grids  Proximity Scaling Techniques

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 7 Background Reading Ü Sources of information:  company reports, organization charts, policy manuals, job descriptions, reports, documentation of existing systems, etc. Ü Advantages:  Helps the analyst to get an understanding of the organization before meeting the people who work there.  Helps to prepare for other types of fact finding  e.g. by being aware of the business objectives of the organization.  may provide detailed requirements for the current system. Ü Disadvantages:  written documents often do not match up to reality.  Can be long-winded with much irrelevant detail Ü Appropriate for  Whenever you not familiar with the organization being investigated.

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 8 “Hard Data” and Sampling Ü Hard data includes facts and figures…  Forms, Invoices, financial information,…  Reports used for decision making,…  Survey results, marketing data,… Ü Sampling  Sampling used to select representative set from a population  Purposive Sampling - choose the parts you think are relevant without worrying about statistical issues  Simple Random Sampling - choose every kth element  Stratified Random Sampling - identify strata and sample each  Clustered Random Sampling - choose a representative subpopulation and sample it  Sample Size is important  balance between cost of data collection/analysis and required significance  Process:  Decide what data should be collected - e.g. banking transactions  Determine the population - e.g. all transactions at 5 branches over one week  Choose type of sample - e.g. simple random sampling  Choose sample size - e.g. every 20th transaction

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 9 Example of hard data Ü Questions:  What does this data tell you?  What would you do with this data?

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 10 Source: Adapted from Goguen and Linde, 1993, p154. Interviews Ü Types:  Structured - agenda of fairly open questions  Open-ended - no pre-set agenda Ü Advantages  Rich collection of information  Good for uncovering opinions, feelings, goals, as well as hard facts  Can probe in depth, & adapt follow up questions to what the person tells you Ü Disadvantages  Large amount of qualitative data can be hard to analyze  Hard to compare different respondents  Interviewing is a difficult skill to master Ü Watch for  Unanswerable questions (“how do you tie your shoelaces?”)  Tacit knowledge (and post-hoc rationalization)  Removal from context  Interviewer’s attitude may cause bias (e.g. variable attentiveness)

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 11 Interviewing Tips Ü Starting off…  Begin the interview with an innocuous topic to set people at ease  e.g. the weather, the score in last night’s SOCCER game  e.g. comment on an object on the person’s desk: “…what a beautiful photograph! Did you take that?” Ü Ask if you can record the interview  Make sure the tape recorder is visible  Say that they can turn it off at any time. Ü Ask easy questions first  perhaps personal information  e.g. “How long have you worked in your present position?” Ü Follow up interesting leads  E.g. if you hear something that indicates your plan of action may be wrong,  e.g.,“Could we pursue what you just said a little further?” Ü Ask open-ended questions towards the end  e.g. “Is there anything else you would like to add?”

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 12 Questionnaires Ü Advantages  Can quickly collect info from large numbers of people  Can be administered remotely  Can collect attitudes, beliefs, characteristics Ü Disadvantages  Simplistic (presupposed) categories provide very little context  No room for users to convey their real needs Ü Watch for:  Bias in sample selection  Bias in self-selecting respondents  Small sample size (lack of statistical significance)  Open ended questions (very hard to analyze!)  Leading questions (“have you stopped beating your wife?”)  Appropriation (“What is this a picture of?”)  Ambiguous questions (I.e. not everyone is answering the same question) Source: Adapted from Goguen and Linde, 1993, p154. Note: Questionnaires MUST be prototyped and tested!

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 13 Meetings Ü Used for summarization and feedback  E.g. meet with stakeholders towards the end of each stage:  to discuss the results of the information gathering stage  to conclude on a set of requirements  to agree on a design etc.  Use the meeting to confirm what has been learned, talk about findings Ü Meetings are an important managerial tool  Used to move a project forward.  Every meeting should have a clear objective:  E.g. presentation, problem solving, conflict resolution, progress analysis, gathering and merging of facts, training, planning,...  Plan the meeting carefully:  Schedule the meeting and arrange for facilities  Prepare an agenda and distribute it well in advance  Keep track of time and agenda during the meeting  Follow up with a written summary to be distributed to meeting participants  Special rules apply for formal presentations, walkthroughs, brainstorming, etc.

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 14 Group Elicitation Techniques Ü Types:  Focus Groups  Brainstorming Ü Advantages  More natural interaction between people than formal interview  Can gauge reaction to stimulus materials (e.g. mock-ups, storyboards, etc) Ü Disadvantages  May create unnatural groups (uncomfortable for participants)  Danger of Groupthink  May only provide superficial responses to technical questions  Requires a highly trained facilitator Ü Watch for  sample bias  dominance and submission

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 15 Joint/Rapid Application Development Ü JAD & RAD Principles:  Group Dynamics - use workshops instead of interviews  Visual Aids  Lots of visualization media, e.g. wall charts, large monitors, graphical interfaces  Organized, Rational Process  Techniques such as brainstorming and top-down analysis  WYSIWYG Documentation Approach  each JAD session results in a document which is easy to understand and is created and agreed upon during the session Ü Notes:  Choose workshop participants carefully  they should be the best people possible representing various stakeholder groups  Workshop should last 3-5 days.  Must turn a group of participants into a team - this takes 1-2 days.  Session leader makes sure each step has been completed thoroughly.  Session leader steps in when there are differences of opinion - “open issues”.  Meeting room should be well-equipped for presentations, recording etc.

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 16 Participant Observation Ü Approach  Observer spends time with the subjects  Joining in long enough to become a member of the group  Hence appropriate for longitudinal studies Ü Advantages  Contextualized;  Reveals details that other methods cannot Ü Disadvantages  Extremely time consuming!  Resulting ‘rich picture’ is hard to analyze  Cannot say much about the results of proposed changes Ü Watch for  going native!

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 17 Ethnomethodology Ü Basis  Social world is ordered  The social order may not be obvious, nor describable from common sense  The social order cannot be assumed to have an a priori structure  Social order is established on a moment-to-moment basis through participants’ collective actions (no pre-existing structures)  i.e. social order only observable when an observer immerses herself in it.  Observation should be done in a natural setting  Need to consider how meanings develop and evolve within context Ü “Use the members’ own Categories”  Most conventional approaches assume preexisting categories  This may mislead the observer (e.g. appropriation)  Ethnography attempts to use the subjects’ own categories  What categories (concepts) do they use themselves to order the social world?  What methods do people use to make sense of the world around them?  Use the same methods members use during observation  E.g by developing a legitimate role within the community under observation. Source: Adapted from Goguen and Linde, 1993, p158.

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 18 Ethnomethodological Approach Ü Ethnomethodology is a subarea of Anthropology  Looks for behaviours that are culture-specific  E.g. Italians brag about sexual conquests to gain status;  E.g. Americans brag about money to gain status.  Each of these topics is taboo in the other culture Ü Uses a very tightly controlled set of methods:  Conversational analysis  Measurement of body system functions - e.g. heartbeat  Non-verbal behavioural studies  Detailed video analysis  These techniques are useful in capturing information about a social setting. Ü Other observation techniques can be applied:  Time-motion study  who is where, when?  Communication audit  who talks to whom about what?  Use of tools - status symbols plus sharing rules

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 19 Knowledge Elicitation (KE) Techniques Ü Protocol Analysis  based on vocalizing behavior  Think aloud vs. retrospective protocols  Advantages  Direct verbalization of cognitive activities  Embedded in the work context  Good at revealing interaction problems with existing systems  Disadvantages  Essentially based on introspection, hence unreliable  No social dimension Source: Adapted from Hudlicka, Ü Proximity Scaling Techniques  Given some domain objects, derive a set of dimensions for classifying them: step 1: pairwise proximity assessment among domain elements step 2: automated analysis to build multi- dimensional space to classify the objects  Advantages  help to elicit mental models, where complex multivariate data is concerned  good for eliciting tacit knowledge  Disadvantages  Requires an agreed on set of objects  Only models classification knowledge (no performance knowledge)

© Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 20 More KE techniques Ü Card Sorting  For a given set of domain objects, written on cards:  Expert sorts the cards into groups... ...then says what the criterion was for sorting, and what the groups were.  Advantages  simple, amenable to automation  elicits classification knowledge  Problems  suitable entities need to be identified with suitable semantic spread across domain.  No performance knowledge Ü Laddering  Uses a set of probes to acquire stakeholders’ knowledge.  Interview the expert.  Use questions to move up and down a conceptual hierarchy  E.g. developing goal hierarchies  Advantages  deals with hierarchical knowledge, including poly-hierarchies (e.g., goal trees, “is-a” taxonomies).  knowledge is represented in standardised format  can elicit structural knowledge  suitable for automation.  Disadvantages  assumes hierarchically arranged knowledge.