Good requirements practices are neither necessary nor sufficient

Requirements Engineering

Volumn 11, Issue 1, 2006, Pages 1-3

  Davis, Alan M ^a   Zowghi, Didar ^b  

^a UNIVERSITY OF COLORADO   (United States)

^b UNIVERSITY OF TECHNOLOGY SYDNEY   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 31044440783     PISSN: 09473602     EISSN: None     Source Type: Journal    
DOI: 10.1007/s00766-004-0206-4     Document Type: Review

References (12)

1. Davis A (2004) Just enough requirements management. Dorset House, New York
2. Gause D, Weinberg J (1989) Exploring requirements: Quality before design. Dorset House, New York
3. Glass R (2002) Searching for the Holy Grail of software engineering. Commun ACM 45(5):15-16. DOI: 10.1145/506218.506231
4. Gottesdiener E (2002) Requirements by collaboration: Workshops for defining needs. Addison Wesley, Reading
5. Hickey A, Davis A (2004) A unified model of requirements elicitation. J Manag Inf Syst 20(4):65-84
6. IEEE Standard 830 (1998) IEEE recommended practice for software requirements specifications. IEEE Computer Society Press, Los Alamitos
7. Laueson S (2002) Software requirements: Styles and techniques. Addison Wesley, Reading
8. Leffingwell D, Widrig D (1999) Managing software requirements - a unified approach. Addison Wesley, New York
9. Robertson J, Robertson S (1999) Mastering the requirements process. Addison Wesley, New York
10. Sommerville I, Sawyer P (1997) Requirements engineering: A good practice guide. Wiley, New York
11. Wiegers K (2003) Software requirements. Microsoft Press, Redmond
12. Young R (2001) Effective requirements practices. Addison Wesley, Reading