Dynamic model evolution

Authors:
Atzmon Hen-Tov;David H. Lorenz;Lena Nikolaev;Lior Schachter;Rebecca Wirfs-Brock;Joseph W. Yoder
Affiliations:
Pontis Ltd.;Open University of Israel;Pontis Ltd.;Open University of Israel;Wirfs-Brock Associates, Inc.;The Refactory, Inc.
Venue:
Proceedings of the 17th Conference on Pattern Languages of Programs
Year:
2010

Citing 11
Cited 0

A third generation Smalltalk-80 implementation

OOPLSA '86 Conference proceedings on Object-oriented programming systems, languages and applications
Design patterns: elements of reusable object-oriented software

Design patterns: elements of reusable object-oriented software
Type object

Pattern languages of program design 3
Metadata and active object-models

Addendum to the 1998 proceedings of the conference on Object-oriented programming, systems, languages, and applications (Addendum)
The Uml Profile for Framework Architectures

The Uml Profile for Framework Architectures
Architecture and design of adaptive object-models

ACM SIGPLAN Notices
The Adaptive Object-Model Architectural Style

WICSA 3 Proceedings of the IFIP 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance
Metadata and Adaptive Object-Models

ECOOP '00 Proceedings of the Workshops, Panels, and Posters on Object-Oriented Technology
ModelTalk: When Everything Is a Domain-Specific Language

IEEE Software
Patterns for data and metadata evolution in adaptive object-models

Proceedings of the 15th Conference on Pattern Languages of Programs
Adaptive object-model builder

Proceedings of the 16th Conference on Pattern Languages of Programs

Quantified Score

Hi-index	0.00

Visualization

Abstract

In the Adaptive Object-Model (AOM) architectural style, user-defined domain entities and their relationships, attributes and behavior are described by externally stored metadata. AOM implementations reify the domain entities at runtime by interpreting the metadata. Users change the object model by editing the metadata to reflect changes in the domain. This paper describes a pattern for incorporating model changes into an AOM production system without taking the system off-line. Dynamic evolution of the object model is done during loading of a domain object. The Dynamic Model Evolution pattern is applicable when a system needs to keep running, and the alternative of updating the entire object model at the time a new version comes online is too time consuming to be a practical option.