Page 100 - Software and Systems Requirements Engineering in Practice

70 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e

FIGURE 3.14 Sit down
Facilitation skills and shut
are important. up!

problems described in this chapter. Furthermore, being a project lead
analyst or facilitator is an art in itself, requiring the ability to get
diverse stakeholders to follow an agenda without deviation, and
drive the elicitation process smoothly to completion in the allotted
time (Figure 3.14).

3.11 Discussion Questions

1. When and how should stakeholder requests be reviewed?
2. How large should a requirements elicitation session
meeting be?
3. What are some of the differences between a brainstorming
session and a requirements elicitation session?

References
Agar, M., Professional Stranger: An Informal Introduction to Ethnography, 2nd ed.,
Academic Press, 1996.
Akao, Y., Quality Function Deployment: Integrating Customer Requirements into Product
Design, Productivity Press, 1990.
Beck, K., Extreme Programming Explained, Addison-Wesley, 1999.
Berry, D., “The Importance of Ignorance in Requirements Engineering,” Journal of
Systems and Software, Vol. 28, No. 2, February 1995, pp. 179–184.
Brooks, F.P., Jr., The Mythical Man-Month: Essays on Software Engineering, Anniversary
Edition, Addison Wesley, 1995.
Carlson, P., “The Flop Heard Round the World,” Washington Post, September 4,
2007.
Clegg, B., and Birch, P., Instant Creativity: Simple Techniques to Ignite Innovation &
Problem Solving, Kogan Page, 2007.
Cleland-Huang, J., “Toward Improved Traceability of Non-Functional
Requirements,” International Workshop on Traceability in Emerging Forms of
Software Engineering, Long Beach, CA, November 2005. (In conjunction with
ASE’05.)
Conway Correll, L., Brainstorming Reinvented: A Corporate Communications Guide to
Ideation, Response Books, 2004.
Dardenne, A., van Lamsweerde, A., and Fickas, S., “Goal-Directed Requirements
Acquisition,” in IWSSD: Selected Papers of the Sixth International Workshop on
Software Specification and Design, 1993, pp. 3–50.