Evolving models in Model-Driven Engineering: State-of-the-art and future challenges

Paige, Richard F.; Matragkas, Nicholas; Rose, Louis M.

doi:10.1016/j.jss.2015.08.047

Cited by 54 publications

(35 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…But those meta-models' evolutions can be difficult because they impact other reusable assets like model transformation operations meaning those assets might have to evolve too. This threat is reduced by the large amount of existing MDE solutions addressing the problem of the meta-model evolution (Paige et al, 2016).…”

Section: Threats To Validitymentioning

confidence: 99%

Reusing Platform-specific Models in Model-Driven Architecture for Software Product Lines

Verdier

Seriai

Tiam³

2018

Proceedings of the 6th International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

One of the main concerns of software engineering is the automation of reuse in order to produce high quality applications in a faster and cheaper manner. Model-Driven Software Product Line Engineering is an approach providing solutions to systematically and automatically reuse generic assets in software development. More specifically, some solutions improve the product line core assets reusability by designing them according to the Model-Driven Architecture approach. However, existing approaches provide limited reuse for platformspecific assets. In fact, platform-specific variability is either ignored or only partially managed. These issues interfere with gains in productivity provided by reuse. In this paper, we first provide a better understanding of platform-specific variability by identifying variation points in different aspects of a software based on the well-known "4+1" view model categorization. Then we propose to fully manage platform-specific variability by building the Platform-Specific-Model using two submodels: the Cross-Cutting Model, which is obtained by transformation of the Platform-Independent Model, and the Application Structure Model, which is obtained by reuse of variable platform-specific assets. The approach has been experimented on two concrete applications. The obtained results confirm that our approach significantly improves the productivity of a product line.

show abstract

Section: Threats To Validitymentioning

confidence: 99%

Reusing Platform-specific Models in Model-Driven Architecture for Software Product Lines

Verdier

Seriai

Tiam³

2018

Proceedings of the 6th International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

show abstract

“…Two types of approaches are identifiable for change detection [17]: Models typically are entities linked to one another. Versioning one entity may thus have an impact on others.…”

Section: Versioning Modelsmentioning

confidence: 99%

“…This makes co-evolution an interesting field of research. Research on model versioning has brought various approaches for managing co-evolution [17]: (a) Inference approaches [6] rely on meta-model comparison to generate a strategy for evolving models to conform to an updated meta-model. (b) Operator approaches [12] are based on patterns and are characterized by a set of predetermined strategies that can handle a step-by-step co-evolution of meta-models and models.…”

Section: Versioning Modelsmentioning

confidence: 99%

Substitutability-Based Version Propagation to Manage the Evolution of Three-Level Component-Based Architectures

Borgne¹,

Delahaye²,

Huchard³

et al. 2017

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

An important issue of software architecture evolution is the capability for architects to keep a trace of the evolution of their work. This paper states that existing research on versioning does not cope well with software architectures. Indeed, it does not propose any adapted solutions to manage the co-evolution of the different architecture representations produced during the development process. We base our work on a three-level architecture description language (ADL) named Dedal, which represents architectures at three abstraction levels. Moreover, Dedal provides a formal base for managing version propagation. It is based on component substitutability that generalizes Liskov's substitutability principle. We propose a set of rules to support the prediction of version compatibility in terms of impact on the different architecture levels.

show abstract

“…Further, as the name implies, native apps are built using platform-specific SDKs and development tools provided by the platform vendors. The advantages of native mobile apps, of course, are (Jobe, 2013):…”

Section: Introductionmentioning

confidence: 99%

“…The MDA approach can help us ensure the sustainability of the know-how and increase the productivity while responding to the problems of fragmentation of the platforms. The Model-Driven Architecture (MDA) approach (Paige et al, 2016) brings significant advances in the control of the development of computer applications and peculiarly it enables productivity gains, increased reliability, significant improvement in sustainability and better agility in the face of changes.…”

Section: Introductionmentioning

confidence: 99%

Pragmatic Approach to Modeling and Generating Mobile Cross-Platform Applications

Lachgar¹,

Lamhaddab²,

Abdali³

et al. 2019

Journal of Computer Science

View full text Add to dashboard Cite

As a result of the ubiquity of smartphones, the number of mobile applications is extensively growing. In order to build native apps that reach all devices, developers should deal with many different operating systems, SDKs, development tools and programming languages, which implies serious effects on cost, time and success of the mobile project. In this study, the main objective is to propose a pragmatic approach for modeling and generating native cross-platform mobile applications, respecting a multilayer architecture. The proposed approach is an MDA based technique which combines UML formals and DSL. The paper is illustrated with the modeling of a typical CRUD based app.

show abstract

Evolving models in Model-Driven Engineering: State-of-the-art and future challenges

Cited by 54 publications

References 39 publications

Reusing Platform-specific Models in Model-Driven Architecture for Software Product Lines

Reusing Platform-specific Models in Model-Driven Architecture for Software Product Lines

Substitutability-Based Version Propagation to Manage the Evolution of Three-Level Component-Based Architectures

Pragmatic Approach to Modeling and Generating Mobile Cross-Platform Applications

Contact Info

Product

Resources

About