|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
Class Schema Evolution for Persistent Object-Oriented Software: Model, Empirical Study, and Automated Support
Feb. 2013 (vol. 39 no. 2)
pp. 184-196
| ASCII Text | x | ||
| Marco Piccioni, Manuel Oriol, Bertrand Meyer, "Class Schema Evolution for Persistent Object-Oriented Software: Model, Empirical Study, and Automated Support," IEEE Transactions on Software Engineering, vol. 39, no. 2, pp. 184-196, Feb., 2013. | |||
| BibTex | x | ||
| @article{ 10.1109/TSE.2011.123, author = {Marco Piccioni and Manuel Oriol and Bertrand Meyer}, title = {Class Schema Evolution for Persistent Object-Oriented Software: Model, Empirical Study, and Automated Support}, journal ={IEEE Transactions on Software Engineering}, volume = {39}, number = {2}, issn = {0098-5589}, year = {2013}, pages = {184-196}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2011.123}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - Class Schema Evolution for Persistent Object-Oriented Software: Model, Empirical Study, and Automated Support IS - 2 SN - 0098-5589 SP184 EP196 EPD - 184-196 A1 - Marco Piccioni, A1 - Manuel Oriol, A1 - Bertrand Meyer, PY - 2013 KW - Object oriented modeling KW - Java KW - Databases KW - Software KW - Robustness KW - Dictionaries KW - Atomic measurements KW - IDE integration KW - Versioning KW - persistence KW - serialization KW - object-oriented class schema evolution VL - 39 JA - IEEE Transactions on Software Engineering ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TSE.2011.123
With the wide support for object serialization in object-oriented programming languages, persistent objects have become commonplace and most large object-oriented software systems rely on extensive amounts of persistent data. Such systems also evolve over time. Retrieving previously persisted objects from classes whose schema has changed is, however, difficult, and may lead to invalidating the consistency of the application. The ESCHER framework addresses these issues through an IDE-integrated approach that handles class schema evolution by managing versions of the code and generating transformation functions automatically. The infrastructure also enforces class invariants to prevent the introduction of potentially corrupt objects. This paper describes a model for class attribute changes, a measure for class evolution robustness, four empirical studies, and the design and implementation of the ESCHER system.
Index Terms:
Object oriented modeling,Java,Databases,Software,Robustness,Dictionaries,Atomic measurements,IDE integration,Versioning,persistence,serialization,object-oriented class schema evolution
Citation:
Marco Piccioni, Manuel Oriol, Bertrand Meyer, "Class Schema Evolution for Persistent Object-Oriented Software: Model, Empirical Study, and Automated Support," IEEE Transactions on Software Engineering, vol. 39, no. 2, pp. 184-196, Feb. 2013, doi:10.1109/TSE.2011.123
Usage of this product signifies your acceptance of the Terms of Use.

