MBI 630: Systems Analysis and Design Toru Sakaguchi, Ph.D.

Slides:



Advertisements
Similar presentations
Chapter 6 Determining System Requirements
Advertisements

Requirements Analysis. Methods of Collecting System Requirements Interview people (individually) informed about the operations and issues of the current.
 Interviewing individuals  Interviewing groups  Observing workers  Studying business documents 1.
Investigating and Determining System Requirements
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Requirements Gathering
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Systems Analysis Requirements determination Requirements structuring
Information Systems System Analysis 421 Class Four
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.
Chapter 6 Determining System Requirements
Chapter 5 Determining System Requirements
Chapter 6 Determining System Requirements
Determining 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.
IFS310: Week 2 BIS310: Structured Analysis and Design 3/23/2008 Fact Finding Techniques and Structured Methodology.
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 6 Determining System Requirements
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 7 Slide 1 Chapter 6 Determining System Requirements.
Determining System Requirements Classes 9,10. SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical.
Chapter 6 Determining System Requirements
Chapter 6 Determining System Requirements
Chapter 6 Determining System Requirements
System Analysis and Design 3 rd Lecture اعداد : أ.ساره الحجام.
BIS 360 – Lecture Five Ch. 7: Determining System Requirements.
Modern Systems Analysis and Design Third Edition
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
Chapter 6 Determining System Requirements Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Requirements Modeling
IS2210: Systems Analysis and Systems Design and Change Twitter:
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.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
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.
Modern Systems Analysis and Design Fifth Edition
© 2005 by Prentice Hall Chapter 6 Determining System Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph.
Systems Analysis And Design
Investigating System Requirements
Lecture 6 Determining System Requirements. Copyright © 2011 Pearson Education, Inc. 2 Chapter 6 Performing Requirements Determination FIGURE 6-1 Systems.
C_ITIP211 LECTURER: E.DONDO.  Gather information on what system should do from many sources ◦ Users ◦ Reports ◦ Forms ◦ Procedures.
5-1 © Prentice Hall, 2004 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Modern Systems Analysis and Design Third Edition
Chapter 3 Determining System Requirements
Chapter 7 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Chapter 5 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Chapter 5 Determining System Requirements
Investigating System Requirements
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
CIS 210 Systems Analysis and Development
Rekayasa Perangkat Lunak
Chapter 5 Determining System Requirements
Chapter 7 Determining System Requirements
Overview Characteristics for gathering requirements.
Modern Systems Analysis and Design Third Edition
Chapter 4 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Presentation transcript:

MBI 630: Systems Analysis and Design Toru Sakaguchi, Ph.D.

Class 2: Determining Requirements Sample Case –Interview key users –Discussion of requirements –Presentation (if time allows) Determining Requirements

Traditional Methods for Determining Requirements Interviewing and Listening –Gather facts, opinions and speculations –Observe body language and emotions –Guidelines Plan –Checklist –Appointment Be neutral Listen Seek a diverse view

Traditional Methods for Determining Requirements Interviewing (Continued) –Interview Questions Open-Ended –No pre-specified answers Close-Ended –Respondent is asked to choose from a set of specified responses –Additional Guidelines Do not phrase questions in ways that imply a wrong or right answer Listen very carefully to what is being said Type up notes within 48 hours Do not set expectations about the new system

Traditional Methods for Determining Requirements Interviewing Groups –Advantages More effective use of time Enables people to hear opinions of others and to agree or disagree –Disadvantages Difficulty in scheduling –Nominal Group Technique Facilitated process to support idea generation by groups Individuals work alone to generate ideas which are pooled under guidance of a trained facilitator

Traditional Methods for Determining Requirements Administering Questionnaires –More cost-effective than interviews –Choosing respondents Should be representative of all users Types of samples –Convenient –Random sample –Purposeful sample –Stratified sample

Traditional Methods for Determining Requirements Questionnaires –Design Mostly closed-ended questions Can be administered over the phone or in person –Vs. Interviews Interviews cost more but yield more information Questionnaires are more cost-effective

Traditional Methods for Determining Requirements Directly Observing Users –Serves as a good method to supplement interviews –Often difficult to obtain unbiased data People often work differently when being observed

Analyzing Procedures and Other Documents Types of information to be discovered: –Problems with existing system –Opportunity to meet new need –Organizational direction –Names of key individuals –Values of organization –Special information processing circumstances –Reasons for current system design –Rules for processing data

Analyzing Procedures and Other Documents Four types of useful documents –Written work procedures Describes how a job is performed Includes data and information used and created in the process of performing the job or task –Business form Explicitly indicate data flow in or out of a system –Report Enables the analyst to work backwards from the report to the data that generated it –Description of current information system