Starting Improvement of Requirements Engineering Processes: An Experience Report
Defining and managing customer requirements is becoming increasingly important in product development. Many software organizations are interested in improving their requirements engineering processes, but they do not know how and where to begin. This report describes the experiences of two Finnish organizations that have started to develop their requirements practices systematically. To guide these development activities, software process improvement procedures and guidelines published in the literature were adjusted and applied. The most important lesson learned was that introducing requirements engineering can require a change of culture and not merely a change of process and technology. The change of culture firstly requires that product development personnel fully understand the reasons for documenting requirements from a customer’s point of view. Secondly, they must commit to defining and managing customer requirements systematically.
KeywordsRequirement Engineering Process Improvement Customer Requirement Requirement Elicitation Requirement Document
Unable to display preview. Download preview PDF.
- 2.Curtis, B.: Software Process Improvement: Methods and Lessons Learned. Proceedings of the 19th International Conference on Software Engineering (1997) 624–625Google Scholar
- 8.Information technology-Software process assessment-Part 7: Guide for use in process improvement, Technical report, ISO/IEC TR 15504-7:1998(E) (1998)Google Scholar
- 9.Jacobs, S.: Introducing Measurable Quality Requirements: A Case Study. Proceedings of the 4th IEEE International Symposium on Requirements Engineering (1999) 172–179Google Scholar
- 10.Johnson, A.: Software Process Improvement Experience in the DP/MIS Function: Experience Report. Proceedings of the 16th International Conference on Software Engineering (1994) 323–329Google Scholar
- 11.McFeeley, B.: IDEAL: A User’s Guide for Software Process Improvement. Handbook CMU/SEI-96-HB-001. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PE, USA (1996)Google Scholar
- 13.Kautz, K., Hansen, H., Thaysen, K.: Applying and Adjusting a Software Process Improvement Model in Practice: The Use of the IDEAL Model in a Small Software Enterprise. Proceedings of the 22nd International Conference on Software Engineering (2000) 626–633Google Scholar
- 14.O’Hara, F.: European Experiences with Software Process Improvement. Proceedings of the 22nd International Conference on Software Engineering (2000) 635–640Google Scholar
- 15.Paulk, M. et al.: The Capability Maturity Model: Guidelines for Improving the Software Process. Carnegie Mellon University, Software Engineering Institute, Addison Wesley Longman, Reading, Massachusetts (1997)Google Scholar
- 16.Sakamoto, K., Nokakoji, K., Takagi, Y.: Toward Computational Support for Software Process Improvement Activities. Proceedings of the 20th International Conference on Software Engineering (1998) 22–31Google Scholar
- 17.Sawyer, P., Sommerville, I., Kotonya, G.: Improving Market-Driven RE Processes. Proceedings of International Conference on Product Focused Software Process Improvement (PROFES’99), Oulu Finland (1999) 222–236Google Scholar
- 19.Tanaka, T., Sakamoto, K., Kusumoto, S., Matsumoto, K., Kikuno, T.: Improvement of Software Process by Process Description and Benefit Estimation. Proceedings of the 17th International Conference on Software Engineering, pp. 123–132, 1995.Google Scholar
- 20.Zahran, S.: Software Process Improvement: Practical Guidelines for Business Success. Addison Wesley (1998)Google Scholar