Understanding the Customer: What Do We Know about Requirements Elicitation?
- 22 February 2008
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 25 (2), 11-13
- https://doi.org/10.1109/ms.2008.53
Abstract
Getting the requirements right is one of the most important activities in software development. Making a crucial misstep at this phase can easily lead to large amounts of rework when the customer simply can't accept a system the way it was developed. When used correctly, approaches such as incremental development or agile methods can mitigate the risks of getting the requirements wrong by making sure that systems are developed in smaller chunks and that each chunk can be shown to the customer for approval. However, the best way to develop a high-quality system with minimal effort is still to get the requirements right the first time.Keywords
This publication has 3 references indexed in Scilit:
- Requirements engineering: The state of the practiceIEEE Software, 2003
- ACRE: selecting methods for requirements acquisitionSoftware Engineering Journal, 1996
- Eliciting knowledge for analytical representationIEEE Transactions on Systems, Man, and Cybernetics, 1989