I have worked in the requirements engineering area as a practitioner and also as a researcher. I have observed both obstacles and incentives to adopting new requirements engineering methods. This subject has been explored previously [1] [2], but remains an interesting area for those of us who would like to effect change.Practitioners must often deal with the obstacles associated with introducing new methods, and need help from researchers in convincing their project teams and management to try something new. Researchers, on the other hand, tend to feel that they are done and ready to move on to the next challenge, after they have produced a few journal articles and some prototype tools.Researchers and practitioners seldom work together on projects, so a gulf must be overcome in order for the researchers to understand what is useful to the practitioners, and for the practitioners to understand exactly what benefits can be derived from trying something new.Many of the obstacles and incentives result from the perceptions of researchers, practitioners, and management. Technology transition is successful when these perceptions are brought into alignment, and when the new method supports the needs of all three groups.
[1]
Marcelo Masera,et al.
Requirements engineering and industrial uptake
,
1998,
Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.
[2]
Khaled El Emam,et al.
A field study of requirements engineering practices in information systems development
,
1995,
Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).
[3]
Steve Miller.
How Can Requirements Engineering Research Become Requirements Engineering Practice?
,
1997,
RE.
[4]
David Harel,et al.
Will I be pretty, will I be rich?: some thoughts on theory vs. practice in systems engineering
,
1994,
PODS.