Categorization of Sample Types No Random Selection Random Selection No Specific Selection Criteria Applied Convenience Sample Simple Random Sample Specific.

Slides:



Advertisements
Similar presentations
Qualitative and Observational Research
Advertisements

© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Seminar Topic: Questionnaire Presented by : Rekha HR.
Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
ANALYSIS PHASE Systems analysis is the part of the SDLC in which to determine how the current information system functions and asses what users would like.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Systems Analysis Requirements determination Requirements structuring
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Determining System Requirements
Chapter 4: Beginning the Analysis: Investigating System Requirements
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Traditional Approach Using Questionnaires. 2 Introduction  Questionnaires  for acquiring large amount of information  Questionnaires allow us to study:
DR. DAWNE MARTIN MKTG 241 FEB. 15, 2011 Marketing Research.
Chapter 4: Beginning the Analysis: Investigating System Requirements
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.
The Information Component: Help Desk Performance Measures
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Requirements Gathering Chapter 5 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon Negash.
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.
Modern Systems Analysis and Design Third Edition
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
ITCS311 Systems Analysis and Design Dr. Taher Homeed Feb 2010 Department of Computer Science College of IT University of Bahrain.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
University of california, san francisco school of medicine Focus Groups For Educational Research and Evaluation School of Medicine Educational Skills Workshop.
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.
University of Sunderland Professionalism and Personal Skills Unit 9 Professionalism and Personal Skills Lecture Data Collection.
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.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
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.
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 4 Systems Requirements Determination.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Interviews By Mr Daniel Hansson.
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.
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Quantitative Data Collection In Advertising Research.
Fashion MARKETING TID1131. Types of research Quantitative research Information relating to numbers – quantity. Method - surveys Qualitative research To.
Questionnaires Justine Ruan Jonathan Shiraki. What are Questionnaires? A document that allows the analyst to collect information and opinions from respondents.
6-1 Functional vs. Nonfunctional Requirements Functional requirement - something the information system must do Nonfunctional requirement - a property.
Marketing Research Systems Chapter 5 Unlocking the secrets of your market segments…
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Fact Finding (Capturing Requirements) Systems Development.
5-1 © Prentice Hall, 2004 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Improved socio-economic services for a more social microfinance.
 System Requirement Specification and System Planning.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
INTERVIEW SALEEQ AHMAD University of Delhi.
Modern Systems Analysis and Design Third Edition
Chapter 5 Determining System Requirements
Chapter 5 Determining System Requirements
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
Chapter 7 Determining System Requirements
Overview Characteristics for gathering requirements.
Chapter 4 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Categorization of Sample Types No Random Selection Random Selection No Specific Selection Criteria Applied Convenience Sample Simple Random Sample Specific Selection Criteria Applied Purposive Sample Complex Random Sample

Sample Business Form

IBID Electronic Whiteboard Source:

Requirements Determination Information Gathering ApproachExamples Interview - current system operations - data needs - proposed system requirements - process sequences Questionnaire - confirmation of facts- end-user demographics - general user attitudes Focus Group - conflicting system requirements - synergies across functional areas Observation - implementation of current processes - confirmation of interview data Archival Document Analysis - Org. policies & procedures - current system documentation - examples of data capture & usage External Research - industry best-practices - technological developments Joint Application Design - synergistic gathering of system requirements - identification of conflicting perspectives Iterative Prototyping - refined understanding of system configuration - operationalization of system look and feel

Well-Stated System Requirements Requirements Characteristic Description Testable and Verifiable Requirement must be stated to allow for independent verification that the system meets or exceeds the stated requirement. Justifiable Requirement should be necessary rather than simply desirable. Unambiguous Requirement should be stated such that multiple interpretations are excluded. Consistent Requirement should not be in conflict with any other stated requirement. Modifiable Requirement should allow for changes in the business environment. Hierarchically Traceable Requirement should contain a single system attribute and should be traceable back to a higher level requirement.

