Adaptive object-model builder

Welicki, León; Yoder, Joseph W.; Wirfs-Brock, Rebecca

doi:10.1145/1943226.1943231

Cited by 6 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Citation information: DOI 10.1109/ACCESS.2021.3087795, IEEE Access different sources and in different formats. Depending on how sophisticated the model is, it might need a specialized builder to assembly the entities and the entity types [18].…”

Section: B Aom System Architecturementioning

confidence: 99%

A Model to Enable the Reuse of Metadata-Based Frameworks in Adaptive Object Model Architectures

et al. 2021

View full text Add to dashboard Cite

The Adaptive Object Model (AOM) is an architectural style in which domain entity types are represented as instances that can be changed at runtime. It can be used to achieve higher flexibility in domain classes. Due to AOM entities having a distinct structure, they are not compatible with most popular frameworks, especially those that use reflection and code annotations. Objective: To solve such limitations, this work aims to propose a model that enables the reuse of frameworks designed for classic object-oriented domain models in an AOM application. Methods: The proposed model uses dynamically-generated adapters for AOM entities that encapsulate them in a class with the format expected by the frameworks. A reference implementation was developed in the Esfinge AOM RoleMapper framework to evaluate the viability of the proposed model. Initially, to evaluate the solution feasibility, a case study was carried out using the Hibernate framework. Further, an experiment was conducted to assess how the participants perceived the framework functionality reuse through the proposed model. Results: The feasibility study revealed that the solution could be applied in a complex setting for the chosen object-relational mapping frame. It raised some difficulties that can be addressed in future studies. In the experiment, the development time did not present a significant difference compared to the competing approach. Despite the considerable learning curve, most participants considered that the proposed approach has more advantages than the alternative. Conclusion: Based on the evaluations, we can conclude that the proposed model can be successfully employed to use AOM entities with frameworks that were not designed for AOM applications. The possibility of reusing existing frameworks can reduce the effort required to adopt an AOM architecture and, consequently, be a facilitator in implementing more flexible and adaptive approaches.

show abstract

Section: B Aom System Architecturementioning

confidence: 99%

A Model to Enable the Reuse of Metadata-Based Frameworks in Adaptive Object Model Architectures

et al. 2021

View full text Add to dashboard Cite

show abstract

“…Once all conflicts are resolved and the custom upgrade scripts are written, the customer can test the new version along with the entire set of upgraders. During production, the upgrade framework is invoked as a first step in the AOM BUILDER (Welicki et al 2009) and performs just-in-time instance upgrade ("on-the-fly upgrade," Fig. 1).…”

Section: Solutionmentioning

confidence: 99%

“…An AOMBuilder (Welicki et al 2009) is responsible for de-serializing entities retrieved from a repository (e.g., a relational database). It invokes a collection of BuildSteps in order to gradually build the entity.…”

Section: Dynamicsmentioning

confidence: 99%

“…This helps in managing the overall process.  AOM BUILDER (Welicki et al 2009) is an evolution of the BUILDER (Gamma et al 1995) pattern.…”

Section: Related Patternsmentioning

confidence: 99%

“…Thus, to represent an entity, TYPE SQUARE (Yoder et al 2001) is used, i.e., a combination of TYPE OBJECT and PROPERTY patterns. Additionally, an AOM might use these patterns: ENTITYRELATIONSHIP (ACCOUNTABILITY), (Welicki et al 2009), RULEOBJECT (Arsanjani 2000), HISTORY OF OPERATIONS (Ferreira et al 2008), SYSTEM MEMENTO (Ferreira et al2008), and MIGRATION (Ferreira et al 2008). For an overview of the core patterns of this architectural style, see Appendix A.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Dynamic model evolution

Hen-Tov¹,

Lorenz

Nikolaev³

et al. 2010

Proceedings of the 17th Conference on Pattern Languages of Programs

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Support for Refactoring an Application towards an Adaptive Object Model

Guerra

Aguiar

2014

Computational Science and Its Applications – ICCSA 2014

View full text Add to dashboard Cite

Adaptive object-model builder

Cited by 6 publications

References 6 publications

A Model to Enable the Reuse of Metadata-Based Frameworks in Adaptive Object Model Architectures

A Model to Enable the Reuse of Metadata-Based Frameworks in Adaptive Object Model Architectures

Dynamic model evolution

Support for Refactoring an Application towards an Adaptive Object Model

Contact Info

Product

Resources

About