Dynamic model evolution

Atzmon Hen-Tov; David Lorenz; Lena Nikolaev; Lior Schachter; Rebecca Wirfs-Brock; Joseph W. Yoder

doi:10.1145/2493288.2493304

Dynamic model evolution

Atzmon Hen-Tov, David Lorenz, Lena Nikolaev, Lior Schachter, Rebecca Wirfs-Brock, Joseph W. Yoder

Computer Science

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › peer-review

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.

Original language	English
Title of host publication	PLoP 2010 - 17th Conference on Pattern Languages of Programs, Proceedings
DOIs	https://doi.org/10.1145/2493288.2493304
State	Published - 2010
Event	17th Conference on Pattern Languages of Programs, PLoP 2010 - Reno, NV, United States Duration: 16 Oct 2010 → 18 Oct 2010

Publication series

Name	ACM International Conference Proceeding Series

Conference

Conference	17th Conference on Pattern Languages of Programs, PLoP 2010
Country/Territory	United States
City	Reno, NV
Period	16/10/10 → 18/10/10

Keywords

Adaptive Object Model (AOM)
Creational patterns
Factory objects
Lazy loading
Model talk

Access to Document

10.1145/2493288.2493304

Cite this

@inproceedings{f9c3b304a87641d0990efb27bbcb5091,

title = "Dynamic model evolution",

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.",

keywords = "Adaptive Object Model (AOM), Creational patterns, Factory objects, Lazy loading, Model talk",

author = "Atzmon Hen-Tov and David Lorenz and Lena Nikolaev and Lior Schachter and Rebecca Wirfs-Brock and Yoder, {Joseph W.}",

year = "2010",

doi = "10.1145/2493288.2493304",

language = "אנגלית",

isbn = "9781450301077",

series = "ACM International Conference Proceeding Series",

booktitle = "PLoP 2010 - 17th Conference on Pattern Languages of Programs, Proceedings",

}

Hen-Tov, A, Lorenz, D, Nikolaev, L, Schachter, L, Wirfs-Brock, R & Yoder, JW 2010, Dynamic model evolution. in PLoP 2010 - 17th Conference on Pattern Languages of Programs, Proceedings., 16, ACM International Conference Proceeding Series, 17th Conference on Pattern Languages of Programs, PLoP 2010, Reno, NV, United States, 16/10/10. https://doi.org/10.1145/2493288.2493304

TY - GEN

T1 - Dynamic model evolution

AU - Hen-Tov, Atzmon

AU - Lorenz, David

AU - Nikolaev, Lena

AU - Schachter, Lior

AU - Wirfs-Brock, Rebecca

AU - Yoder, Joseph W.

PY - 2010

Y1 - 2010

N2 - 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.

AB - 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.

KW - Adaptive Object Model (AOM)

KW - Creational patterns

KW - Factory objects

KW - Lazy loading

KW - Model talk

UR - http://www.scopus.com/inward/record.url?scp=84892904650&partnerID=8YFLogxK

U2 - 10.1145/2493288.2493304

DO - 10.1145/2493288.2493304

M3 - ???researchoutput.researchoutputtypes.contributiontobookanthology.conference???

AN - SCOPUS:84892904650

SN - 9781450301077

T3 - ACM International Conference Proceeding Series

BT - PLoP 2010 - 17th Conference on Pattern Languages of Programs, Proceedings

T2 - 17th Conference on Pattern Languages of Programs, PLoP 2010

Y2 - 16 October 2010 through 18 October 2010

ER -

Dynamic model evolution

Abstract

Publication series

Conference

Keywords

Access to Document

Other files and links

Fingerprint

Cite this