1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.

Slides:



Advertisements
Similar presentations
Fact-finding Techniques Transparencies
Advertisements

Fact Finding Techniques
SEM A – Marketing Information Management
2.06 Understand data-collection methods to evaluate their appropriateness for the research problem/issue.
Indira Gandhi National Open University presents. A Video Lecture Course; System Analysis.
Primary and Secondary Data
Karolina Muszyńska Based on
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 5.1.
Topics: Interviewing Question Type Interviewing techniques
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Lesson 17 Requirements Discovery
1 Pertemuan 18 Penemuan Fakta Matakuliah: >/ > Tahun: > Versi: >
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.
Karolina Muszyńska Based on
© Pearson Education Limited, Chapter 6 Fact-finding Transparencies.
Chapter 5 Determining System Requirements
Chapter 4: Beginning the Analysis: Investigating System Requirements
Chapter 29 conducting marketing research Section 29.1
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
CSC271 Database Systems Lecture # 20.
Chapter 4: Beginning the Analysis: Investigating System Requirements
Business and Management Research
The Market Research Process
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 33 Conducting Marketing Research. The Marketing Research Process 1. Define the Problem 2. Obtaining Data 3. Analyze Data 4. Rec. Solutions 5.
Fact-Finding Techniques for Requirements Discovery
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
PRJ566 Project Planning and Management
BIS 360 – Lecture Five Ch. 7: Determining System Requirements.
Modern Systems Analysis and Design Third Edition
Data Collection Methods
There are many occasions for fact-finding during the database system development lifecycle. fact-finding is particularly crucial to the early stages of.
Team-Based Development ISYS321 Determining Object- Oriented Systems Requirements.
1 Chapter 10 Fact-Finding Techniques Transparencies.
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.
8/29/2012ISC 329 Isabelle Bichindaritz1 Database Application Example The Dreamhome.
Database Analysis and the DreamHome Case Study
Database Analysis Fact-finding techniques
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.
1 Fact-Finding Techniques. 2 u Critical to capture necessary facts to build the required database application. u These facts are captured using fact-finding.
Chapter 10 Fact-finding Techniques 1 © Pearson Education Limited 1995, 2005.
1 Fact-finding Techniques © Pearson Education Limited 1995, 2005.
Facilitate Group Learning
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.
Questionnaires Justine Ruan Jonathan Shiraki. What are Questionnaires? A document that allows the analyst to collect information and opinions from respondents.
6-1 Functional vs. Nonfunctional Requirements Functional requirement - something the information system must do Nonfunctional requirement - a property.
6-1 Objectives Define system requirements and differentiate between functional and nonfunctional requirements. Understand the activity of problem analysis.
THE MARKETING RESEARCH PROCESS CHAPTER 29 Mrs. Simone Seaton Marketing Management.
Fact Finding (Capturing Requirements) Systems Development.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Chapter 5 Determining System Requirements
TIM 58 Chapter 3: Requirements Determination
2.06 Understand data-collection methods to evaluate their appropriateness for the research problem/issue.
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
Chapter 7 Determining System Requirements
REQUIRED DISCOVERY PART II
Chapter 4 Determining System Requirements
2.06 Understand data-collection methods to evaluate their appropriateness for the research problem/issue.
Presentation transcript:

1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design

Problem Definition 2 Identifying Requirements – Most important factors in building correct systems is to first clearly define what the system must do – Requirements may be Functional Nonfunctional Example : Library system Functional- borrowing books, returning process Non functional- security level, interface

Requirements elicitation 3 Requirements elicitation is the process of identifying the sources of requirements for a new system and obtaining those requirements from those sources.

Requirement discovery methods (fact finding ) 4 It is the formal process of using techniques to collect information about systems requirements Methods 1.Sampling of existing documents 2.Research and site visits 3.Observations of the work environment 4.Questionnaires 5.Interviews 6.Joint requirements planning 7.Brainstorming

1. Sampling of existing documents 5 You can get good idea by studying existing – Documents – Forms – files

Documents 6 Documents that describe the problem – Inter office memo – Mints of meeting – Customer complain – Accounting records Document that describe business functions – Company mission statements – Objective of the organization Documents that describe previous studies – Feasibility report

2. Research and site visits 7 Good Source of information Computer Trade Journals Internet Intranet Reference books Word wide Web

3. Observations of the work environment 8 System Analyst participates in or watches a person perform activities to learn about the system. Advantages – Highly reliable. – Relatively inexpensive Disadvantages – People usually feel uncomfortable when being watched

4. Questionnaires 9 Questionnaires are special purpose documents that allow the analysts to collect information and opinions from a large audience. Advantages – Most questionnaires Can be answered quickly. – Allow individuals to maintain anonymity. – Relatively inexpensive way of gathering data. – Responses can be tabulated and analyzed quickly etc.

Questionnaires…. 10 Disadvantages – Number of responses is often low. – No guarantee that an individual will answer or expand on all the questions – Difficult to prepare

Type of questionnaires 11 1.Free-format: – A question is asked, and the respondent records the answer in the space provided after the question. – Eg: What additional reports would you require from the system?…………………………………………………………………………… 1.Fixed-format: – Contains questions that required specific responses from individuals.

Three type of fixed-format questions 12 1)Yes /No Questions E.g: Do you print reports from the existing system? Yes No 2) Multiple choice questions E.g.: How many new clients do you obtain in a year? (Please tick one box only) a) ) Rating questions E.g: How satisfied are you with the response time of the stock update? 1) Very Satisfied 2) Satisfied 3) Dissatisfied 4) Very dissatisfied

5. Interviews 13 System Analyst collects information from individuals face to face. Advantages – Gives the analyst an opportunity to motivate the interviewee to respond freely and openly to questions. – Allow the analyst to look for more feedback from the interviewee. – Permit the analyst to ask questions from each individuals. – New ideas may arise

5. Interviews…. 14 Disadvantages – Very time consuming. Therefore costly approach. – Depend on analyst ‘s human relations skill. Types of Interviews – Unstructured interviews – Structured interviews Types of interview questions – Open ended – Closed ended

How to conduct an interview? 15 Select interviewees Prepare an interview guide – Use clear and concise language. – Don’t include your opinion as part of a question. – Avoid long and complex question – Avoid threatening questions – verify before you leave

6.Joint requirements planning 16 Highly structured group meeting are conducted to analyze problems and define requirements. JRP is a subset of a more comprehensive joint application development or JAD technique.

7. Brainstorming 17 Brainstorming sessions are used to let the stakeholders come up with creative ideas or new approaches to a problem

Step by Step 18 1.Define your problem or issue as a creative challenge. A well designed creative challenge generates the best ideas to solve your problem. 2.Give yourselves a time limit. We recommend around 25 minutes, but experience will show how much time is required. 3.Once the brainstorming starts, participants shout out solutions to the problem while the facilitator writes them down – usually on a white board or flip-chart for all to see. 4.Once your time is up, select the five ideas which you like best. 5.Write down about five criteria for judging which ideas best solve your problem. Criteria should start with the word "should", 6.Give each idea a score of 0 to 5 points depending on how well it meets each criterion. 7.The idea with the highest score will best solve your problem.

19