Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Model-driven architecture”

Model Driven Architecture

Aksit, Mehmet, Rensink, Arend, Assmann, Uwe · Lecture notes in computer science · 2005

Cited by 9Open access

Model Driven Architecture (MDA)

Gernot Starke · 2011

No AccessEffektive Software-ArchitekturenAug 2011Model Driven Architecture (MDA)Gernot StarkeGernot Starkehttps://doi.org/10.3139/9783446428515.008SectionsAboutPDF ToolsAdd to FavoritesDownload CitationTrack CitationsCopy LTI LinkPDF key 'share (en)' returned an object instead of string.FacebookTwitterEmailLinkedIn previous chapternext chapter FiguresReferencesRelatedDetails 2011Pages: 293-300Print ISBN: 978-3-446-42728-0eISBN: 978-3-446-42851-5 Copyright & Permissions© 2011 Carl Hanser Verlag GmbH & Co. KGPDF DownloadLoading ...

Cited by 8

Investigating Model Driven Architecture

Atif Mashkoor · 2004

would like to thank my supervisor Magnus Eriksson for his help, valuable suggestions and timely advices, which played important role in the fulfillment of this thesis. 2

Cited by 0

Model Transformations in Model Driven Architecture

Atif Aftab, Ahmed Jilani, Muhammad Usman et al. · 2016

AbstractTransformation is one of the prominent features and the rising research area of Model Driven Architecture since last few years. There are many techniques which have been proposed as a Request for Proposal (RFP) in Query, View and Transformation (QVT). In this paper we have conducted a survey on transformation techniques. The surveyed techniques include pattern based approaches, transformation languages, transformation rules, Metamodel based approaches etc. This work has summarize, categorized and identified different analysis parameters of these techniques. On the basis of identified parameters we have presented an analysis matrix to describe the strength of different approaches. The major focus of the work is on model to model transformation techniques i.e. from PIM to PSM transformation. Keywords- Model Driven Architecture; Transformation and analysis matrix

Cited by 0

1 Transformations in the Model Driven Architecture 1.1 Towards the Model Driven Architecture

2014

The Action Semantics for UML provides a standard and platform independent way to describe the behavior of methods and executable actions in object-oriented system design prior to implementation allowing the development of highly auto-mated and optimized code generators for UML CASE tools. Model transformation systems provide visual but formal background to specify arbitrary transformations in the Model Driven Architecture (the leading trend in software engineering). In the current paper, we describe a general encoding of model transformation systems as executable Action Semantics expressions to provide a standard way for auto-matically generating the implementation of formal (and provenly correct) trans-formations by off-the-shelf MDA tools. In addition, we point out a weakness in the Action Semantics standard that must be improved to achieve a stand-alone and functionally complete action specification language.

Cited by 0

Software performance model-driven architecture

Vittorio Cortellessa, Antinisca Di Marco, Paola Inverardi · 2006

Model transformations in MDA mostly aim at stepping from a Platform Independent Model (PIM) to a Platform Specific Model (PSM) from a functional viewpoint. In order to develop high quality software products, non-functional attributes (such as performance) must be taken into account. In this paper we extend the canonical view of the MDA approach to embed additional types of models that allow to structure a Model Driven approach keeping into account performance issues. We define the relationships between MDA typical models and the newly introduced models, as well as relationships among the latter ones. In this extended framework new types of model-to-model transformations also need to be devised. We place an existing methodology for transforming software models into performance models within the scope of this framework.

Cited by 28

What is model driven architecture

Ragnhild Kobro Runde, Ketil Stølen · Duo Research Archive (University of Oslo) · 2003

OMG promotes Model Driven Architecture (MDA) as the new direction for system development, especially supporting integration, interoperability and portability. But what is MDA really about, and what is model driven architecture? These are fundamental questions, to which precise answers are surprisingly hard to find. Not even the term "model driven" is clearly defined.\nThis article views MDA as a framework for constructing methodologies for model driven development of system architectures. The exact meaning of this position is presented in detail, and a definition of the term "model driven" is proposed. The main concepts in MDA are explained, with an emphasis on giving specific guidelines as to which interpretation should be chosen in cases where the official documentation is ambiguous or unclear. In particular, the important notions of refinement and transformation are examined, and it is explained how these similar, but different, concepts are related. The conclusion gives a short survey describing to which extent current methodologies fulfil the visions of MDA, and points at important areas with a particular need for more research.

Cited by 8Open access

What is Model Driven Architecture?

