Skip to main content

Specifying Changes Only – A Case Study on Delta Requirements

  • Conference paper
Requirements Engineering: Foundation for Software Quality (REFSQ 2009)

Abstract

[Context and motivation] Requirements engineering methods and examples presented in textbooks and scientific publications usually treat software which is developed - and therefore specified - from scratch. However, in the software development practice, this situation is very rare. In an industry case study, we encountered the situation that a software system in use had to be enhanced by a small delta. [Question/problem] Our objective was to specify these delta requirements without having to describe the complete system in detail. Therefore we explored how much of the existing system had to be specified in order to make the delta requirements understandable. [Principal ideas/results] We made an intensive literature search to proven practices. As we were not successful we applied the requirements engineering method TORE and extended it to capture the delta requirements. [Contribution] In this paper we describe a process for capturing delta requirements. To our knowledge, this is the first work about this practically relevant question. In our case study, hierarchical refinement of requirements top-down and iterative requirements prioritization successfully supported the specification of deltas, combined with a high-level specification of the existing system. We also present our experiences during the case study and propose ideas for further research.

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

Access this chapter

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. Dutoit, A.H., Paech, B.: Developing Guidance and Tool Support for Rationale-based Use Case Specification. In: REFSQ - Workshop on Requirements Engineering for Software Quality, Foundations for Software Quality, pp. 85–100. Springer, Heidelberg (2001)

    Google Scholar 

  2. Kiedaisch, F., Pohl, M., Weisbrod, J., Bauer, S., Ortmann, S.: Requirements archaeology: from unstructured information to high quality specifications [in the automotive industry]. In: Fifth IEEE International Symposium on Requirements Engineering, pp. 304–305 (2001)

    Google Scholar 

  3. Finnegan, R.: Requirements engineering methodologies for COTS systems. In: IEEE International Conference on Electro/Information Technology EIT, pp. 475–481 (2008)

    Google Scholar 

  4. Paech, B., Kohler, K.: Task-driven Requirements in object-oriented Development. In: Leite, J., Doorn, J. (eds.) Perspectives on RE. Kluwer Academic Publishers, Dordrecht (2003)

    Google Scholar 

  5. Boehm, B.: Requirements that handle IKIWISI, COTS, and rapid change. IEEE Computer 33(7), 99–102 (2000)

    Article  Google Scholar 

  6. Palmer, S.R., Felsing, J.M.: A Practical Guide to Feature-Driven Development. The Coad Series. Prentice Hall PTR, Upper Saddle River (2002)

    Google Scholar 

  7. Beck, K.: Extreme programming explained. Addison-Wesley, Upper Saddle River (2000)

    Google Scholar 

  8. Nejmeh, B., Thomas, I.: Business-Driven Product Planning Using Feature Vectors and Increments. IEEE Software 19(6), 34–42 (2002)

    Article  Google Scholar 

  9. Zhang, W., Mei, H., Zhao, H.: Feature-driven requirement dependency analysis and high-level software design. Requirements Engineering Journal 11(3), 205–220 (2006)

    Article  Google Scholar 

  10. Davis, A.M.: The Art of Requirements Triage. IEEE Computer 36(3), 42-49 (2003)

    Google Scholar 

  11. Denne, M., Cleland-Huang, J.: Software by Numbers: Low-Risk, High-Return Development. Prentice-Hall, Upper Saddle River (2003)

    Google Scholar 

  12. Denne, M., Cleland-Huang, J.: The incremental funding method: data-driven software development. IEEE Software 21(3), 39–47 (2004)

    Article  Google Scholar 

  13. ISO/IEC: Quality management systems – Guidelines for configuration management – ISO/IEC 10007:2003(E). International Standards Organization ISO (2003)

    Google Scholar 

  14. Unicase, https://teambruegge.informatik.tu-muenchen.de/groups/unicase/

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Herrmann, A., Wallnöfer, A., Paech, B. (2009). Specifying Changes Only – A Case Study on Delta Requirements. In: Glinz, M., Heymans, P. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2009. Lecture Notes in Computer Science, vol 5512. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-02050-6_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-02050-6_5

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-02049-0

  • Online ISBN: 978-3-642-02050-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics