System Analysis-Gathering Requirements.  System analysis is the process of gathering info about existing system, which may be computerized or not, while.

Slides:



Advertisements
Similar presentations
Fact Finding Techniques
Advertisements

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Session # 2 SWE 211 – Introduction to Software Engineering Lect. Amanullah Quadri 2. Fact Finding & Techniques.
© 2005 Prentice Hall13-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
ACCOUNTING INFORMATION SYSTEMS
 Interviewing individuals  Interviewing groups  Observing workers  Studying business documents 1.
Chapter Fourteen Chapter Fourteen.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
© Copyright 2011 John Wiley & Sons, Inc.
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.
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Chapter 5 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.
Fact-finding Techniques
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
3 Methods for Collecting Data Mgt Three Major Techniques for Collecting Data: 1. Questionnaires 2. Interviews 3. Observation.
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
Requirements Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 7 Slide 1 Chapter 6 Determining System Requirements.
Approaches to Investigating a System “Who knows what’s happening now?”
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Lect 6 chapter 3 Research Methodology.
The Analysis Phase: Gathering Information. The Analysis Phase The “ Analysis Phase ” answers the questions of who will use the system, what the system.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 03: Requirements Capture Requirements Analysis.
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
Data Collection Methods
Systems Life Cycle 1.Project Idenification 2. Initial Investigation 3. Feasibilty Study 4. Analysis 5. Design 6. Development and testing 7. Implementation.
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.
Fact-finding Transparencies 1. ©Pearson Education 2009 Objectives When fact-finding techniques are used in the database system development lifecycle.
Chapter 13. Reviewing, Evaluating, and Testing © 2010 by Bedford/St. Martin's1 Usability relates to five factors of use: ease of learning efficiency of.
Systems Development Lifecycle Analysis. Learning Objectives List the nine stages of the system life cycle Explain the system life cycle as an iterative.
What is systems ? It is a set of components that interact to accomplish some purpose. e.g. human body, business. What is system analysis and design? It.
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Ways of Collecting Information Interviews Questionnaires Ethnography Books and leaflets in the organization Joint Application Design Prototyping.
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 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.
Chapter 10 Fact-finding Techniques 1 © Pearson Education Limited 1995, 2005.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
Interviews By Mr Daniel Hansson.
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.
Designed & developed by E4 SBA SEMESTER ONE SESSION 5 BASICS OF MARKETING- I BASICS OF MARKETING I Session 5 Understanding marketing research.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
1 Administrative Office Management, 8/e by Zane Quible ©2005 Pearson Education, Inc. Pearson Prentice Hall Upper Saddle River, NJ Job Analysis Chapter.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
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 5 Determining System Requirements
MGT-351 Human Resource Management Chapter-04
Essentials of Systems Analysis and Design Fourth Edition
Rekayasa Perangkat Lunak
The Analysis Phase: Gathering Information
Chapter 7 Determining System Requirements
Chapter 4 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Presentation transcript:

System Analysis-Gathering Requirements

 System analysis is the process of gathering info about existing system, which may be computerized or not, while identifying system’s strengths and problems.  Commonly used info gathering techniques are: Interviews Review of document Observation Questionnaires Joint Application Design Prototyping

 Interviews Reveals info about the interviewee opinions about existing system. 4 basic steps in an interview are :-  Read the background materials to establish the interview objectives  Decide who to interview  Prepare the interview  Decide on question type and structure It is a formal face to face meeting between system development team and user

There are two types of interview:  Structured  The interviewer will only ask questions that have been planned and write in advance  Unstructured  The interviewer will ask questions that have been prepared earlier and also other subjects if they seem appropriate Advantages :  Get to meet the person personally and get more info if asked correctly  Reveals what actually being done  Indications of resistance to the proposed system

Disadvantages:  Time consuming to undertake  More costly

 Review of documents Written doc includes manuals, procedures, forms reports etc Copies of documentation should be able for review Reviewing such documentation can reveal about the organization, operation and its existing system It is important to:  Identify a complete list of doc

 Go through them  Analyze  Check for duplication of data to ensure it is not appear under two names By reviewing doc, more effective interviews can be conduct with managers and users.  Observation Allows to gain info that cannot get by other techniques

First hand info can be obtained Direct observation is where system analyst watches the users as they performing their job function It enables us to see the reality situation rather than listening to others Used as supplementary interview info or acts as a signal any extra care to be taken into account

 Questionnaires Are used when there are large number of users The questions should be reasonably straightforward and relatively few to increase the likelihood of response Cheaper and quicker way to interview but difficult to set a clear questions and ensure adequate response rate

Advantages :  Obtain info from large number of people with less time and money Disadvantages :  Info maybe less detailed  Info could be bias if only a few respond to the survey  Joint Application Design Info gathering technique that allows a system dev team, users and mgt to work together in a focused workshop to identify requirements for the system Effective in building user commitment through their participation in analysis of requirements and specifications of systems design Advantages :  It takes shorter time to complete a project  Improves the quality of final system by focusing on up-front SDLC,thus reducing errors

 Prototyping is a model of a proposed system Acts as a communications device between users and system dev team and aid in the learning process Has five main stages :  Agree approximately what is needed  Build something quickly that look like what is wanted  Test it and see if it does what the user wants

 Use it in a representative environment  Adapt and develop the prototype based on the info gained Advantages:  Improve info gathering technique process  Improve relationship between system dev team and user  Better identification of systems problems Disadvantages :  Potential cause of conflict between dept that want different things from the system

 Misunderstanding by end user that actual system can be design and dev at same speed