CIS 255.  Impertinence—question everything  Impartiality  Relaxing of Constraints—Assume everything is possible.  Attention to Detail—Every fact must.

Slides:



Advertisements
Similar presentations
Requirements Analysis. Methods of Collecting System Requirements Interview people (individually) informed about the operations and issues of the current.
Advertisements

 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.
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.
Requirements Gathering
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Systems Analysis Requirements determination Requirements structuring
Gathering Information and Use Case Scenarios
Systems Analysis and Design in a Changing World, Fourth Edition
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 5 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.
Chapter 4: Beginning the Analysis: Investigating System Requirements
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.
Chapter 6 Determining System Requirements
Chapter 6 Determining System Requirements
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.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
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.
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.
Systems Analysis and Design in a Changing World, Thursday, Feb 1.
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.
Investigating System Requirements
Questionnaires Justine Ruan Jonathan Shiraki. What are Questionnaires? A document that allows the analyst to collect information and opinions from respondents.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
C_ITIP211 LECTURER: E.DONDO.  Gather information on what system should do from many sources ◦ Users ◦ Reports ◦ Forms ◦ Procedures.
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.
MBI 630: Systems Analysis and Design Toru Sakaguchi, Ph.D.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Modern Systems Analysis and Design Third Edition
Chapter 7 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Requirements Determination
Rekayasa Perangkat Lunak Part-14
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:

CIS 255

 Impertinence—question everything  Impartiality  Relaxing of Constraints—Assume everything is possible.  Attention to Detail—Every fact must fit every other fact  Reframing—look at the problem in new ways

 Interviews  Questionnaires  Observations of Workers  Business Documents

 Plan interview—prepare a checklist, agenda, questions  Be neutral  Listen and take notes  Review notes—transcribe them within 48 hours  Seek diverse points of view

 Open ended questions –what is the worst thing about your current system?  Close ended questions—multiple choice, true/false, ranking

 Must be careful who you sample and if there is a bias in the answers  Questions must be unambigous  Better for gathering specific information, than for determining general requirments

 Interviews are more open ended and allow immediate follow up on answers  Questionnaires allow access to larger groups and have a quicker response time.  It is harder to judge the accuracy or truthfulness of a questionnaire.  Questionnaires tend to be less expensive than interviews

 Observation is essential  Workers often do not have a full, accurate appreciation for what they do  They may take parts of it for granted as being too trivial to mention  They may not mention the interruptions and other events that contribute to what they do

 Documents can tell you ◦ Problems with current system ◦ Opportunities to meet new needs if only information were available ◦ Organizational directions ◦ Titles and names of key individuals ◦ Values of the organization ◦ Special information processing circumstances ◦ Reasons why the current system has its present design ◦ Data, rules for processing data

 Joint Application Design  Business Process Reengineering

 Joint Application Design brings all the stakeholders together in the design process— literally bringing them all to one room

 Session Leader  Users  Managers  Sponsor (Vice President, President of company)  Systems analysts  Scribe  IS staff

 This is basically to ask the question, if we could start over from scratch, how would we redesign the system differently.  It advocated radical redesign of individual business systems