Software evolution in componentware - a practical approach

Rausch, Andreas

doi:10.1109/aswec.2000.844553

Cited by 3 publications

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The notion of tranquility is not only applicable in component systems [19,18], but also in all other paradigms that allow modularization and explicit interaction. We have found applications of the notion of quiescence in procedural programming, service-oriented programming and in objectoriented systems.…”

Section: Related Workmentioning

confidence: 99%

An alternative to Quiescence: Tranquility

Vandewoude

Ebraert²,

Berbers

et al. 2006

2006 22nd IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

This paper revisits a problem that was identified by Kramer and Magee: placing a system in a consistent state before and after runtime changes [16]. We show that their notion of quiescence as a necessary and sufficient condition for safe runtime changes is too strict and violates the black-box design principle. We introduce a weaker condition, tranquility; easier to obtain, less disruptive for the system and still sufficient to ensure application consistency. We also present an implementation of this concept in a component middleware platform.

show abstract

Section: Related Workmentioning

confidence: 99%