An alternative to Quiescence: Tranquility

  • Authors:
  • Yves Vandewoude;Peter Ebraert;Yolande Berbers;Theo D'Hondt

  • Affiliations:
  • Deparment of Computer Science - Celestijnenlaan 200A - 3000 Leuven, Belgium;Programming Technology Lab - Pleinlaan 2 - 1050 Brussel, Belgium;Deparment of Computer Science - Celestijnenlaan 200A - 3000 Leuven, Belgium;Programming Technology Lab - Pleinlaan 2 - 1050 Brussel, Belgium

  • Venue:
  • ICSM '06 Proceedings of the 22nd IEEE International Conference on Software Maintenance
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper revisits a problem that was identified by Kramer andMagee: placing a system in a consistent state before and afterruntime changes [16]. We show that their notion of quiescence as anecessary and sufficient condition for safe runtime changes is toostrict and violates the black-box design principle. We introduce aweaker condition, tranquility; easier to obtain, less disruptivefor the system and still sufficient to ensure applicationconsistency. We also present an implementation of this concept in acomponent middleware platform.