Managing requirements evolution and change

Part of the IFIP Advances in Information and Communication Technology book series (IFIPAICT)


Requirements evolve, not only during system development but also after a system has been installed. This paper discusses our work on defining a systematic approach for managing change at the requirements level. We present a meta-model for change concepts, which is used to underpin a proposed process for change management. Related work is discussed and the paper concludes by delineating the issues in requirements evolution that have emerged so far from our work.


Software evolution requirements evolution change management 


  1. Arnold, R., and Bohner, S., Eds. (1996). Software change impact analysis, IEEE Computer Society Press.Google Scholar
  2. Bennett, K. (1996). Software evolution: past, present and future, Information and Software Technology, 38: 673–680.CrossRefGoogle Scholar
  3. Charette, R.,, Adams, K., and White, M. (1997). Managing risk in software maintenance, IEEE Software, May-June.Google Scholar
  4. Erickson, P., (1994). A practical guide to environmental impact assessment, Academic Press, London.Google Scholar
  5. Finkelstein, A., Kramer, J., and Goedicke, M. (1990). Viewpoint-oriented software development, Proceedings of the 3rd International Workshop on Software Engineering and its Applications, 1: 337–351.Google Scholar
  6. Fischer, D., and Davies, G. (1973). An approach to assessing environmental impacts, Journal of Environmental Management, 1: 207–227.Google Scholar
  7. Fischer, D., and Nakakoji, K. (1992). Beyond the macho approach of artificial intelligence: empowering human designers — do not replace them, Knowledge-Based Systems Journal, 5 (1): 15–30.CrossRefGoogle Scholar
  8. Harker, S., Eason, K., and Dobson, J. (1993). The change and evolution of requirements as a challenge to the practice of software engineering, in Proceedings of the IEEE international symposium on requirements engineering (RE’93), San Diego, California.Google Scholar
  9. Huh, S., and Rosenberg, D. (1996). A change management framework: dependency maintenance and change notification, Journal of Systems and Software, 34Google Scholar
  10. Lehman, M., and Belady, L. (1985). Program evolution: processes of software change, Academic Press, London.Google Scholar
  11. Lehman, M. (1996). Feedback in the software evolution process, Information and Software Technology, 38: 681–686.CrossRefMathSciNetGoogle Scholar
  12. Leveson, N.G. (1996). Software safety: why, what and how, ACM Computing Surveys, 18 (2): 125–163.CrossRefGoogle Scholar
  13. Lientz, B., and Swanson, E. (1980). Software maintenance management, Addison-Wesley.Google Scholar
  14. Oates, T., Prasad, M. and Lesser, V. (1997). Co-operative information gathering: a distributed problem-solving approach, Journal of Systems and Software, 144 (1): 72–88.Google Scholar
  15. Petroski, H. (1985). To engineer is human: the role of failure in successful design, New York, St. Martin’s Press.Google Scholar
  16. Pohl, K., Domges, R., and Jarke, M. (1997). Towards method-driven trace capture, 9th International Conference, CaiSE’ 97, Barcelona, Spain.Google Scholar
  17. Sisti, F., and Joseph, S. (1994). Software risk evaluation method, Technical report CMU/SEI-94-TR-19, Software Engineering Institute, Pittsburgh.Google Scholar
  18. Sugden, R., and Strens, M. (1996a). Strategies, tactics and methods for handling change, In Proceedings of International IEEE Symposium and Workshop on Engineering of Computer-Based Systems (ECBS ’86), Friedrichshafen, Germany.CrossRefGoogle Scholar
  19. Sugden, R., and Strens, M. (1996b). Change analysis: A step towards meeting the challenge of changing requirements, In Proceedings of International IEEE Symposium and Workshop on Engineering of Computer-Based Systems (ECBS ’86), Friedrichshafen, Germany.Google Scholar
  20. Zowghi, D., and Offen, R. (1997). A logical framework for modeling and reasoning about the evolution of requirements, In Proceedings of the 3rd IEEE International Conference on Requirements Engineering.CrossRefGoogle Scholar

Copyright information

© IFIP 1998

Authors and Affiliations

  • W. Lam
    • 1
  1. 1.Requirements Engineering Lab (RE Lab) Department of Computer ScienceUniversity of Hertfordshire College Lane, HatfieldUK

Personalised recommendations