MIS 321 PS 2 FACT FINDING METHODS: SURVEY AND INTERVIEW.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Systems Development Environment
Chapter 2 Analyzing the Business Case.
Requirements Modeling
Chapter 1 Assuming the Role of the Systems Analyst
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Chapter 8 Information Systems Development & Acquisition
Lab/Sessional -CSE-374. TACKLING COMPUTER PROJECT A step-by-step guide to better projects.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Computers: Tools for an Information Age
Systems Analysis Requirements determination Requirements structuring
Systems Analysis and Design in a Changing World, Fourth Edition
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Chapter 5 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.
Introduction to Systems Analysis and Design
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
SDLC and alternative methodologies 1/14/2015 © Abdou Illia MIS Spring 2015.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Acquiring Information Systems and Applications
Requirements Modeling
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Systems Analysis and Design: The Big Picture
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
System Analysis and Design 3 rd Lecture اعداد : أ.ساره الحجام.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Information Systems in Organisations System Development: The Environment.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Problem Identification
PRJ566 Project Planning and Management
Chapter 14 Information System Development
Chapter 16 Structured Systems Analysis. Learning Objectives Know goals, plans, tasks, tools, & results of systems analysis Understand/appreciate costs.
1 SYS366 Week 4, Lecture 1 Introduction to Requirements Gathering: Part 3 – Getting to Software Requirements.
Modern Systems Analysis and Design Third Edition
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
Database Analysis and the DreamHome Case Study
CHAPTER 13 Acquiring Information Systems and Applications.
1 SYS366 Week 5 - Lecture 1 Systems Requirements Gathering: Identifying Software Requirements.
IFS310: Module 3 1/25/2007 Fact Finding Techniques.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
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.
 2004 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, by Bodnar/Hopwood 10 – 1 Systems Planning and Analysis Chapter 10.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
SYS366 Week 7, Lecture 1 Introduction to Requirements Gathering:
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
Chapter 6 Determining System Requirements. Objectives:  Describe interviewing options and develop interview plan.  Explain advantages and pitfalls of.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
Systems Analysis Requirements Modeling Systems Analysis and Design Fourth Edition SDLC Phases Phase 2: Systems Analysis Objectives  Develop a logical.
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.
Modern Systems Analysis and Design Third Edition
Fundamentals of Information Systems, Sixth Edition
Chapter 5 Determining System Requirements
SYSTEMS ANALYSIS Chapter-2.
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
Chapter 7 Determining System Requirements
Chapter 4 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Presentation transcript:

MIS 321 PS 2 FACT FINDING METHODS: SURVEY AND INTERVIEW

SYSTEM DEVELOPMENT LIFE CYCLE

PLANNING Determine tasks, choose personnel, assign related personnel to the right tasks, prepare schedule etc. Planning Tools: MS Project

ANALYSIS System analysis is the second phase of the systems development life cycle (SDLC). In the analysis phase, our objective is to: Determine and document how the current system works Determine how the system could work better Develop a logical or business model of the new system Make recommendations to management We will go through three major steps to address the above objectives: Determine Systems Requirements Analyze Systems Requirements Evaluate Alternative Solutions

ANALYSIS To determine system requirements, the analyst sought information of the current system and the opportunities for improvements in the following areas: System Objectives: Identify the objectives of the current system Evaluate these objectives System Inputs and Outputs: Identify the inputs and outputs of the current system The origin of the inputs and the destinations of the outputs System Functions: Define the functions of the current system Identify the components of the systems: manual procedures, user interfaces, computer programs, files and databases Identify timings of input, output and processing Identify controls on data entry, security, and processing

ANALYSIS FACT FINDING METHODS: Interviews Questionnaires Review Documentation Observation Prototypes JAD Sessions (Joint Application Design) RAD (Rapid Application Development)

Interview The interview is the most common method of information-gathering techniques. There are several basic steps to the interview process: Preparation for the Interview Design of Interview Questions Conduct the Interview Document the Interview Perform a Follow-Up Interview.

Interview Example INFORMATION ABOUT INTERVIEWEE Reyhan Çepik- CoFounder of firsatbufirsat.com Oğuz Arslan-CoFounder of firsatbufirsat.com Questions Asked: 1. How many deals did you sell last month? What is the average for one month? 2. Nowadays, there are certain big firms which step back from this sector. What do you think about that? Is that a sign for group buying sector about coming to an end ? 3. Many users think that daily mailing is disruptive. On the other hand, you need to promote your company. How often do you think people should be informed about promotions? 4. When they register to the platform, do you think it is critical to ask users whether they want to be informed about promotions? 5. Are there any other fields that you want to have promotions on website? For example, we usually see brunch or wealth opportunities. Discounts on technological products may be a new and increasing demanded platform. 6. What are the criterias that you are looking for when dealing with a company? 7. What is the largest age group among your users? 8. Have you ever had any trouble with the companies you work with ?

Questionnaire A project that requires input from a large number of people, the questionnaire can be a valuable tool to determine system requirements. A questionnaire is a document containing a number of standard questions that can be sent to many individuals. Questionnaires can be used to obtain information about workloads, reports received, volumes of transactions handled, types of job duties, difficulties, and opinions of how the job could be performed.

Questionnaire Some guidelines for designing questionnaire are: Brief and user-friendly Clear instructions Ask questions related to the requirement Questions in logical order Simple wording to avoid misunderstanding Avoid leading questions Open-ending questions are difficult to tabulate Limit questions raising concern/negative issues Section for general comments Test the questionnaire in advance

Questionnaire Example

WF2zKW0PWAN6mdUly4/viewform WF2zKW0PWAN6mdUly4/viewform UogdV_2IovT2VlLaopGt3hu_VUNnJ5fGh68/viewform UogdV_2IovT2VlLaopGt3hu_VUNnJ5fGh68/viewform