Ragnhild Kobro, Runde, Ketil Stølen et al. · 2003

OMG promotes Model Driven Architecture (MDA) as the new direction for system development, especially supporting integration, interoperabil-ity and portability. But what is MDA really about, and what is model driven architecture? These are fundamental questions, to which precise answers are surprisingly hard to nd. Not even the term \\model driven" is clearly dened. This article views MDA as a framework for constructing methodologies for model driven development of system architectures. The exact meaning of this position is presented in detail, and a denition of the term \\model driven " is proposed. The main concepts in MDA are explained, with an emphasis on giving specic guidelines as to which interpretation should be chosen in cases where the ocial documentation is ambiguous or unclear. In particular, the important notions of renement and transformation are examined, and it is explained how these similar, but dierent, concepts are related. The conclusion gives a short survey describing to which extent current methodologies full the visions of MDA, and points at important areas with a particular need for more research. 1

Cited by 0

Abstract: The Model Driven Architecture

Salim Bouzitouna, Marie-pierre Gervais, Xavier Blanc · 2008

(MDA) approach defined by OMG advocates a clear separation between platform-independent models (PIMs) and platform-specific models (PSMs) in distributed applications. As such, MDA would ease the migration of applications to new platforms. However, it deals only with the evolution of the platform underlying the applications not the evolution of the business part of applications, i.e., the PIM itself. A way for dealing with this later evolution is to reuse as much as possible the existing PIMs and their corresponding PSMs. We propose a new initiative based on two principal points: the expressions of the reuse of PIM without change them and from these expressions, the automatic generation of glue binding their corresponding PSM. We focus in this paper on the concept of GLUE, and more

Cited by 0

Poole -- Model-Driven Architecture. ECOOP 2001.

Model-Driven Architecture Vision, John D. Poole · 2001

This paper surveys the core OMG MDA standards (i.e., UML, MOF, XMI and CWM) and discusses the current attempts at mapping these standards to J2EE, as examples of PIM-to-PSM translations that are currently under development. These forthcoming APIs will provide the initial building blocks for a new generation of systems based on the model-driven architecture concept. The progression of these initial MDA realizations to AOMs is the next logical step in this evolution. 2. The Vision This paper's proposed vision for the evolution of the MDA is twofold, consisting of both a near term vision and a long term vision of the future. The near term vision (i.e., nearly seamless interoperability, based on formal PIM-PSM translations and shared metadata) is achievable right now. The supporting technologies are largely specified and implementations are currently being built by a number of organizations. The long-term vision (i.e., the wide spread deployment of AOMs, as an evolution of the MDA), on the other hand, is still being conceptualized

Cited by 0

Model Driven Architecture: Foundations and Applications

Arend Rensink, Arend Rensink (editor · 2003

classes to Interfaces in Java or pure virtuals in C++ Translation of State Machine States and Events into Classes Translation of UML relationships into Operations and Attributes We will give one simple example. UML diagrams comprise boxes for concepts with lines for relationships between them. A few boxes correspond directly to language constructs such as classes, but for the other boxes and lines, it is necessary to find an appropriate implementation approach. An example of one form of relationship without a direct language counterpart is a composition.

Cited by 0

Entropy-based consistent model driven architecture

Stanisław Jerzy Niepostyn · Proceedings of SPIE, the International Society for Optical Engineering/Proceedings of SPIE · 2016

A description of software architecture is a plan of the IT system construction, therefore any architecture gaps affect the overall success of an entire project. The definitions mostly describe software architecture as a set of views which are mutually unrelated, hence potentially inconsistent. Software architecture completeness is also often described in an ambiguous way. As a result most methods of IT systems building comprise many gaps and ambiguities, thus presenting obstacles for software building automation. In this article the consistency and completeness of software architecture are mathematically defined based on calculation of entropy of the architecture description. Following this approach, in this paper we also propose our method of automatic verification of consistency and completeness of the software architecture development method presented in our previous article as Consistent Model Driven Architecture (CMDA). The proposed FBS (Functionality-Behaviour-Structure) entropy-based metric applied in our CMDA approach enables IT architects to decide whether the modelling process is complete and consistent. With this metric, software architects could assess the readiness of undergoing modelling work for the start of IT system building. It even allows them to assess objectively whether the designed software architecture of the IT system could be implemented at all. The overall benefit of such an approach is that it facilitates the preparation of complete and consistent software architecture more effectively as well as it enables assessing and monitoring of the ongoing modelling development status. We demonstrate this with a few industry examples of IT system designs.

Cited by 3