Determining System Requirements Classes 9,10. SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical.

Slides:



Advertisements
Similar presentations
 Interviewing individuals  Interviewing groups  Observing workers  Studying business documents 1.
Advertisements

Investigating and Determining System Requirements
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Determining systems requirements Updated: September 2014.
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.
Systems Requirements 10/4/2010 © Abdou Illia MIS Fall 2010.
Systems Analysis Requirements determination Requirements structuring
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Analysis and Design in a Changing World, Fifth 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
Chapter 6 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.
Requirements Modeling
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 4 Investigating System Requirements
System Analysis and Design 3 rd Lecture اعداد : أ.ساره الحجام.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
BIS 360 – Lecture Five Ch. 7: Determining System Requirements.
Modern Systems Analysis and Design Third Edition
Chapter 6 Determining System Requirements
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.
IS2210: Systems Analysis and Systems Design and Change Twitter:
University of Sunderland Professionalism and Personal Skills Unit 9 Professionalism and Personal Skills Lecture Data Collection.
Ways of Collecting Information Interviews Questionnaires Ethnography Books and leaflets in the organization Joint Application Design Prototyping.
4 Systems Analysis and Design in a Changing World, Fourth Edition.
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.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Psychological Research Methods Psychology: Chapter 2, Section 2.
Centre for Information & Knowledge Management INFORMATION SYSTEMS MANAGEMENT Jamie O’Brien Centre for Information & Knowledge Management University of.
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.
1 Requirements Determination (Analysis) Lecture 3 Courtesy to Dr.Subhasish Dasgupta.
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.
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
Fundamentals of Information Systems, Sixth Edition
Chapter 5 Determining System Requirements
Modern Systems Analysis and Design Third Edition
Chapter 5 Determining System Requirements
Chapter 5 Determining System Requirements
Essentials of Systems Analysis and Design Fourth Edition
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
Public Management Information Systems System Analysis Thursday, August 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

Determining System Requirements Classes 9,10

SDLC Project Identification & Selection Project Initiation & Planning Analysis ** Logical Design Physical Design Implementation Maintenance

Requirements Determination System requirements Functional requirements Current and future functions Current and future data Current and future employee jobs

Requirements Structuring Two essential views of the current and replacement information systems. Both are describing the same system, but in a different way. Process view: The sequence of data movement & handling operations within the system Data flow diagrams Data: The inherent structure of data independent of how or when it is processed Entity-relation diagrams

Remember to...

Who will you get info from? User Stakeholders Users Managers Client Stakeholders Technical Stakeholders

What Information Do You Need?

Traditional Methods for Determining System Requirements Administering questionnaires Interviewing and listening Interviewing groups Directly observing users Analyzing procedures & other documents

Administering Questionnaires Advantages & Disadvantages Strengths Weaknesses

Give Me Ambiguity or Give Me Something Else! How often do you back up your computer files? A. Frequently B. Sometimes C. Hardly at all D. Never

This is better… How often do you back up the computer files stored on the hard disk on the PC you use for over 50% of your work time? A. Frequently (at least once per week) B. Sometimes (from 1 to 3 times per month) C. Hardly at all (once per month or less) D. Never

Interviewing & Listening Before During the interview Afterwards

During the Interview Beginning Introduction, open-ended questions, interest & attention Middle Open & close-ended questions, f-u questions, active listening, provide feedback, limit note- taking End Summarize, request feedback and/or f-u, ask for corrections

Interviews Advantages & Disadvantages Strengths Extracts both qualitative and quantitative data Detailed and summary data Good way to find needs and assumptions Weaknesses Requires skills May be biased; May collect lots of useless data Expensive, time consuming Requires other methods to verify results

How do you choose interview questions? Open-ended questions Closed-ended questions

Find out about someone’s job Write 3 open-ended questions Ask 3 open-ended questions (You may substitute questions during interview.) Write down answers Write 3 closed-ended questions Ask 3 closed-ended questions (You may substitute questions during interview.) Write down answers

Interviewing Groups Adv & Disadv Strengths Not biased by one user’s opinion Can get many user’s opinion Weaknesses With many people present, decision- making takes time Interruptions during process

You May Need to Analyze Work Procedures Work procedures describe a particular job or task May show duplication of effort May find missing steps May contradict info collected from interviews, questionnaires, and observations Formal systems vs informal systems

Directly Observing Users Strengths Doesn’t rely on a user’s memory More objective and accurate than interviews Weaknesses Hawthorne effect Time consuming

Temporary Job Assignment Strengths Good for learning context, terminology, procedures Provides insight for other questions Get operation “feel”; adds to analysts credibility with users Weaknesses Time Consuming May bias future work design towards way things are currently done

Reviewing internal documents Strengths Good way to learn history and politics Explains current context May help understand why and way of current procedures & applications Weaknesses May bias future work design Not useful for obtaining current attitudes or motives

Modern Methods for Determining System Requirements Prototyping Joint Application Design (JAD) - Intensive meetings between users, managers, sponsor, & systems analysts to discuss & review system requirements Group Support Systems (GSS) to share ideas & voice opinions BPR – Business process reengineering CASE tools to analyze existing systems

Structured Walkthroughs What is it? When is it done? Who is involved? How is it done?