Slide 1 Systems Analysis and Design with UML Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden Chapter 5: Requirements Determination John Wiley.

Slide 1

Systems Analysis and Design with UML Version 2.0

Alan Dennis, Barbara Wixom, and David Tegarden

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

Requirements Determination

Chapter 5

Slide 2

Slide 3

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 4

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 5

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 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.

Slide 7

Functional Requirements

Slide 8

Nonfunctional Requirements

Slide 9

Requirements Gathering

Interviews -- Five Basic Steps

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

Slide 10

Slide 11

Selecting Interviewees

Based on information neededOften good to get different perspectives

ManagersUsersIdeally, all key stakeholders

Slide 12

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 13

Designing Interview Questions

Unstructured interviewBroad, roughly defined information

Structured interviewMore specific information

Slide 14

Questioning Strategies

Slide 15

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 16

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 17

Conducting the InterviewPractical Tips

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

Slide 18

Post-Interview Follow-Up

Prepare interview notesPrepare interview reportLook for gaps and new questions

Slide 19

Interview Report

INTERVIEW REPORT

Interview notes approved by: ____________

Person interviewed ______________Interviewer _______________Date _______________Primary Purpose:

Summary of Interview:

Open Items:

Detailed Notes:

Slide 20

JOINT APPLICATION DESIGN (JAD)

Slide 21

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 22

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 23

Joint Application Design (JAD) Setting

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

Slide 24

JAD Meeting Room

JPEG Figure 5-5 Goes Here

Slide 25

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 26

Managing Problems in JAD Sessions

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

Slide 27

Document Analysis

Provides clues about existing “as-is” systemTypical documents

FormsReportsPolicy manuals

Look for user additions to formsLook for unused form elements

Slide 28

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 29

Selecting the Appropriate Techniques