DocumentCode
2393348
Title
To do or not to do: If the requirements engineering payoff is so good, why aren´ t more companies doing it?
Author
Berry, Daniel M. ; Damian, Daniela ; Finkelstein, A. ; Gause, D. ; Hall, R. ; Simmons, E. ; Wassyng, Alan
Author_Institution
Waterloo Univ., Ont.
fYear
2005
fDate
Aug. 29 2005-Sept. 2 2005
Firstpage
447
Lastpage
447
Abstract
One thing that keeps many software-development organizations from doing serious requirements engineering before beginning development is the perception that doing requirements engineering wastes time and delays getting on to the real work, designing and programming. The first third of this paper presents anecdotal and case study evidence that upfront RE pays off big. The second third is a discussion on structural and cultural barriers to industrial adoption of RE practices. The final third is a free-wheeling discussion on these and related issues
Keywords
social aspects of automation; software development management; systems analysis; cultural barriers; requirements engineering; software development; structural barriers; Cultural differences; Delay effects; Design engineering; Impedance; Productivity; Risk management; Software quality; Software safety; Technology transfer; Testing;
fLanguage
English
Publisher
ieee
Conference_Titel
Requirements Engineering, 2005. Proceedings. 13th IEEE International Conference on
Conference_Location
Paris
Print_ISBN
0-7695-2425-7
Type
conf
DOI
10.1109/RE.2005.74
Filename
1531068
Link To Document