Testable vs. Nontestable Testable RequirementNontestable Requirement Compute Price Extension by multiplying Quantity by Unit Price. Price Extension is the total cost for each item ordered. Reorder Quantity is computed by multiplying Average Daily Sales by 30. Reorder Quantity should be equal to a 30 day supply. Daily inventory levels must be accurate.Daily inventory levels must be accurate to within 2% for at least 99% of all raw material stores. The system must increase sales and market share. The system will increase annual sales by 14% and current market share by 6.5% within the first 12 months of operation.

Traditional Information Gathering Information Gathering Activity Explanation Direct Interview Consists of meeting with individuals or small groups to ask questions about their roles, responsibilities, and needs for the current and proposed systems. Questionnaires and Surveys Consists of submitting written, structured questions to selected individuals to gather information regarding attitudes, perceptions, or population characteristics. Direct Observation Consists of observing individuals or groups, processes, and events to determine the facts surrounding a particular process or the culture within a business environment. Archival Document Analysis Consists of reviewing recorded organizational documents such as current system documentation, mission statements, policies and procedures, and recorded memos and reports. Forms Analysis Consists of analyzing and cataloging the existing data capture forms within the organization to assist in determining the current sources and uses of data.

Direct Interview AdvantagesDisadvantages Analyst can motivate the respondent to answer freely and openly. Respondent can more easily develop a sense of active contribution to the proposed system. Analyst can probe for additional information and feedback. Questions can be reworded or restated for better clarity or to facilitate mutual understanding. Analyst can easily observe nonverbal communication channels such as body language and facial expressions. The interview process is time-consuming and resource intensive. Interview success is highly dependent on the communication skills of the analyst. Geographical location of the necessary respondents may make the interview process impractical.

Structured vs. Unstructured VariableStructured Interview Unstructured Interview Required preparation time HighLow Required contact time with respondent ModerateHigh Analyst experience and training required HighLow Evaluation of results and responses EasyDifficult Degree of spontaneity of responses LowHigh Depth and breadth of topic coverage ModerateHigh Reliability and precision of responses Moderate to HighLow to Moderate Insight into respondent LowHigh Overall analyst control of dialogue HighLow to Moderate Degree of flexibility of interaction LowHigh

Open vs. Closed Questions

Questionnaires AdvantagesDisadvantages Questionnaires can often be answered in less time. Respondents can answer questions at their convenience. Responses can be easily tabulated and analyzed. Questionnaires allow for respondents to maintain anonymity. Response rate is often low. Questionnaires allow for less flexibility than other, more direct methods. No guarantee exists that respondent will answer all questions posed. No direct observation of the respondent can be conducted during questioning. Questionnaires are often time- consuming and difficult to prepare. No opportunity to clarify points or expand on topics covered.

Scaling Methods

Scaling Methods (continued)

Choosing the Appropriate Scale Scale TypeGeneral Application Nominal Classification without need for ranking Ordinal Classification with ranking but without need for equal intervals between ranks Interval Degree of presence of phenomena using equal intervals without need for absolute zero Ratio Degree of presence or absence of a phenomena

Confidence Coefficients Level of Confidence (%)Confidence Coefficient (z)

JAD Participants JAD Participant Description of Role Session Leader organizes and runs the actual JAD session remains neutral on all issues and does not contribute ideas or opinions sets the agenda for the meeting concentrates on keeping to agenda, resolving conflicts, & generating dialogue from participants User represents end users’ perspective with regard to proposed system Manager represents management’s perspective with regard to proposed system Project Sponsor represents all parties responsible for funding and supporting the development effort Analyst analyst participation is limited to observation and listening to better understand the needs of the users and managers Scribe responsible for taking notes and recording important information and events relevant to the JAD proceedings IS Staff responsible for providing clarification on technical questions and issues contribute ideas on technical feasibility of and limitations of proposed system components