Starting Improvement of Requirements Engineering Processes: An Experience Report

  • Marjo Kauppinen
  • Sari Kujala
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2188)


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.


Requirement Engineering Process Improvement Customer Requirement Requirement Elicitation Requirement Document 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Basili, V., Zelkowitz, M., McGarry, F., Page, J., Waligora, S., Pajerski, R.: SEL’s Software Process-Improvement Program. IEEE Software, Vol. 12, Issue 6 (1995) 83–87CrossRefGoogle Scholar
  2. 2.
    Curtis, B.: Software Process Improvement: Methods and Lessons Learned. Proceedings of the 19th International Conference on Software Engineering (1997) 624–625Google Scholar
  3. 3.
    Davis, A. M., Hsia, P.: Giving Voice To Requirements Engineering. IEEE Software, Vol. 11, Issue 2 (1994) 12–15CrossRefGoogle Scholar
  4. 4.
    Diaz, M., Sligo, J.: How Software Process Improvement Helped Motorola. IEEE Software, Vol. 14, Issue 5 (1997) 75–81CrossRefGoogle Scholar
  5. 5.
    Haley, T.: Software Process Improvement at Raytheon. IEEE Software, Vol. 13, Issue 6 (1996) 33–41CrossRefGoogle Scholar
  6. 6.
    Humprey, W., Snyder, T., Willis, R.: Software Process Improvement at Hughes Aircraft. IEEE Software, Vol. 8, Issue 4 (1991) 11–23CrossRefGoogle Scholar
  7. 7.
    Hutchings, A., Knox, S.: Creating Products Customers Demand. Communications of the ACM, 38 (5) (1995) 72–80CrossRefGoogle Scholar
  8. 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. 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. 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. 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
  12. 12.
    Kamsties, E., Hörmann, K., Schlich, M.: Requirements Engineering in Small and Medium Enterprises. Requirements Engineering, Vol. 3, No. 2 (1998) 84–90CrossRefGoogle Scholar
  13. 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. 14.
    O’Hara, F.: European Experiences with Software Process Improvement. Proceedings of the 22nd International Conference on Software Engineering (2000) 635–640Google Scholar
  15. 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. 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. 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
  18. 18.
    Sommerville, I., Sawyer, P.: Requirements Engineering-A Good Practice Guide. John Wiley & Sons, New York (1997)zbMATHGoogle Scholar
  19. 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. 20.
    Zahran, S.: Software Process Improvement: Practical Guidelines for Business Success. Addison Wesley (1998)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2001

Authors and Affiliations

  • Marjo Kauppinen
    • 1
  • Sari Kujala
    • 1
  1. 1.Software Business and Engineering InstituteHelsinki University of TechnologyHUTFinland

Personalised recommendations