Page 77 - Software and Systems Requirements Engineering in Practice

c
i
l
i
n
i
t
e
t
p
r
:
3

m
e
r
e
s
t
n
R

g
e
i
u
q
a
h
C C h a p t e r 3 : E E l i c i t i n g R e q u i r e m e n t s 49 49
Elicitation Analysis
Business Goals Ethnographic Research Survey Techniques Brainstorming Techniques Feature Modeling Prototyping Business Modeling Global Analysis Focus Group Meetings Traditional Requirements Analysis Release Planning
ITERATIVE
FIGURE 3.4 Example elicitation and analysis methods
Eliciting Business Goals
A sometimes overlooked aspect of requirements elicitation is the
determination of business goals. These goals are associated with the
needs of the manufacturing or development organization rather than
the needs of the customer or purchaser. For example, sample business
goals might be
• Increase profitability by 5 percent the next fiscal year.
• Customers should associate our product with high quality.
• Customers should associate our product with best value.
• Our next product should take advantage of emerging
technologies.

One way of visualizing and capturing business goals is a simple
graphical technique known as goal modeling. Two of the more
popular techniques are KAOS [Dardenne et al. 1993] and I* [Yu 1993].
A nice survey of different goal modeling techniques can be found in
the article by van Lamsweerde [van Lamsweerde 2001].
Goal modeling is a nice way to crystallize ideas, to present
corporate goals in a simple-to-understand and unambiguous way,
and to identify and balance difficult choices. In Figure 3.5, we see a
simple goal model fragment, where a plus sign indicates that the
lower-level goal contributes to the higher-level goal, and a minus sign
indicates that the lower-level goal detracts from the higher-level goal.
If the additions and detractions can be quantified, then the selection of