Specifying Changes Only – A Case Study on Delta Requirements
[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.
Keywordschange request evolution requirements specification
Unable to display preview. Download preview PDF.
- 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
- 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
- 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
- 13.ISO/IEC: Quality management systems – Guidelines for configuration management – ISO/IEC 10007:2003(E). International Standards Organization ISO (2003)Google Scholar