Burt's Bees Case Study

Only available on StudyMode
  • Download(s) : 65
  • Published : March 9, 2013
Open Document
Text Preview
Requirements
Elicitation and Analysis
Author : Lamsweerde (2011), Kotonya, G. &
Sommerville, I. (2003)

Objectives
1. To describe the processes of
requirements elicitation and analysis.
2. To introduce a number of
requirements elicitation and
requirements analysis techniques.
3. To discuss how prototypes may be
used in the RE process.

2

:: Topic ::
Introduction
Requirements Elicitation
Elicitation and Analysis Process
Elicitation techniques
Prototyping
Requirements analysis and
Negotiation




Analysis checklist
Interaction Matrices
Requirements negotiation

Summary

3

:: Introduction ::
 Main activities in RE :
1.

2.
3.
4.
5.

Requirements Elicitation
Requirements Analysis and Negotiation
Requirements Documentation
Requirements Validation
Requirements Management

 Concerns with:






discovering requirements
Analyzing requirements for inconsistency,
incompleteness, relevance, practicality
Elicitation techniques  fact finding techniques

4

:: Introduction ::
 Definition : knowledge transfer process
where requirements engineer elicit and
document existing customer knowledge
 In practice, this process is much more
COMPLEX due to many reasons:






Customers do not have clear picture of their
needs
Different people in organization have conflicting
requirements
Technological constraints etc

 Davis (1993) defined this process as :






activity that encompasses learning about the
problem to be solved,
understanding the needs of potential users,
trying to find out who the user really is, and
understanding all the constraints on the solution.
5

Problems in Elicitation activities


Application domain understanding is not collected
neatly in one location too many sources :
textbooks, manuals, and even heads of the people
involve. Too many specialist term  not
understandable by requirements engineer
People who actually understand the real domain
problem is not usually available, or may not want to
participate
Organizational issues and political factors
Stakeholders often do not really know what they
want from a system except for general terms.









Unrealistic demand  unaware of the costs of their
requests
The same requirements may be expressed differently by
different stakeholders
6

Obstacles to effective knowledge
acquisition

Distributed and conflicting knowledge
sources




Multiple stakeholders
Large volume of data
Maybe conflict with each other: different
priorities and concern, competition among
representatives, outdated docs etc.

Difficult access to sources




Knowledge sources are not easily available
Busy, reluctant to cooperate, suspicious
7

Obstacles to effective knowledge
acquisition

Obstacles to good communication




Communication barriers
Differences in terms of backgrounds,
terminologies, cultures

Tacit knowledge and hidden needs





Implicit information
Hard time explaining their daily routine etc
May have unrealistic expectations

8

Obstacles to effective knowledge
acquisition

Sociopolitical factors


External factors may interfere
 Politics, competition, resistance to change, time,
cost, personal interest etc

Unstable conditions





Organization structure maybe volatile.
Personnel in charge may be transferred to
another department
Priorities may change

9

RE skills
Communication skill





Address the right people
Use the right terminologies
Be able to listen and capture the keypoints

Knowledge reformulation


Information must be properly organized and
structured

10

:: Topic ::
Introduction
Requirements Elicitation
Elicitation and Analysis Process
Elicitation techniques
Prototyping
Requirements analysis and
Negotiation




Analysis checklist
Interaction Matrices
Requirements...
tracking img