This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Understanding the Customer: What Do We Know about Requirements Elicitation?
March/April 2008 (vol. 25 no. 2)
pp. 11-13
ASCII Text
x 
 
Oscar Dieste, Natalia Juristo, Forrest Shull, "Understanding the Customer: What Do We Know about Requirements Elicitation?," IEEE Software, vol. 25, no. 2, pp. 11-13, March/April, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.53,
author = {Oscar Dieste and Natalia Juristo and Forrest Shull},
title = {Understanding the Customer: What Do We Know about Requirements Elicitation?},
journal ={IEEE Software},
volume = {25},
number = {2},
issn = {0740-7459},
year = {2008},
pages = {11-13},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.53},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Understanding the Customer: What Do We Know about Requirements Elicitation?
IS - 2
SN - 0740-7459
SP11
EP13
EPD - 11-13
A1 - Oscar Dieste,
A1 - Natalia Juristo,
A1 - Forrest Shull,
PY - 2008
KW - Requirements elicitation techniques
KW - software requirements
VL - 25
JA - IEEE Software
ER -
 
Oscar Dieste, Madrid Technical University
Natalia Juristo, Madrid Technical University
Forrest Shull, Fraunhofer Center for Experimental Software Engineering, Maryland
"Getting the requirements right" is one of the most important activities in software development, and making a crucial misstep at this phase can easily lead to large amounts of rework. The best way to develop a high-quality system with minimal effort is still to get the requirements right the first time. However, requirements elicitation still relies mainly on the same old proven techniques: interviewing the customer and showing him or her prototypes to get feedback. Has research has provided any clues on how to better accomplish this?

1. E. Kamsties, K. Hormann, and M. Schlich, "Requirements Engineering in Small and Medium Enterprises: State-of-the-Practice, Problems, Solutions, and Technology Transfer," Proc. Conf. European Industrial Requirements Eng. (CEIRE98), British Computer Soc., 1998, pp. 40–50.
2. C.J. Neill and P.A. Laplante, "Requirements Engineering: The State of the Practice," IEEE Software, vol. 20, no. 6, 2003, pp. 40–45.
3. E.F. Fern, "Focus Groups: A Review of Some Contradictory Evidence, Implications, and Suggestions for Future Research," Advances in Consumer Research, vol. 10, no. 1, 1983, pp. 121–126.
4. B. Fischhoff, "Eliciting Knowledge for Analytical Representation," IEEE Trans. Systems, Man, and Cybernetics, vol. 19, no. 3, 1989, pp. 448–461.
5. S. Frankel, "NGT+MDS: An Adaptation of the Nominal Group Technique for Ill-Structured Problems," J. Applied Behavioral Science, vol. 23, no. 4, 1987, pp. 543–551.
6. N.A.M. Maiden and G. Rugg, "ACRE: Selecting Methods for Requirements Acquisition," Software Eng. J., vol. 11, no. 3, 1996, pp. 183–192.

Index Terms:
Requirements elicitation techniques, software requirements
Citation:
Oscar Dieste, Natalia Juristo, Forrest Shull, "Understanding the Customer: What Do We Know about Requirements Elicitation?," IEEE Software, vol. 25, no. 2, pp. 11-13, March-April 2008, doi:10.1109/MS.2008.53
Usage of this product signifies your acceptance of the Terms of Use.