Skip to main content
SpringerLink
Log in

Requirements Evolution From Process to Product Oriented Management

  • Conference paper
  • First Online:
Product Focused Software Process Improvement (PROFES 2001)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 2188))

Abstract

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.

This work has been partially funded by a grant of the Italian National Research Council (CNR) within the thematic Science and Information Technology, Bando n. 203.15.11. Research Program: “Requirements Evolution: Understanding Formally Engineering Processes within Industrial Contexts”.

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

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  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.

    Chapter  Google Scholar 

  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. Stuart Anderson and Massimo Felici. Requirements engineering questionnaire, version 1.0, January 2001.

    Google Scholar 

  4. Barry W. Boehm. Software Engineering Economics. Prentice-Hall, 1981.

    Google Scholar 

  5. Barry W. Boehm. Software engineering economics. IEEE Transaction on Software Engineering, 10(1):4–21, January 1984.

    Article  Google Scholar 

  6. CCTA, editor. Prince2 Manual-Managing successful projects with PRINCE 2. CCTA-Central Computer and Telecommunications Agency, 1998.

    Google Scholar 

  7. DIRC Project. Interdisciplinary research collaboration in dependability of computer-based systems. http://www.dirc.org.uk/.

  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. Tom Gilb and Dorothy Graham. Software Inspection. Addison-Wesley, 1993.

    Google Scholar 

  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. Ivy F. Hooks and Kristin A. Farry. Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. AMACOM, 2001.

    Google Scholar 

  12. IEEE. IEEE Std 982.1-IEEE Standard Dictionary of Measures to Produce Reliable Software, 1988.

    Google Scholar 

  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. M.M. Lehman. Software’s future: Managing evolution. IEEE Software, pages 40–44, Jan–Feb 1998.

    Google Scholar 

  15. Nancy G. Leveson. SAFEWARE: System Safety and Computers. Addison-Wesley, 1995.

    Google Scholar 

  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. Shari Lawrence Pfleeger. Software Engineering: Theory and Practice. Prentice-Hall, 1998.

    Google Scholar 

  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. James Robertson and Suzanne Robertson. Volere: Requirements specification template. Technical Report Edition 6.1, Atlantic Systems Guild, 2000.

    Google Scholar 

  20. Suzanne Robertson and James Robertson. Mastering the Requirements Process. Addison-Wesley, 1999.

    Google Scholar 

  21. RTCA. DO-178B Software Considerations in Airborne Systems and Equipment Certification, 1992.

    Google Scholar 

  22. Ian Sommerville and Pete Sawyer. Requirements Engineering: A Good Practice Guide. John Wiley & Sons, 1997.

    Google Scholar 

  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. Neil Storey. Safety-Critical Computer Systems. Addison-Wesley, 1996.

    Google Scholar 

  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. David M. Weiss and Chi Tau Robert Lai. Software Product-Line Engineering: A Family-Based Software Development Process. Addison-Wesley, 1999.

    Google Scholar 

  27. Karl Eugene Wiegers. Software Requirements. Microsoft Press, 1999.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. LFCS, Division of Informatics, The University of Edinburgh, Mayfiled Road, Edinburgh, EH9 3JZ, UK

    Stuart Anderson & Massimo Felici

Authors
  1. Stuart Anderson
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Massimo Felici
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. Fraunhofer IESE, Sauerwiesen 6, 67661, Kaiserslautern, Germany

    Frank Bomarius

  2. VTT Electronics, P.O. Box 1100, 90571, Oulu, Finland

    Seija Komi-Sirviö

Rights and permissions

Reprints and permissions

Copyright information

© 2001 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Anderson, S., Felici, M. (2001). Requirements Evolution From Process to Product Oriented Management. In: Bomarius, F., Komi-Sirviö, S. (eds) Product Focused Software Process Improvement. PROFES 2001. Lecture Notes in Computer Science, vol 2188. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-44813-6_6

Download citation

  • DOI: https://doi.org/10.1007/3-540-44813-6_6

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-42571-7

  • Online ISBN: 978-3-540-44813-6

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation