2014
DOI: 10.1007/978-3-319-09156-3_6
|View full text |Cite
|
Sign up to set email alerts
|

Support for Refactoring an Application towards an Adaptive Object Model

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2015
2015
2021
2021

Publication Types

Select...
2
1

Relationship

2
1

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 14 publications
0
3
0
Order By: Relevance
“…This is part of a larger project called Esfinge that embraces several innovative metadata-based frameworks. Previous work on Esfinge AOM RoleMapper focused on different issues, such as the primary mapping between domain-specific and domain-independent classes [38] and the support to incrementally refactor towards the AOM patterns [39]. A preliminary solution for the generation of static class adapters was first presented in [40] but without support for code annotations, which is essential to reuse metadatabased frameworks.…”
Section: Esfinge Aom Rolemappermentioning
confidence: 99%
See 1 more Smart Citation
“…This is part of a larger project called Esfinge that embraces several innovative metadata-based frameworks. Previous work on Esfinge AOM RoleMapper focused on different issues, such as the primary mapping between domain-specific and domain-independent classes [38] and the support to incrementally refactor towards the AOM patterns [39]. A preliminary solution for the generation of static class adapters was first presented in [40] but without support for code annotations, which is essential to reuse metadatabased frameworks.…”
Section: Esfinge Aom Rolemappermentioning
confidence: 99%
“…Another benefit of allowing the application to define its own domain-specific AOM classes is that it has more freedom to define a more suitable structure based on its adaptability requirements. As presented by a previous work [39], the mapping enables the model to start simple and be evolved to implement more patterns. That also allows the specific AOM model to contain more specific business rules and to have features not implemented by the framework domainindependent AOM model, such as entity type inheritance.…”
Section: B Mapping Domain-specific Aom Modelsmentioning
confidence: 99%
“…In real applications that use AOM as the architectural style, the AOM model is usually implemented only in entities where flexibility is a requirement, using only the required patterns [7]. Other entities also follow a static model adopted by the target programming language, containing fixed attributes and access methods.…”
Section: Figure 3: Aom Framework Model Representationmentioning
confidence: 99%