Top Banner
Slide 1 Requirement Analysis
39
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Requirements analysis

Slide 1

Requirement Analysis

Page 2: Requirements analysis

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.

Page 3: Requirements analysis

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.

Page 4: Requirements analysis

Slide 4

Analysis PhaseThis phase takes the general ideas in the system request and

refines them into a detailed requirements definition, functional models, structural models, and behavioral models

This becomes the system proposalIncludes revised project management deliverables,

feasibility analysis and work plan .

Page 5: Requirements analysis

Slide 5

Requirement Specification

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

Page 6: Requirements analysis

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.

Page 7: Requirements analysis

Nonfunctional Requirements

Slide 7

Page 8: Requirements analysis

Slide 8

Functional Requirements

Page 9: Requirements analysis

Slide 9

Nonfunctional Requirements

Page 10: Requirements analysis

Steps of analysis

Understand the as-is systemIdentify improvementsDevelop requirements for the to-be system

Slide 10

Page 11: Requirements analysis

Slide 11

Requirements Analysis Techniques

Business process automation (BPA)

Doesn’t change basic operations Automates some operations

BPA TechniquesProblem AnalysisRoot Cause Analysis

Page 12: Requirements analysis

Slide 12

Business Process Improvement

Business process improvement (BPI) changes

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

Page 13: Requirements analysis

Slide 13

BPI Components

Duration AnalysisTime to perform each process

Activity-Based CostingExamines major process costs

Informal BenchmarkingStudies how other organizations perform business processes

Page 14: Requirements analysis

Slide 14

Business Process Reengineering

Changes how the organization does certain operationsConsists of

Outcome AnalysisTechnology analysis Activity Elimination

Page 15: Requirements analysis

Slide 15

Select Appropriate Technique

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

Page 16: Requirements analysis

Slide 16

Analysis Characteristics

Page 17: Requirements analysis

Slide 17

Requirements Gathering

Page 18: Requirements analysis

Slide 18

Interviews -- Five Basic Steps

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

Page 19: Requirements analysis

Slide 19

Selecting Interviewees

Based on information neededOften good to get different perspectives

ManagersUsersIdeally, all key stakeholders

Page 20: Requirements analysis

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?

Page 21: Requirements analysis

Slide 21

Designing Interview Questions

Unstructured interviewBroad, roughly defined information

Structured interviewMore specific information

Page 22: Requirements analysis

Slide 22

Questioning Strategies

Page 23: Requirements analysis

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

Page 24: Requirements analysis

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

Page 25: Requirements analysis

Slide 25

Conducting the InterviewPractical Tips

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

Page 26: Requirements analysis

Slide 26

Post-Interview Follow-Up

Prepare interview notesPrepare interview reportLook for gaps and new questions

Page 27: Requirements analysis

Slide 27

Interview Report

INTERVIEW REPORT

Interview notes approved by: ____________

Person interviewed ______________Interviewer _______________Date _______________Primary Purpose:

Summary of Interview:

Open Items:

Detailed Notes:

Page 28: Requirements analysis

Slide 28

JOINT APPLICATION DESIGN (JAD)

Page 29: Requirements analysis

Slide 29

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

Page 30: Requirements analysis

Slide 30

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

Page 31: Requirements analysis

Slide 31

Joint Application Design (JAD) Setting

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

Page 32: Requirements analysis

Slide 32

JAD Meeting Room

JPEG Figure 5-5 Goes Here

Page 33: Requirements analysis

Slide 33

The JAD Session

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

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

Post-session follow-up

Page 34: Requirements analysis

Slide 34

Managing Problems in JAD Sessions

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

Page 35: Requirements analysis

Slide 35

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

Page 36: Requirements analysis

Slide 36

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

Page 37: Requirements analysis

Slide 37

Selecting the Appropriate Techniques

Page 38: Requirements analysis

Slide 38

Summary

First Step is to determine requirementsSystems analysts use these techniques

InterviewsJADQuestionnaires

Page 39: Requirements analysis

Slide 39

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