The Community for Technology Leaders
RSS Icon
Issue No.03 - May/June (2008 vol.25)
pp: 71-77
Jörg Dörr , Fraunhofer Institute for Experimental Software Engineering
Sebastian Adam , Fraunhofer Institute for Experimental Software Engineering
Michael Eisenbarth , Fraunhofer Institute for Experimental Software Engineering
Michael Ehresmann , Insiders Technologies
As enterprises become increasingly aware of requirements engineering's importance, many have been tempted to invest in improving corresponding processes. Unfortunately, many process improvement approaches for requirements engineering don't meet small enterprises' needs and are often hard to apply in small companies. The ReqMan process improvement approach considers small organizations' specific needs by involving employees in the improvement process, enabling them to make improvement decisions rather than having external consultants make the decisions. During the last two years, this approach has been successfully applied in case studies, resulting in strong, positive stakeholder participation in the improvement discussion and high acceptance of the improvements, even by persons who were normally skeptical about improvement activities.
requirements engineering, requirements management, process improvement, best practices
Jörg Dörr, Sebastian Adam, Michael Eisenbarth, Michael Ehresmann, "Implementing Requirements Engineering Processes: Using Cooperative Self-Assessment and Improvement", IEEE Software, vol.25, no. 3, pp. 71-77, May/June 2008, doi:10.1109/MS.2008.63
1. C. Gresse von Wangenheim, A. Anacleto, and C.F. Salviano, "Helping Small Companies Assess Software Processes," IEEE Software, vol. 23, no. 1, 2006, pp. 91–98.
2. N. Juristo, A.M. Moreno, and A. Silva, "Is the European Industry Moving Toward Solving Requirements Problems?" IEEE Software, vol. 19, no. 6, 2002, pp. 70–77.
3. M. Niazi, D. Wilson, and D. Zowghi, "Critical Success Factors for Software Process Improvement Implementation: An Empirical Study," Software Process Improvement and Practice, vol. 11, no. 2, 2006, pp. 193–211.
4. T. Olsson et al., "A Flexible and Pragmatic Requirements Engineering Framework for SME," Proc. 1st Int'l Workshop Situational Requirements Eng. Processes, Univ. of Limerick, 2005, pp. 1–12, 01.pdf.
5. A. Rainer, T. Hall, and N. Baddoo, "Persuading Developers to 'Buy into' Software Process Improvement: Local Opinion and Empirical Evidence," Proc. Int'l Symp. Empirical Software Eng., IEEE CS Press, 2003, pp. 326–335.
6. I. Richardson, "SPI Models: What Characteristics Are Required for Small Software Development Companies?" Software Quality J., vol. 10, no. 2, 2002, pp 101–114.
7. W.E. Deming, Out of the Crisis, MIT Press, 1989.
8. J. Gremba and C. Myers, "The IDEALModel: A Practical Guide for Improvement," Bridge, no. 3, 1997;
4 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool