From Java to UpgradeJ: an empirical study

Authors:
Ewan Tempero;Gavin Bierman;James Noble;Matthew Parkinson
Affiliations:
University of Auckland;Microsoft Research;Victoria University of Wellington;University of Cambridge
Venue:
Proceedings of the 1st International Workshop on Hot Topics in Software Upgrades
Year:
2008

Citing 5
Cited 2

Mutatis mutandis: safe and predictable dynamic software updating

Proceedings of the 32nd ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Micro patterns in Java code

OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
How do APIs evolve? A story of refactoring: Research Articles

Journal of Software Maintenance and Evolution: Research and Practice - IEEE International Conference on Software Maintenance (ICSM2005)
Micro pattern evolution

Proceedings of the 2006 international workshop on Mining software repositories
A survey and taxonomy of approaches for mining software repositories in the context of software evolution

Journal of Software Maintenance and Evolution: Research and Practice

Dynamic software updates: a VM-centric approach

Proceedings of the 2009 ACM SIGPLAN conference on Programming language design and implementation
Aspect-based dynamic software updating: a model and its empirical evaluation

Proceedings of the tenth international conference on Aspect-oriented software development

Quantified Score

Hi-index	0.00

Visualization

Abstract

UpgradeJ is a variant of Java that offers linguistic support for lightweight dynamic software updating (DSU), or hotswapping. UpgradeJ allows co-existing multiple versions of classes and adapts Java's type system to provide incremental typechecking. This paper provides some preliminary, but encouraging, results of an empirical study into the applicability of UpgradeJ. By analysing how classes in popular, open-source Java applications change from release to release, we are able to estimate the proportion of those changes that could be made dynamically in UpgradeJ. Although these applications were not designed with DSU in mind we find that many of the changes to classes could be supported by the UpgradeJ DSU model without any significant code rewriting.