Developing web applications for different architectures: The MoWebA approach

González, Magalí; Cernuzzi, Luca; Aquino, Nathalie; Pastor, Oscar

doi:10.1109/rcis.2016.7549344

Cited by 8 publications

(16 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For this matter, we consider MoWebA [3,4,55], a MDD approach for to develop web applications that, among other things, propose the ASM phase considered in this study.…”

Section: The Pim Portability Problemmentioning

confidence: 99%

“…This new level of abstraction is the Architectural Specific Model -ASM [3], which is an intermediate model between PIM and PSM, and whose final goal is to encapsulate information referred to the system architecture [4]. The motivation for defining this new level of abstraction might be understood by analyzing one of the most popular web architectures: the one related to Rich Internet Applications -RIA.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Exploring Model-to-Model Transformations for RIA Architectures by means of a Systematic Mapping Study

Bonhaure

González

Aquino

et al. 2017

CLEIej

Self Cite

View full text Add to dashboard Cite

This study focuses on model-to-model -M2M -transformations, as part of the ModelDriven Development -MDD -approach, for Rich Internet Applications -RIA. The main aim of this study is to identify fields that require further contributions, and/or research opportunities in the previously mentioned context. We applied mapping studies techniques, since these techniques use the same basic methodology as reviews but are more general and aimed at discovering what the research trends are, allowing to identify gaps in the literature. From an initial set of 132 papers, we selected 30 papers first. Then, thanks to experts' suggestion, we added 3 additional papers. Therefore, we considered 33 research papers. The performed analysis led to various considerations. Among the important ones, we can mention: there are many newly proposed methods, the scarcity of rigorous and formal validation of such methods, the problem of the portability of Platform Independent Models -PIM, and the low number of tools available for MDD.

show abstract

“…For this matter, we consider MoWebA [3,4,55], a MDD approach for to develop web applications that, among other things, propose the ASM phase considered in this study.…”

Section: The Pim Portability Problemmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Exploring Model-to-Model Transformations for RIA Architectures by means of a Systematic Mapping Study

Bonhaure

González

Aquino

et al. 2017

CLEIej

Self Cite

View full text Add to dashboard Cite

show abstract

“…Brambilla et al [3] han recomendado un proceso que permite la definición de una sintaxis abstracta y MoWebA lo sigue con el objetivo de definir un metamodelo para el ASM. Además, MoWebA complementa el proceso sugerido con pasos adicionales que van desde la definición de la sintaxis concreta hasta la generación del código final de una aplicación [12]. Los pasos de este proceso se sintetizan a continuación:…”

Section: Definición Y Aplicación De Modelos Asmunclassified

“…Un aporte diferenciador de MoWebA es la inclusión de un nuevo nivel de abstracción a los ya definidos por el framework MDA. Este nuevo nivel lo constituye el Modelo Específico de la Arquitectura (ASM -del inglés "Architecture Specific Model") [12], que permite, entre otras cosas, omitir la definición de Modelos Independientes de la Plataforma (PIM -del inglés "Platform-Independent Model ") específicos para cada tipo de arquitectura, fortaleciendo de esta manera la portabilidad de los mismos.…”

Section: Introductionunclassified

See 1 more Smart Citation

Una propuesta de transformación M2M para el análisis de la fase ASM de MoWebA

Falcón¹,

Pierre²

View full text Add to dashboard Cite

In the scenery of web engineering methodologies [1] [2], there is a current trend on following the Model-Driven Development (MDD) approach [3], adopting the Model-Driven Architecture (MDA). In MDA, model transformations are essential. Thus, instead of directly generate the code from the conceptual model (model-to-text transformation), the conceptual models, i.e. Platform Independent Models (PIMs), are translated to one or more Platform Specific Models (PSMs) by means of model-tomodel (M2M) transformations. Subsequently, PSMs are translated into code by means of model-to-text (M2T) transformation techniques.One of the strategies that MDA promotes to facilitate changeability and portability of the conceptual model is the prescription of the PIM separated from the PSM. However, in practice, current web methodologies tend to cope with architectural evolution trends by extending their modeling notations directly at the PIM level (e.g., WebML RIA [4], UWE for RIA [5], OOH4Ria [6], among others). MDD proposals for mobile applications development also follow this landscape. Examples of this are WebRatio [3], MD2 [7], MobiCloud [8], among others. Such extension usually results in an enriched PIM that includes characteristics and constraints of a certain specific architecture or platform. The enriched PIMs are obtained either by adding marks (but without considering this as a marked PIM), or by adding new entire models, or even by adding new elements in the PIM notation. Although it could be argued that after extending a PIM to support a specific architecture it is no longer a PIM, but a PSM, in general, the literature does not analyze this distinction.The problem is that this tendency of adapting the PIM to specific architectures goes against the principle of the PIM portability promoted by MDA. The enriched PIM loses part of its independence from the architecture/platform, and becomes increasingly more complex to understand and manage. The consequence is a loss of portability and reusability of the conceptual models.A complementary portability problem arises when web methodologies tend to enrich the PSM with architectural details, since the same architecture can be implemented in different platforms (e.g., the RIA architecture can be implemented in Backbase, Dojo, GWT, jQuery, among others). In this case, the problem is not concerning the conceptual model, but it requires for the same architecture multiple PSMs according to the different implementation platforms.To preserve the independence of the PIM and the portability of models towards different architectures, some authors have already proposed the introduction of an Architectural Specific Model (ASM) (e.g., [9], [10]). The ASM allows details related to the architecture to be moved out from the problem space (PIM) to an intermediate vii model in the solution space (ASM), avoiding the PIM from containing such details and contributing to its so desired portability. Moreover, the ASM model can result in different PSM models, one per each implementation platform.In this w...

show abstract