Chapter 5

Slide 1

Systems Analysis and Systems Analysis and Design with UML Version Design with UML Version 2.0, Second Edition2.0, Second Edition

Alan Dennis, Barbara Wixom, and David Tegarden

Chapter 5: Requirements DeterminationJohn Wiley & Sons, Inc.Copyright 2005

Slide 2

Copyright © 2005 John Wiley & Sons, Inc.

All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.

Slide 3

Requirements Determination

Chapter 5

Slide 4

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 5

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 6

Analysis PhaseThis 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 proposalIncludes revised project management deliverables,

feasibility analysis (Chapter 3) and workplan (Chapter 4).

Slide 7

Requirement Specification

a statement of what the system must do or characteristics it must haveWritten from businessperson perspective (“what” of system)Later requirements become more technical (“how” of system)

Slide 8

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.

Slide 9

Functional Requirements

Slide 10

Nonfunctional Requirements

Slide 11

Requirements Analysis Techniques

Business process automation (BPA)

Doesn’t change basic operations Automates some operations

BPA TechniquesProblem AnalysisRoot Cause Analysis

Slide 12

Business Process Improvement

Business process improvement (BPI) changes

How an organization operatesChanges operation with new techniquesCan improve efficiencyCan improve effectiveness

Slide 13

BPI Components

Duration AnalysisTime to perform each process

Activity-Based CostingExamines major process costs

Informal BenchmarkingStudies how other organizations perform business processes

Slide 14

Business Process Reengineering

Changes how the organization does certain operationsConsists of

Outcome AnalysisTechnology analysis Activity Elimination

Slide 15

Select Appropriate Technique

Assess Potential Business ValueDetermine Project CostSpecify Breadth or Scope of AnalysisDetermine Risk of Failure

Slide 16

Analysis Characteristics

Slide 17

Requirements Gathering

Slide 18

Interviews -- Five Basic Steps

Selecting intervieweesDesigning interview questionsPreparing for the interviewConducting the interviewPost-interview follow-up

Slide 19

Selecting Interviewees

Based on information neededOften good to get different perspectives

ManagersUsersIdeally, all key stakeholders

Slide 20

Types of Questions

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 21

Designing Interview Questions

Unstructured interviewBroad, roughly defined information

Structured interviewMore specific information

Slide 22

Questioning Strategies

Slide 23

Interview Preparation Steps

Prepare general interview planList of questionAnticipated answers and follow-ups

Confirm areas of knowledgeSet priorities in case of time shortagePrepare the interviewee

ScheduleInform of reason for interviewInform of areas of discussion

Slide 24

Conducting the Interview

Appear professional and unbiasedRecord all informationCheck on organizational policy regarding tape recordingBe sure you understand all issues and termsSeparate facts from opinionsGive interviewee time to ask questionsBe sure to thank the intervieweeEnd on time

Slide 25

Conducting the InterviewPractical Tips

Don’t worry, be happyPay attentionSummarize key pointsBe succinctBe honestWatch body language

Slide 26

Post-Interview Follow-Up

Prepare interview notesPrepare interview reportLook for gaps and new questions

Slide 27

Interview Report

INTERVIEW REPORT

Interview notes approved by: ____________

Person interviewed ______________Interviewer _______________Date _______________Primary Purpose:

Summary of Interview:

Open Items:

Detailed Notes:

Slide 28

Your TurnYou are interviewing the director of the PC lab at your school regarding a new program to support keeping track of students’ borrowing software

With a partner, write 5 questions you would ask the PC lab directorTake turns having one pair of students posing the questions to another pair of studentsBe sure to take notes and write up the results when you have finished.

Slide 29

JOINT APPLICATION DESIGN (JAD)

Slide 30

JAD Key Ideas

Allows project managers, users, and developers to work togetherMay reduce scope creep by 50%Avoids requirements being too specific or too vague

Slide 31

Joint Application Design (JAD) Important Roles

Facilitatorsets the meeting agenda and guides the discussion

Scribeassist the facilitator by recording notes, making copies, etc.

Project team, users, and management

Slide 32

Joint Application Design (JAD) Setting

U-Shaped seatingAway from distractionsWhiteboard/flip chartPrototyping toolse-JAD

Slide 33

JAD Meeting Room

JPEG Figure 5-5 Goes Here

Slide 34

The JAD Session

Tend to last 5 to 10 days over a three week periodPrepare questions as with interviewsFormal agenda and groundrulesFacilitator activities

Keep session on trackHelp with technical terms and jargonRecord group inputHelp resolve issues

Post-session follow-up

Slide 35

Managing Problems in JAD Sessions

Reducing dominationEncouraging non-contributorsSide discussionsAgenda merry-go-roundViolent agreementUnresolved conflictTrue conflictUse humor

Slide 36

Questionnaire Steps

Selecting participantsUsing samples of the population

Designing the questionnaireCareful question selection

Administering the questionnaireWorking to get good response rate

Questionnaire follow-upSend results to participants

Slide 37

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 38

Document Analysis

Provides clues about existing “as-is” systemTypical documents

FormsReportsPolicy manuals

Look for user additions to formsLook for unused form elements

Slide 39

Observation

Users/managers often don’t remember everything they doChecks validity of information gathered other waysBehaviors change when people are watchedCareful not to ignore periodic activities

Weekly … Monthly … Annual

Slide 40

Selecting the Appropriate Techniques

Slide 41

Suggest how CD Selections should proceed in eliciting requirements.

Consider steps, techniques and goals, who and how.

Slide 42

How would you identify possible improvements?

What possible improvements would you suggest?

Slide 43

Summary

First Step is to determine requirementsSystems analysts use these techniques

Interviews, JAD, Questionnaires, Document Analysis, and Observation.

Slide 44

Expanding the Domain

Additional resources regarding Joint Application Development can be found at:http://www.carolla.com/wp-jad.htmhttp://www.utexas.edu/hr/is/pubs/jad.html