A trace model for system requirements changes on embedded systems

ABSTRACT Technical systems play an important role in our daily lives. Most systems have to be changed during their lifetime, but cost estimates of changes are often inaccurate and implementation of changes is time consuming and cost intensive. Planning and performing changes can be supported by precise impact analysis. Traditionally, impact analysis has been something that software professionals do intuitively, after some cursory examination of code and documentation. But, empirical investigation shows that even experienced software professionals predict incomplete sets of change impacts. This paper introduces an approach that focuses on impact analysis of system requirements changes and that is suited for embedded control systems. The approach is based on a fine-grained trace model. Empirical studies show that the approach allows a more effective impact analysis of changes on embedded systems.

[1]  Joseph A. Goguen,et al.  An Object-Oriented Tool for Tracing Requirements , 1996, IEEE Softw..

[2]  H. M. Sneed,et al.  The myth of 'top-down' software development and its consequences for software maintenance , 1989, Proceedings. Conference on Software Maintenance - 1989.

[3]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[4]  Antje von Knethen,et al.  Change-Oriented Requirements Traceability: Support for Evolution of Embedded Systems , 2002, ICSM.

[5]  Mikael Lindvall,et al.  How well do experienced software developers predict software change? , 1998, J. Syst. Softw..

[6]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[7]  H. Dieter Rombach,et al.  A Controlled Expeniment on the Impact of Software Structure on Maintainability , 1987, IEEE Transactions on Software Engineering.

[8]  Thierry Bodhuin,et al.  Supporting impact analysis: a semi-automated technique and associated tool , 1995, Proceedings of International Conference on Software Maintenance.

[9]  Jan U. Kiess Objektorientierte Modellierung von Automatisierungssystemen: Software Engineering für embedded systems , 1995 .

[10]  J. C. Townsend,et al.  Software Requirements Specification , 2001 .

[11]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[12]  Jun Han,et al.  Supporting impact analysis and change propagation in software engineering environments , 1997, Proceedings Eighth IEEE International Workshop on Software Technology and Engineering Practice incorporating Computer Aided Software Engineering.

[13]  Robert S. Arnold,et al.  Software Change Impact Analysis , 1996 .

[14]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..