Skip to main content
Log in

A market-driven requirements engineering process: Results from an industrial process improvement programme

  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

In market-driven software evolution, the objective of a requirements engineering process include the envisioning and fostering of new requirements on existing packaged software products in a way that ensures competitiveness in the marketplace. This paper describes an industrial, market-driven requirements engineering process which incorporates continuous requirements elicitation and prioritisation together with expert cost estimation as a basis for release planning. The company has gained a measurable improvement in delivery precision and product quality of their packaged software. The described process will act as a baseline against which promising new techniques can be evaluated in the continuation of the improvement programme.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. Specification and Description Language (SDL). ITU-T Standard Z. 100. International Telecommunication Union, 1992

  2. Message Sequence Chart (MSC). ITU-T Recommendation Z. 120. International Telecommunication Union, 1996

  3. Tree and Tabular Combined Notation (TTCN). ISO/IEC Recommendation 9646-3. International Standardization Organization, 1992

  4. Fowler M, Scott K. UML distilled: applying the standard object modelling language. Addison-Wesley, Reading, MA, 1997

    Google Scholar 

  5. Shaw M, Garlan D. Software architecture: perspectives on an emerging discipline. Prentice-Hall, Englewood Cliffs, NJ, 1996

    MATH  Google Scholar 

  6. Sommerville I, Sawyer P. Requirements engineering: a good practice guide. Wiley, New York, 1997

    MATH  Google Scholar 

  7. Humphrey WS. Managing the software process. Addison-Wesley, Reading, MA, 1989

    Google Scholar 

  8. Regnell B, Andersson M, Bergstrand J. A hierarchical use case model with graphical representation. In: IEEE international symposium and workshop on engineering of computer-based systems, Germany, March 1996

  9. Wohlin C, Gustavsson A, Höst M, Mattsson C. A framework for technology introduction in software organizations. In: International conference on software process improvement, Brighton, UK, 1996

  10. Regnell B, Kimbler K, Wesslén A. Improving the use case driven approach to requirements engineering. In: IEEE second international symposium on requirements engineering, York, UK, March 1995

  11. Regnell B. Hierarchical use case modelling for requirements engineering. Licentiate thesis no. 120, Department of Communication Systems, Lund University, Sweden, 1996

    Google Scholar 

  12. Karlsson J, Ryan K. A cost-value approach for prioritizing requirements. IEEE Software 1997; September/October

  13. Karlsson J. A systematic approach for prioritizing software requirements. Doctoral disertation no. 526, Dept. of Computer and Information Science, Linköping University, Sweden, 1998

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Björn Regnell.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Regnell, B., Beremark, P. & Eklundh, O. A market-driven requirements engineering process: Results from an industrial process improvement programme. Requirements Eng 3, 121–129 (1998). https://doi.org/10.1007/BF02919972

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF02919972

Keywords

Navigation