Requirements Evolution From Process to Product Oriented Management

  • Stuart Anderson
  • Massimo Felici
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2188)


Requirements Evolution represents one of the major problems in developing computer-based systems. Current practice in Requirement Engineering relies on process-oriented methodologies, which lack of product features. The resulting scenario then is a collection of general methodologies, which do not take into account product features that may enhance our ability in monitoring and controlling Requirements Evolution. This paper shows empirical investigations of two industrial case studies. The results point out evolutionary product features and identify an Empirical Framework to analysing Requirements Evolution. This work represents a shift from process to product-oriented management of Requirements Evolution.


Requirement Engineering Smart Card Requirement Engineer Software Requirement Requirement Change 
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.
    Stuart Anderson and Massimo Felici. Controlling requirements evolution: An avionics case study. In Proceedings of SAFECOMP 2000, 19th International Conference on Computer Safety, Reliability and Security, LNCS 1943, pages 361–370, Rotterdam, The Netherlands, October 2000. Springer-Verlag.CrossRefGoogle Scholar
  2. 2.
    Stuart Anderson and Massimo Felici. Requirements changes risk/cost analyses: An avionics case study. In M.P. Cottam, D.W. Harvey, R.P. Pape, and J. Tait, editors, Foresight and Precaution, Proceedings of ESREL 2000, SARS and SRA-EUROPE Annual Conference, volume 2, pages 921–925, Edinburgh, Scotland, United Kingdom, May 2000.Google Scholar
  3. 3.
    Stuart Anderson and Massimo Felici. Requirements engineering questionnaire, version 1.0, January 2001.Google Scholar
  4. 4.
    Barry W. Boehm. Software Engineering Economics. Prentice-Hall, 1981.Google Scholar
  5. 5.
    Barry W. Boehm. Software engineering economics. IEEE Transaction on Software Engineering, 10(1):4–21, January 1984.CrossRefGoogle Scholar
  6. 6.
    CCTA, editor. Prince2 Manual-Managing successful projects with PRINCE 2. CCTA-Central Computer and Telecommunications Agency, 1998.Google Scholar
  7. 7.
    DIRC Project. Interdisciplinary research collaboration in dependability of computer-based systems.
  8. 8.
    Norman E. Fenton and Shari Lawrence Pfleeger. Software Metrics: A Rigorous and Practical Approach. International Thomson Computer Press, second edition, 1996.Google Scholar
  9. 9.
    Tom Gilb and Dorothy Graham. Software Inspection. Addison-Wesley, 1993.Google Scholar
  10. 10.
    Theodore F. Hammer, Leonore L. Huffman, and Linda H. Rosenberg. Doing requirements right the first time. CROSSTALK The Journal of Defense Software Engineering, pages 20–25, December 1998.Google Scholar
  11. 11.
    Ivy F. Hooks and Kristin A. Farry. Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. AMACOM, 2001.Google Scholar
  12. 12.
    IEEE. IEEE Std 982.1-IEEE Standard Dictionary of Measures to Produce Reliable Software, 1988.Google Scholar
  13. 13.
    IEEE. IEEE Std 982.2-IEEE Guide for the Use of IEEE Standard Dictionary of Measures to Produce Reliable Software, 1988.Google Scholar
  14. 14.
    M.M. Lehman. Software’s future: Managing evolution. IEEE Software, pages 40–44, Jan–Feb 1998.Google Scholar
  15. 15.
    Nancy G. Leveson. SAFEWARE: System Safety and Computers. Addison-Wesley, 1995.Google Scholar
  16. 16.
    Mark C. Paulk et al. Key practices of the capability maturity model, version 1.1. Technical Report CMU/SEI-93-025, Software Engineering Institute, Carnegie Mellon University, February 1993.Google Scholar
  17. 17.
    Shari Lawrence Pfleeger. Software Engineering: Theory and Practice. Prentice-Hall, 1998.Google Scholar
  18. 18.
    PROTEUS Project. Meeting the challenge of changing requirements. Deliverable 1.3, Centre for Software Reliability, University of Newcastle upon Tyne, June 1996.Google Scholar
  19. 19.
    James Robertson and Suzanne Robertson. Volere: Requirements specification template. Technical Report Edition 6.1, Atlantic Systems Guild, 2000.Google Scholar
  20. 20.
    Suzanne Robertson and James Robertson. Mastering the Requirements Process. Addison-Wesley, 1999.Google Scholar
  21. 21.
    RTCA. DO-178B Software Considerations in Airborne Systems and Equipment Certification, 1992.Google Scholar
  22. 22.
    Ian Sommerville and Pete Sawyer. Requirements Engineering: A Good Practice Guide. John Wiley & Sons, 1997.Google Scholar
  23. 23.
    George Stark, Al Skillicorn, and Ryan Ameele. An examination of the effects of requirements changes on software releases. CROSSTALK The Journal of Defense Software Engineering, pages 11–16, December 1998.Google Scholar
  24. 24.
    Neil Storey. Safety-Critical Computer Systems. Addison-Wesley, 1996.Google Scholar
  25. 25.
    Axel van Lamsweerde. Requirements engineering in the year 00: A research perspective. In Proceedings of the 2000 International Conference on Software Engineering (ICSE’2000), pages 5–19, Limerick, Ireland, June 2000.Google Scholar
  26. 26.
    David M. Weiss and Chi Tau Robert Lai. Software Product-Line Engineering: A Family-Based Software Development Process. Addison-Wesley, 1999.Google Scholar
  27. 27.
    Karl Eugene Wiegers. Software Requirements. Microsoft Press, 1999.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2001

Authors and Affiliations

  • Stuart Anderson
    • 1
  • Massimo Felici
    • 1
  1. 1.LFCS, Division of InformaticsThe University of EdinburghEdinburghUK

Personalised recommendations