The Analysis Phase: Gathering Information

Slides:



Advertisements
Similar presentations
Methodology and Explanation XX50125 Lecture 3: Interviews and questionnaires Dr. Danaë Stanton Fraser.
Advertisements

Session # 2 SWE 211 – Introduction to Software Engineering Lect. Amanullah Quadri 2. Fact Finding & Techniques.
Requirements Analysis. Methods of Collecting System Requirements Interview people (individually) informed about the operations and issues of the current.
© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.
 Interviewing individuals  Interviewing groups  Observing workers  Studying business documents 1.
© Copyright 2011 John Wiley & Sons, Inc.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Required Skills for IS PM. Contemplative Questions What skills are important for work in IS? What skills are important for work in IS? Do I have these.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Systems Analysis Requirements determination Requirements structuring
Gathering Information and Use Case Scenarios
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Requirements Gathering. Adapted from PowerPoint Presentation for Dennis, Wixom & Tegardem, Systems Analysis and Design, John Wiley & Sons, Inc. For CSU’s.
WRITING THE ClASS REPORT
Requirements Modeling
Choosing Your Primary Research Method What do you need to find out that your literature did not provide?
James Wolff Monita Baba-Djara March 26,  Course goal: ◦ To prepare students to work in maternal and child health in a developing country setting.
Slide 1 IS6112 – Application Modelling and Design.
The Analysis Phase: Gathering Information. The Analysis Phase The “ Analysis Phase ” answers the questions of who will use the system, what the system.
PRJ566 Project Planning and Management
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
System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination.
CS211 Slide 3-1 ADCS 21 Systems Analysis Phase Overview Systems Requirements Checklist Fact-Finding techniques Documentation (Chapter 3) SYSTEMS ANALYSIS.
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.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Requirements Determination
Principles of Marketing - UNBSJ
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Requirements Determination
CHAPTER OVERVIEW The Case Study Ethnographic Research
Information Systems Development
TIM 58 Chapter 3, continued: Requirements Determination Ch
Chapter 2 Sociological Research Methods.
Requirements Determination
Rekayasa Perangkat Lunak Part-14
Imran Hussain University of Management and Technology (UMT)
Systems Analysis & Design N106
Fundamentals of Information Systems, Sixth Edition
Chapter 5 Determining System Requirements
TIM 58 Chapter 3: Requirements Determination
Investigation Techniques
Modern Systems Analysis and Design Third Edition
Asking questions: Interviews, Wednesday 14th December 2016
Chapter 2 Sociological Research Methods
ELT. General Supervision
Essentials of Systems Analysis and Design Fourth Edition
Lecture 1: Course Outline and Introduction
CIS 210 Systems Analysis and Development
Information Systems Development MIS331
Lecture 2: Data Collecting and Sampling
Data and Data Collection
Rekayasa Perangkat Lunak
EVIDENCE COLLECTION TECHNIQUES (Interview)
Modern Systems Analysis and Design Third Edition
Experimental Software Engineering (ESE)
Modern Systems Analysis and Design Third Edition
AUDIT TESTS.
CHAPTER OVERVIEW The Case Study Ethnographic Research
Lesson Aims 1. Examine the skills needed in order to conduct a good interview 2. Identify the main types of interviews used in sociological research 3.
Case studies: interviews
Presentation transcript:

The Analysis Phase: Gathering Information

The Analysis Phase Understanding the “As-Is System” The “Analysis Phase” answers the questions of who will use the system, what the system will do, and where and when it will be used. It consists of three stages: Understanding the “As-Is System” Identifying the improvements needed to that system Producing a description of the “To-Be System”

Objectives Understand how to use interviews to gather requirements information Understand how to use joint application design sessions to gather requirements information Be familiar with questionnaires Be familiar with document analysis Be familiar with observation Understand when to use each technique

Information Gathering Strategies There are many strategies for information gathering, we will focus on five strategies: Interviews Joint Application Design (JAD) sessions Document Analysis Observation Questionnaires

Information Gathering Strategies Information gathering strategies by degree of intrusiveness Observation Document Analysis Questionnaires Interviews Joint Application Design (JAD) sessions

Interviews Selecting Interviewees Designing Interview Questions The interview is the most commonly used information-gathering technique. There are five basic steps to the interview process: Selecting Interviewees Designing Interview Questions Preparing for the Interview Conducting the Interview Follow-up

Joint Application Design (JAD) JAD is an information-gathering technique for large groups the project team, users and management JAD is a structured process that requires a skilled facilitator. The facilitator is the person who sets the meeting agenda and guides the discussion. The facilitator remains neutral during the discussion.

Questionnaires Questionnaires (surveys) are often used when there is a large number of people (the population) who may have the information needed for the project. Instead of interviewing, or even surveying, everyone (this would be a census), a representative sample of the population is taken. Can cover a wider range of the population than interviews, but lack the richness of detail that interviews can provide.

Document Analysis Document analysis can be very useful in understanding the as-is system. Provide strong evidence of how the as-is system was intended to operate. However, it is important to distinguish between the formal and informal systems. Documents can help with both.

Observation Observation can be used see how the as-is system actually operates. Observation in conjunction with the other techniques is very helpful in distinguishing between the formal and informal systems. However, an observer must be careful of the “Hawthorne Effect.”

Information Gathering Strategies Getting the actual information is not as trivial The "more intrusive" methods (interviews and joint application development) have the advantage of being able to adjust questions based on previous responses but take considerably more time. One approach is to use less intrusive methods first (document analysis and observation) then follow up with the other three methods (interviews, JAD, or questionnaires) based on these findings.

Selecting the Appropriate Technique There is no one appropriate technique; each has its strengths and weaknesses. Generally a combination of techniques is best. Consideration should be given to: Type of Information Depth of Information Breadth of Information Integration of Information User Involvement Cost

Risk Management What are some of the risks that we might encounter even before the system is deployed? That is, in the SDLC process. Would you make a good analyst?

A hypothetical problem You have been asked to design a “part 2” of A337 that includes more hands-on computer skill development. The student group that designs the best course will receive University recognition as well as a substantial cash award.

A hypothetical problem What would you suggest as a analysis plan for this object? Your final result should include all sources of information, the type of information sought, the method(s) you will use, and the order in which you will perform will acquire the information (if that is important)

A hypothetical problem 2 An unscrupulous group of A337 students want to maximize their course grade at the expense of honesty. They believe that a high final score is the secret. The students have even gone as far as to offer payments to “analysts” (i.e., past and current A337 students) based on their test “performance”

A hypothetical problem 2 The “analysts” get paid more for presenting their findings earlier  The analysts get a bonus after the fact based on how well the students actually did on the exam. What would you suggest as a analysis plan for these scoundrels? Consider the methods, “respondents”, and the order you would use.