A Classification of Unanticipated Runtime Software Changes in Java

  • Authors:
  • Jens Gustavsson

  • Affiliations:
  • -

  • Venue:
  • ICSM '03 Proceedings of the International Conference on Software Maintenance
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

For some software systems with high availabilityrequirements, it is not acceptable to have the system shutdown when a new version of it is to be deployed. Analternative is to use unanticipated runtime softwareevolution, which means making changes to the softwaresystem while it is executing. We propose a classificationof unanticipated runtime software changes. Ourclassification consists of a code change aspect, a statechange aspect and an activity aspect. The purpose of theclassification is to get a greater understanding of thenature of such changes, and to facilitate an abstract viewof them. We also present results from a case study, wherehistorical changes to an existing software system havebeen categorized according to the classification. The datafrom the case study gives an indication that the JavaPlatform Debugger Architecture, a standard mechanismin Java virtual machines, is a viable technical foundationfor runtime software evolution systems.