Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.

Slides:



Advertisements
Similar presentations
Fact Finding Techniques
Advertisements

Chapter 3: Requirements Determination
Systems Analysis and Design with UML Version 2.0, Second Edition
Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.
© 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.
IS 421 Information Systems Analysis James Nowotarski 30 September 2002.
Requirements Gathering
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Systems Analysis Requirements determination Requirements structuring
Gathering Information and Use Case Scenarios
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Jump to first page Chapter 2 System Analysis - Determining System Requirements.
Requirements Gathering. Adapted from PowerPoint Presentation for Dennis, Wixom & Tegardem, Systems Analysis and Design, John Wiley & Sons, Inc. For CSU’s.
Chapter 5 Determining System Requirements
Fact-Finding Fact-Finding Overview
Lesson 18 Requirements Discovery(2)
The chapter will address the following questions:
Slide 1 IS6112 – Application Modelling and Design.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
5-1 © Prentice Hall, 2007 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
Systems Analysis and Design with UML Version 2.0, Second Edition
Chapter 6 Determining System Requirements
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
Requirement Gathering Fall 2006/1385 Semester 1 Sharif Univ. of Tech.2 Sources Gather information on what system should do from many sources –Users –Reports.
The Analysis Phase: Gathering Information. The Analysis Phase The “ Analysis Phase ” answers the questions of who will use the system, what the system.
PRJ566 Project Planning and Management
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Requirements Gathering Chapter 5 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by Solomon Negash.
BIS 360 – Lecture Five Ch. 7: Determining System Requirements.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
ZEIT2301 Design of Information Systems Requirements Gathering
SYSTEM ANALYSIS Chapter 5.
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
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
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.
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:
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.
Slide 1 Requirements Analysis - What is a Requirement? - Business requirements -> System requirements - Functional Requirements: _______________ - Nonfunctional.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination.
4 - 1 Systems Analysis and Design, 2 nd Edition Alan Dennis and Barbara Haley Wixom John Wiley & Sons, Inc. Slides by Roberta M. Roth University of Northern.
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.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
SYSTEM ANALYSIS AND DESIGN SAFAA S.Y. DALLOUL. REQUIREMENT DETERMINATION.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Requirements Determination
Requirements Determination
Systems Analysis and Design 3rd Edition
TIM 58 Chapter 3, continued: Requirements Determination Ch
Requirements Determination
Rekayasa Perangkat Lunak Part-14
Systems Analysis and Design with UML Version 2.0, Second Edition
TIM 58 Chapter 3: Requirements Determination
Systems Analysis and Design
Essentials of Systems Analysis and Design Fourth Edition
Rekayasa Perangkat Lunak
Chapter 7 Determining System Requirements
Presentation transcript:

Slide 1 Requirements Determination Chapter 5

Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements analysis techniques. ■ Understand when to use each requirements analysis technique. ■ Understand how to gather requirements using interviews, JAD sessions, questionnaires, document analysis, and observation. ■ Understand when to use each requirements- gathering technique.

Slide 3 Key Ideas The goal of the analysis phase is to truly understand the requirements of the new system and develop a system that addresses them. The first challenge is collecting and integrating the information The second challenge is finding the right people to participate.

Slide 4 Analysis Phase This phase takes the general ideas in the system request and refines them into a detailed requirements definition (this chapter), functional models (Chapter 6), structural models (Chapter 7), and behavioral models (Chapter 8) This becomes the system proposal Includes revised project management deliverables,  feasibility analysis (Chapter 3) and  workplan (Chapter 4).

Slide 5 Requirement Specification a statement of what the system must do or characteristics it must have Written from businessperson perspective – business requirement Later requirements become more technical – system requirement

Slide 6 Functional vs. Nonfunctional A functional requirement relates directly to a process the system has to perform or information it needs to contain. Nonfunctional requirements refer to behavioral properties that the system must have, such as performance and usability.

