On the Role of Architectural Style in Model Driven Development

Mikkonen, Tommi; Pitkänen, Risto; Pussinen, Mika

doi:10.1007/978-3-540-24769-2_6

Cited by 13 publications

(10 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…One of them is the role of the Architecture within a MDA-based methodology. Previous studies [19] have remarked the importance of specifying the architectural view as key aspect of the development process. In the scope of a MDAbased development, the modeling of the architecture determines which elements should be included inside models and which models should be generated at each abstraction level.…”

Section: Introductionmentioning

confidence: 99%

A model-driven approach to weave architectural styles into service-oriented architectures

López-Sanz

Vara

Marcos

et al. 2009

Proceedings of the First International Workshop on Model Driven Service Engineering and Data Quality and Security

View full text Add to dashboard Cite

Model-driven development is recognized as one of the most popular approaches in Software Engineering. Recent research in the area highlights the importance of using an explicit architectural model in this context. Since current needs in software development have been adequately covered by serviceoriented architectures, we have used the model-driven approach to generate service-oriented architectural models. However, the emphasis on the SOC paradigm has led to the design of architectures lacking some desirable features. Knowing the benefits provided by architectural styles, we have found that their use can help us to overcome those needs. Our goal is to obtain a service-oriented model which satisfies the requirements of the concrete architecture and complies with the constraints and vocabulary defined for a specific architectural style. To achieve this, we propose to use a weaving model which merges the architectural model with a model of the architectural style of choice.

show abstract

Section: Introductionmentioning

confidence: 99%

A model-driven approach to weave architectural styles into service-oriented architectures

López-Sanz

Vara

Marcos

et al. 2009

Proceedings of the First International Workshop on Model Driven Service Engineering and Data Quality and Security

View full text Add to dashboard Cite

show abstract

“…To preserve the independence of the PIM and the portability of models towards different architectures, some authors have already proposed the introduction of an Architecture Specific Model (ASM) (e.g., [13,14]). The ASM allows details related to the architecture to be moved out from the problem space (PIM) to an intermediate model in the solution space (ASM), avoiding the PIM from containing such details and contributing to its so desired portability.…”

Section: Introductionmentioning

confidence: 99%

Model-Driven Approach to develop Rich Web Applications

Nuñez¹,

Bonhaure²,

González³

et al. 2018

CLEIej

View full text Add to dashboard Cite

Many Web applications have among their features the possibility of distributing their data and their business logic between the client and the server, also allowing an asynchronous communication between them. These features, originally associated with the arrival of Rich Internet Applications (RIA), remain particularly relevant and desirable. In the area of RIA, there are few proposals that simultaneously consider these features, adopt Model-Driven Development (MDD), and use implementation technologies based on scripting. In this work, we start from MoWebA, an MDD approach to web application development, and we extend it by defining a specific architecture model with RIA functionalities, supporting the previously mentioned features. We have defined the necessary metamodels and UML profiles, as well as transformation rules that allow you to generate code based on HTML5, Javascript, jQuery, jQuery Datatables and jQuery UI. The preliminary validation of the proposal shows positive evidences regarding the effectiveness, efficiency and satisfaction of the users with respect to the modeling and code generation processes of the proposal.

show abstract

“…In other words, the application seems to be more generic than a particular implementation, whereas we used the underlying architecture as a starting point, and added application specifics on top of the architecture. Still, even if following MDA practices, the possibility to use patterns to represent design guidelines provides added value [10].…”

Section: Related Workmentioning

confidence: 99%