Patterns for data and metadata evolution in adaptive object-models

Authors:
Hugo Sereno Ferreira;Filipe Figueiredo Correia;Leon Welicki
Affiliations:
University of Porto;University of Porto;ONO (Cableuropa S.A.)
Venue:
Proceedings of the 15th Conference on Pattern Languages of Programs
Year:
2008

Citing 7
Cited 4

Type object

Pattern languages of program design 3
Refactoring: improving the design of existing code

Refactoring: improving the design of existing code
Patterns of Enterprise Application Architecture

Patterns of Enterprise Application Architecture
Architecture and design of adaptive object-models

ACM SIGPLAN Notices
Schema versioning and database conversion techniques for bi-temporal databases

Annals of Mathematics and Artificial Intelligence
Model-driven Development of Complex Software: A Research Roadmap

FOSE '07 2007 Future of Software Engineering
Towards a pattern language for adaptive object models

Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion

Supporting the evolution of software knowledge with adaptive software artifacts

Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Core patterns of object-oriented meta-architectures

Proceedings of the 17th Conference on Pattern Languages of Programs
Dynamic model evolution

Proceedings of the 17th Conference on Pattern Languages of Programs
Documenting software using adaptive software artifacts

Proceedings of the 2013 companion publication for conference on Systems, programming, & applications: software for humanity

Quantified Score

Hi-index	0.00

Visualization

Abstract

An Adaptive Object-Model (AOM) is an architectural pattern based upon a dynamic meta-modeling technique where the object model of the system is explicitly defined as data to be interpreted at run-time. The object model encompasses the full specification of domain objects, states, events, conditions, constraints and business rules. Several design patterns, that have before been documented, describe a set of good-practices within this domain. This paper approaches data and metadata evolution issues in the context of AOMs, by describing three additional patterns --- History of Operations, System Memento and Migration. They establish ways to track, version, and evolve information, at the several abstraction levels that may exist in an AOM.