Nonfunctional Requirements Slide 7

Slide 8 Functional Requirements

Slide 9 Nonfunctional Requirements

Steps of analysis Understand the as-is system Identify improvements Develop requirements for the to-be system Slide 10

Slide 11 Requirements Gathering Interviews

Slide 12 Interviews -- Five Basic Steps Selecting interviewees Designing interview questions Preparing for the interview Conducting the interview Post-interview follow-up

Slide 13 Selecting Interviewees Based on information needed Often good to get different perspectives Managers Users Ideally, all key stakeholders

Slide 14 Types of Questions Examples Closed-Ended Questions* How many telephone orders are received per day? * How do customers place orders? * What additional information would you like the new system to provide? Open-Ended Questions* What do you think about the current system? * What are some of the problems you face on a daily basis? * How do you decide what types of marketing campaign to run? Probing Questions* Why? * Can you give me an example? * Can you explain that in a bit more detail?

Slide 15 Designing Interview Questions Unstructured interview Broad, roughly defined information Structured interview More specific information

Slide 16 Questioning Strategies

Slide 17 Interview Preparation Steps Prepare general interview plan List of question Anticipated answers and follow-ups Confirm areas of knowledge Set priorities in case of time shortage Prepare the interviewee Schedule Inform of reason for interview Inform of areas of discussion

Slide 18 Conducting the Interview Appear professional and unbiased Record all information Check on organizational policy regarding tape recording Be sure you understand all issues and terms Separate facts from opinions Give interviewee time to ask questions Be sure to thank the interviewee End on time

Slide 19 Conducting the Interview Practical Tips Don’t worry, be happy Pay attention Summarize key points Be succinct Be honest Watch body language

Slide 20 Post-Interview Follow-Up Prepare interview notes Prepare interview report Look for gaps and new questions

Slide 21 Interview Report INTERVIEW REPORT Interview notes approved by: ____________ Person interviewed ______________ Interviewer _______________ Date _______________ Primary Purpose: Summary of Interview: Open Items: Detailed Notes:

Sample Interview Report Slide 22

Slide 23 JOINT APPLICATION DESIGN (JAD)

Slide 24 JAD Key Ideas Allows project managers, users, and developers to work together May reduce scope creep by 50% Avoids requirements being too specific or too vague

Slide 25 Joint Application Design (JAD) Important Roles Facilitator sets the meeting agenda and guides the discussion Scribe assist the facilitator by recording notes, making copies, etc. Project team, users, and management

Slide 26 Joint Application Design (JAD) Setting U-Shaped seating Away from distractions Whiteboard/flip chart Prototyping tools e-JAD

Slide 27 JAD Meeting Room JPEG Figure 5-5 Goes Here

Slide 28 The JAD Session Tend to last 5 to 10 days over a three week period Prepare questions as with interviews Formal agenda and groundrules Facilitator activities Keep session on track Help with technical terms and jargon Record group input Help resolve issues Post-session follow-up

Slide 29 Managing Problems in JAD Sessions Reducing domination Encouraging non-contributors Side discussions Agenda merry-go-round Violent agreement Unresolved conflict True conflict Use humor

Slide 30 Questionnaires

Slide 31 Questionnaire Steps Selecting participants Using samples of the population Designing the questionnaire Careful question selection Administering the questionnaire Working to get good response rate Questionnaire follow-up Send results to participants

Slide 32 Good Questionaire Design Begin with nonthreatening and interesting questions. Group items into logically coherent sections. Do not put important items at the very end of the questionnaire. Do not crowd a page with too many items. Avoid abbreviations. Avoid biased or suggestive items or terms. Number questions to avoid confusion. Pretest the questionnaire to identify confusing questions. Provide anonymity to respondents.

Slide 33 Selecting the Appropriate Techniques

Slide 34 Summary First Step is to determine requirements Systems analysts use these techniques Interviews JAD Questionnaires