Relevant bibliographies by topics / Model-driven engineering

Academic literature on the topic 'Model-driven engineering'

Author: Grafiati
Published: 4 June 2021
Last updated: 19 October 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Model-driven engineering.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Model-driven engineering"

1

Rugaber, S., and K. Stirewalt. "Model-driven reverse engineering." IEEE Software 21, no. 4 (July 2004): 45–53. http://dx.doi.org/10.1109/ms.2004.23.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Margaria, Tiziana, and Bernhard Steffen. "Continuous Model-Driven Engineering." Computer 42, no. 10 (October 2009): 106–9. http://dx.doi.org/10.1109/mc.2009.315.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Kent, Stuart. "Model Driven Language Engineering." Electronic Notes in Theoretical Computer Science 72, no. 4 (March 2003): 6. http://dx.doi.org/10.1016/s1571-0661(04)80621-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Maroukian, Krikor, Charalampos Apostolopoulos, and George Tsaramirsis. "Extending model driven engineering aspects to business engineering domain: a model driven business engineering approach." International Journal of Information Technology 9, no. 1 (February 22, 2017): 49–57. http://dx.doi.org/10.1007/s41870-017-0009-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Schlereth, Michael, Marius Lauder, Sebastian Rose, and Andy SchÜrr. "Concurrent Model Driven Automation Engineering." atp edition - Automatisierungstechnische Praxis 52, no. 11 (November 1, 2010): 64. http://dx.doi.org/10.17560/atp.v52i11.421.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Nambiar, Manoj, Ajay Kattepur, Gopal Bhaskaran, Rekha Singhal, and Subhasri Duttagupta. "Model Driven Software Performance Engineering." ACM SIGMETRICS Performance Evaluation Review 43, no. 4 (February 25, 2016): 53–62. http://dx.doi.org/10.1145/2897356.2897363.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Jiménez-Pastor, Antonio, Antonio Garmendia, and Juan de Lara. "Scalable model exploration for model-driven engineering." Journal of Systems and Software 132 (October 2017): 204–25. http://dx.doi.org/10.1016/j.jss.2017.07.011.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Zacharewicz, Gregory, Nicolas Daclin, Guy Doumeingts, and Hezam Haidar. "Model Driven Interoperability for System Engineering." Modelling 1, no. 2 (October 15, 2020): 94–121. http://dx.doi.org/10.3390/modelling1020007.

Full text
Abstract:
To keep up to date, manufacturing enterprises need to use the latest results from the ICT sector, especially when collaborating with external partners in a supply chain and exchanging products and data. This has led to dealing with an increasing amount of heterogeneous information exchanged between partners including machines (physical means), humans and IT in the Supply Chain of ICT Systems (SC-ICTS). In this context, interoperability management is becoming more and more critical, but paradoxically, it is not yet fully efficiently anticipated, controlled and accompanied to recover from incompatibilities issues or failures. This paper intends to present how enterprise modeling, enterprise interoperability and model driven approaches can lead, together with system engineering architecture, to contribute to developing and improving the interoperability in the SC-ICTs. Model Driven System Engineering Architecture (MDSEA) is based on Enterprise Modeling using GRAI Model and its extensions. It gives enterprise internal developments guidelines, but originally, MDSEA is not the considering interoperability that is required between partners when setting a collaboration in the frame of SC-ICTS. As a result, the MDSEA, extended with interoperability concerns, led to the design of the MDISE (Model Driven Interoperability System Engineering) framework, which capitalizes on the research on enterprise interoperability. To finish, some proposals are made to extend the Model System Tool Box (MSTB) and the use of MDISE for Cyber Physical System (CPS) that are relevant components of SC-ICTS.
APA, Harvard, Vancouver, ISO, and other styles
9

Di Ruscio, Davide, Ludovico Iovino, and Alfonso Pierantonio. "Coupled Evolution in Model-Driven Engineering." IEEE Software 29, no. 6 (November 2012): 78–84. http://dx.doi.org/10.1109/ms.2012.153.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Akiki, Pierre A., Arosha K. Bandara, and Yijun Yu. "Engineering Adaptive Model-Driven User Interfaces." IEEE Transactions on Software Engineering 42, no. 12 (December 1, 2016): 1118–47. http://dx.doi.org/10.1109/tse.2016.2553035.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Model-driven engineering"

1

Patrascoiu, Octavian. "Model driven language engineering." Thesis, University of Kent, 2005. https://kar.kent.ac.uk/14352/.

Full text
Abstract:
Modeling is a most important exercise in software engineering and development and one of the current practices is object-oriented (OO) modeling. The Object Management Group (OMG) has defined a standard object-oriented modeling language the Unified Modeling Language (UML). The OMG is not only interested in modeling languages; its primary aim is to enable easy integration of software systems and components using vendor-neutral technologies. This thesis investigates the possibilities for designing and implementing modeling frameworks and transformation languages that operate on models and to explore the validation of source and target models. Specifically, we will focus on OO models used in OMG's Model Driven Architecture (MDA), which can be expressed in terms of UML terms (e.g. classes and associations). The thesis presents the Kent Modeling Framework (KMF), a modeling framework that we developed, and describes how this framework can be used to generate a modeling tool from a model. It then proceeds to describe the customization of the generated code, in particular the definition of methods that allows a rapid and repeatable instantiation of a model. Model validation should include not only checking the well-formedness using OCL constraints, but also the evaluation of model quality. Software metrics are useful means for evaluating the quality of both software development processes and software products. As models are used to drive the entire software development process it is unlikely that high quality software will be obtained using low quality models. The thesis presents a methodology supported by KMF that uses the UML specification to compute the design metrics at an early stage of software development. The thesis presents a transformation language called YATL (Yet Another Transformation Language), which was designed and implemented to support the features provided by OMG's Request For Proposal and the future QVT standard. YATL is a hybrid language (a mix of declarative and imperative constructions) designed to answer the Query/Views/Transformations Request For Proposals issued by OMG and to express model transformations as required by the Model Driven Architecture (MDA) approach. Several examples of model transformations, which have been implemented using YATL and the support provided by KMF, are presented. These experiments investigate different knowledge areas as programming languages, visual diagrams and distributed systems. YATL was used to implement the following transformations: * UML to Java mapping * Spider diagrams to OCL mapping * EDOC to Web Services
APA, Harvard, Vancouver, ISO, and other styles
2

Kunkel, Robert. "Model Driven Logistics Integration Engineering." Universitätsbibliothek Leipzig, 2012. http://nbn-resolving.de/urn:nbn:de:bsz:15-qucosa-83999.

Full text
Abstract:
Der Logistikdienstleistungssektor ist durch arbeitsteilige sowie kurz-, mittel und langfristige Zusammenarbeit gekennzeichnet. Insbesondere Fourth Party Logistics (4PL) stehen permanent vor der Aufgabe unterschiedliche Logistikdienstleister und damit auch deren Informationssysteme ad-hoc und medienbruchfrei in unternehmensübergreifende Informationsflüsse zu integrieren. Dieser Beitrag stellt verschiedene logistikspezifische Integrationsvarianten, einen modellgetriebenen Integrationsansatz sowie ein Lösungskonzept auf Basis der Logistik Service Engineering & Management (LSEM)-Plattform vor.
APA, Harvard, Vancouver, ISO, and other styles
3

Bucaioni, Alessio. "Bidirectionality in Model-Driven Engineering." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-18202.

Full text
Abstract:
In Model-Driven Engineering bidirectional model transformations emerged as an important ingredient to cope with scenarios such as change propagation, synchronization and to keep consistent system views whenever changes occurring on some view have to be propagated over the others. However, bidirectional mappings open a number of intricate issues that have been only partially solved by research. This master thesis identifies a set of features characterizing bidirectional transformations and validates them against two existing approaches. In particular, a benchmark based on the UML2RDBMS transformation and consisting of two different configurations is implemented by means of two different approaches, such as Triple Graph Grammars and the Janus Transformation Language, for understanding bidirectional transformations with respect to the elicited features.
APA, Harvard, Vancouver, ISO, and other styles
4

Kunkel, Robert. "Model Driven Logistics Integration Engineering." Forschungsberichte des Instituts für Wirtschaftsinformatik der Universität Leipzig Heft 8/15. Interuniversitäres Doktorandenseminar Wirtschaftsinformatik der Universitäten Chemnitz, Dresden, Freiberg, Halle-Wittenberg, Jena und Leipzig, 2011. https://ul.qucosa.de/id/qucosa%3A11353.

Full text
Abstract:
Der Logistikdienstleistungssektor ist durch arbeitsteilige sowie kurz-, mittel und langfristige Zusammenarbeit gekennzeichnet. Insbesondere Fourth Party Logistics (4PL) stehen permanent vor der Aufgabe unterschiedliche Logistikdienstleister und damit auch deren Informationssysteme ad-hoc und medienbruchfrei in unternehmensübergreifende Informationsflüsse zu integrieren. Dieser Beitrag stellt verschiedene logistikspezifische Integrationsvarianten, einen modellgetriebenen Integrationsansatz sowie ein Lösungskonzept auf Basis der Logistik Service Engineering & Management (LSEM)-Plattform vor.
APA, Harvard, Vancouver, ISO, and other styles
5

Adesina, Opeyemi. "Integrating Formal Methods with Model-Driven Engineering." Thesis, Université d'Ottawa / University of Ottawa, 2017. http://hdl.handle.net/10393/36269.

Full text
Abstract:
This thesis presents our method to integrate formal methods with model-driven engineering. Although a large amount of literature exists with the goal of facilitating the adoption of formal methods for educational and industrial practice, yet the adoption of formal methods in academia and industry is poor. The goal of this research is to improve the adoption of formal methods by automating the generation of formal methods code while maintaining scalability and bridging the gaps between formal analysis and actual implementation of the complete system. Our approach is based on generating formal representations of software abstractions expressed in a textual language, called Umple, which is derived from UML. Software abstractions of interest include class models and state machines. For state machines, we address concerns such as composite and concurrent states separately. The resulting systems are analyzable by back-end analysis engines such as Alloy and nuXmv or NuSMV for model checking. To ensure correctness of our approach, we have adopted simulation, empirical studies and rigorous test-driven development (TDD) methodologies. To guarantee correctness of state machine systems under analysis (SSUAs), we present methods to automatically generate specifications to analyze domain-independent properties such as non-determinism and reachability analysis. We apply these methods in various case studies; certify their conformance with sets of requirements and uncover certain flaws. Our contributions include a) The overall approach, involving having the developer write the system in Umple and generating both the formal system for analysis and the final code from the same model; b) a novel approach to encode SSUAs even in the presence of and-cross transitions; c) a fully automated approach to certify an SSUA to be free from nondeterminism even in the presence of unbounded domains and multiple and-cross transitions within the same enclosing orthogonal state; d) an empirical study of the impact of abstraction on some performance parameters; and e) a translator from Umple to Alloy and SMV.
APA, Harvard, Vancouver, ISO, and other styles
6

Kraus, Andreas. "Model Driven Software Engineering for Web Applications." Diss., lmu, 2007. http://nbn-resolving.de/urn:nbn:de:bvb:19-79362.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Gomes, Andrigo, and Andreas Pettersson. "Market-Driven Requirements Engineering Process Model – MDREPM." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3533.

Full text
Abstract:
Research findings in requirements engineering (RE) report that software organizations still struggle in establishing processes that lead to proper requirements handling. This leads to the acknowledgement that the adoption of good requirements engineering practices by industry is still not common. Although some initiatives have been made to spread the use of good practices of bespoke RE, the area of market-driven requirements engineering (MDRE) still lacks a contribution in that direction. MDRE is characterized by strong market and strategic orientation, which contrasts with the customer/development organization relationship of bespoke RE. This poses several challenges to software product organizations, such as the need for aligning development activities with organizational and product strategies. In an attempt to help these organizations to realize the benefits of MDRE, this Master Thesis presents the Market-Driven Requirements Engineering Process Model (MDREPM). MDREPM is both a collection of good practices in MDRE, and an assessment tool for organizations to get a snapshot of the current state of their MDRE practices. The assessment intends to reveal problem areas of organization’s requirements process, which can then be worked upon by introducing good practices described in the model. The thesis describes the motivation for creating MDREPM, both from an academia and industry perspectives. In addition, it describes the process of developing the model, from its creation through to its validation within academia and industry. As the series of three case studies conducted indicate, the MDREPM has been shown to be useful for industry practitioners. A unanimous opinion has been found as to the good coverage it provides of issues related to MDRE, and as to its usefulness for driving improvement efforts in requirements engineering.
APA, Harvard, Vancouver, ISO, and other styles
8

Zolotas, Athanasios. "Type inference in flexible model-driven engineering." Thesis, University of York, 2016. http://etheses.whiterose.ac.uk/16380/.

Full text
Abstract:
Model-driven Engineering (MDE) is an approach to software development that promises increased productivity and product quality. Domain models that conform to metamodels, both of which are the core artefacts in MDE approaches, are manipulated to perform different development processes using specific MDE tools. However, domain experts, who have detailed domain knowledge, typically lack the technical expertise to transfer this knowledge using MDE tools. Flexible or bottom-up Model-driven Engineering is an emerging approach to domain and systems modelling that tackles this challenge by promoting the use of simple drawing tools to increase the involvement of domain experts in MDE processes. In this approach, no metamodel is created upfront but instead the process starts with the definition of example models that will be used to infer a draft metamodel. When complete knowledge of the domain is acquired, a final metamodel is devised and a transition to traditional MDE approaches is possible. However, the lack of a metamodel that encodes the semantics of conforming models and of tools that impose these semantics bears some drawbacks, among others that of having models with nodes that are unintentionally left untyped. In this thesis we propose the use of approaches that use algorithms from three different research areas, that of classification algorithms, constraint programming and graph similarity to help with the type inference of such untyped nodes. We perform an evaluation of the proposed approaches in a number of randomly generated example models from 10 different domains with results suggesting that the approaches could be used for type inference both in an automatic or a semi-automatic style.
APA, Harvard, Vancouver, ISO, and other styles
9

Ed-douibi, Hamza. "Model-driven round-trip engineering of REST APIs." Doctoral thesis, Universitat Oberta de Catalunya, 2019. http://hdl.handle.net/10803/667111.

Full text
Abstract:
Les API web s'han convertit cada vegada més en un actiu clau per a les empreses, que n'han promogut la implementació i la integració en les seves activitats quotidianes. A la pràctica, la majoria d'aquestes API web són "REST-like", que significa que s'adhereixen parcialment a l'estil arquitectònic conegut com transferència d'estat representacional ('representational state transfer', REST en anglés). De fet, REST és un paradigma de disseny i no proposa cap estàndard. Com a conseqüència, tant desenvolupar com consumir API REST són tasques difícils i costoses per als proveïdors i clients de l'API. L'objectiu d'aquesta tesi és facilitar el disseny, la implementació, la composició i el consum de les API REST, basant-se en tècniques d'enginyeria dirigida per models ('model-driven engineering', MDE en anglés). Aquesta tesi proposa les contribucions següents: EMF-REST, APIDiscoverer, APITester, APIGenerator, i APIComposer. Aquestes contribucions constitueixen un ecosistema que avança l'estat de la qüestió al camp de l'enginyeria de programari automàtica per al desenvolupament i el consum de les API REST.
Las API Web se han convertido en una pieza fundamental para un gran número de compañías, que han promovido su implementación e integración en las actividades cotidianas del negocio. En la práctica, estas API Web son "REST-like", lo que significa que se adhieren parcialmente al estilo arquitectónico conocido como transferencia de estado representacional ('representational state transfer', REST en inglés). De hecho, REST es un paradigma de diseño y no propone ningún estándar. Por ello, tanto el desarrollo como el consumo de API REST son tareas difíciles y que demandan mucho tiempo de los proveedores y los clientes de API. El objetivo de esta tesis es facilitar el diseño, la implementación, la composición y el consumo de API REST, apoyándose en el desarrollo de software dirigido por modelos (DSDM). Esta tesis propone las siguientes contribuciones: EMF-REST, APIDiscoverer, APITester, APIGenerator y APIComposer. Estas contribuciones constituyen un ecosistema que avanza el estado de la cuestión en el área de la ingeniería del software referida a la automatización de las tareas relacionadas con el desarrollo y consumo de API REST.
Web APIs have become an increasingly key asset for businesses, and their implementation and integration in companies' daily activities has thus been on the rise. In practice, most of these Web APIs are "REST-like", meaning that they adhere partially to the Representational State Transfer (REST) architectural style. In fact, REST is a design paradigm and does not propose any standard, so developing and consuming REST APIs end up being challenging and time-consuming tasks for API providers and clients. Therefore, the aim of this thesis is to facilitate the design, implementation, composition and consumption of REST APIs by relying on Model-Driven Engineering (MDE). Likewise, it offers the following contributions: EMF-REST, APIDiscoverer, APITester, APIGenerator and APIComposer. Together, these contributions make up an ecosystem which advances the state of the art of automated software engineering for REST APIs.
APA, Harvard, Vancouver, ISO, and other styles
10

Hebig, Regina. "Evolution of model-driven engineering settings in practice." Phd thesis, Universität Potsdam, 2014. http://opus.kobv.de/ubp/volltexte/2014/7076/.

Full text
Abstract:
Nowadays, software systems are getting more and more complex. To tackle this challenge most diverse techniques, such as design patterns, service oriented architectures (SOA), software development processes, and model-driven engineering (MDE), are used to improve productivity, while time to market and quality of the products stay stable. Multiple of these techniques are used in parallel to profit from their benefits. While the use of sophisticated software development processes is standard, today, MDE is just adopted in practice. However, research has shown that the application of MDE is not always successful. It is not fully understood when advantages of MDE can be used and to what degree MDE can also be disadvantageous for productivity. Further, when combining different techniques that aim to affect the same factor (e.g. productivity) the question arises whether these techniques really complement each other or, in contrast, compensate their effects. Due to that, there is the concrete question how MDE and other techniques, such as software development process, are interrelated. Both aspects (advantages and disadvantages for productivity as well as the interrelation to other techniques) need to be understood to identify risks relating to the productivity impact of MDE. Before studying MDE's impact on productivity, it is necessary to investigate the range of validity that can be reached for the results. This includes two questions. First, there is the question whether MDE's impact on productivity is similar for all approaches of adopting MDE in practice. Second, there is the question whether MDE's impact on productivity for an approach of using MDE in practice remains stable over time. The answers for both questions are crucial for handling risks of MDE, but also for the design of future studies on MDE success. This thesis addresses these questions with the goal to support adoption of MDE in future. To enable a differentiated discussion about MDE, the term MDE setting'' is introduced. MDE setting refers to the applied technical setting, i.e. the employed manual and automated activities, artifacts, languages, and tools. An MDE setting's possible impact on productivity is studied with a focus on changeability and the interrelation to software development processes. This is done by introducing a taxonomy of changeability concerns that might be affected by an MDE setting. Further, three MDE traits are identified and it is studied for which manifestations of these MDE traits software development processes are impacted. To enable the assessment and evaluation of an MDE setting's impacts, the Software Manufacture Model language is introduced. This is a process modeling language that allows to reason about how relations between (modeling) artifacts (e.g. models or code files) change during application of manual or automated development activities. On that basis, risk analysis techniques are provided. These techniques allow identifying changeability risks and assessing the manifestations of the MDE traits (and with it an MDE setting's impact on software development processes). To address the range of validity, MDE settings from practice and their evolution histories were capture in context of this thesis. First, this data is used to show that MDE settings cover the whole spectrum concerning their impact on changeability or interrelation to software development processes. Neither it is seldom that MDE settings are neutral for processes nor is it seldom that MDE settings have impact on processes. Similarly, the impact on changeability differs relevantly. Second, a taxonomy of evolution of MDE settings is introduced. In that context it is discussed to what extent different types of changes on an MDE setting can influence this MDE setting's impact on changeability and the interrelation to processes. The category of structural evolution, which can change these characteristics of an MDE setting, is identified. The captured MDE settings from practice are used to show that structural evolution exists and is common. In addition, some examples of structural evolution steps are collected that actually led to a change in the characteristics of the respective MDE settings. Two implications are: First, the assessed diversity of MDE settings evaluates the need for the analysis techniques that shall be presented in this thesis. Second, evolution is one explanation for the diversity of MDE settings in practice. To summarize, this thesis studies the nature and evolution of MDE settings in practice. As a result support for the adoption of MDE settings is provided in form of techniques for the identification of risks relating to productivity impacts.
Um die steigende Komplexität von Softwaresystemen beherrschen zu können, werden heutzutage unterschiedlichste Techniken gemeinsam eingesetzt. Beispiele sind, Design Pattern, Serviceorientierte Architekturen, Softwareentwicklungsprozesse oder modellgetriebene Entwicklung (MDE). Ziel dabei ist die Erhöhung der Produktivität, so dass Entwicklungsdauer und Qualität stabil bleiben können. Während hoch entwickelte Softwareentwicklungsprozesse heute schon standardmäßig genutzt werden, fangen Firmen gerade erst an MDE einzusetzen. Jedoch zeigen Studien, dass der erhoffte Erfolg von MDE nicht jedes Mal eintritt. So scheint es, dass noch kein ausreichendes Verständnis dafür existiert, inwiefern MDE auch Nachteile für die Produktivität bergen kann. Zusätzlich ist bei der Kombination von unterschiedlichen Techniken damit zu rechnen, dass die erreichten Effekte sich gegenseitig negieren anstatt sich zu ergänzen. Hier entsteht die Frage wie MDE und andere Techniken, wie Softwareentwicklungsprozesse, zusammenwirken. Beide Aspekte, der direkte Einfluss auf Produktivität und die Wechselwirkung mit anderen Techniken, müssen aber verstanden werden um den Risiken für den Produktivitätseinfluss von MDE zu identifizieren. Außerdem, muss auch die Generalisierbarkeit dieser Aspekte untersucht werden. Das betrifft die Fragen, ob der Produktivitätseinfluss bei jedem Einsatz von MDE gleich ist und ob der Produktivitätseinfluss über die Zeit stabil bleibt. Beide Fragen sind entscheidend, will man geeignete Risikobehandlung ermöglichen oder künftige Studien zum Erfolg von MDE planen. Diese Dissertation widmet sich der genannten Fragen. Dafür wird zuerst der Begriff MDE Setting'' eingeführt um eine differenzierte Betrachtung von MDE-Verwendungen zu ermöglichen. Ein MDE Setting ist dabei der technische Aufbau, inklusive manueller und automatische Aktivitäten, Artefakten, Sprachen und Werkzeugen. Welche Produktivitätseinflüsse von MDE Settings möglich sind, wird in der Dissertation mit Fokus auf Änderbarkeit und die Wechselwirkung mit Softwareentwicklungsprozessen betrachtet. Dafür wird einerseits eine Taxonomie von Changeability Concerns'' (potentiell betroffene Aspekte von Änderbarkeit) vorgestellt. Zusätzlich, werden drei MDE Traits'' (Charakteristika von MDE Settings die unterschiedlich ausgeprägt sein können) identifiziert. Es wird untersucht welche Ausprägungen dieser MDE Traits Einfluss auf Softwareentwicklungsprozesse haben können. Um die Erfassung und Bewertung dieser Einflüsse zu ermöglichen wird die Software Manufaktur Modell Sprache eingeführt. Diese Prozessmodellierungssprache ermöglicht eine Beschreibung, der Veränderungen von Artefaktbeziehungen während der Anwendung von Aktivitäten (z.B. Codegenerierung). Weiter werden auf Basis dieser Modelle, Analysetechniken eingeführt. Diese Analysetechniken erlauben es Risiken für bestimmte Changeability Concerns aufzudecken sowie die Ausprägung von MDE Traits zu erfassen (und damit den Einfluss auf Softwareentwicklungsprozesse). Um die Generalisierbarkeit der Ergebnisse zu studieren, wurden im Rahmen der Arbeit mehrere MDE Settings aus der Praxis sowie teilweise deren Evolutionshistorien erhoben. Daran wird gezeigt, dass MDE Settings sich in einem breiten Spektrum von Einflüssen auf Änderbarkeit und Prozesse bewegen. So ist es weder selten, dass ein MDE Setting neutral für Prozesse ist, noch, dass ein MDE Setting Einschränkungen für einen Prozess impliziert. Ähnlich breit gestreut ist der Einfluss auf die Änderbarkeit.Zusätzlich, wird diskutiert, inwiefern unterschiedliche Evolutionstypen den Einfluss eines MDE Settings auf Änderbarkeit und Prozesse verändern können. Diese Diskussion führt zur Identifikation der strukturellen Evolution'', die sich stark auf die genannten Charakteristika eines MDE Settings auswirken kann. Mithilfe der erfassten MDE Settings, wird gezeigt, dass strukturelle Evolution in der Praxis üblich ist. Schließlich, werden Beispiele aufgedeckt bei denen strukturelle Evolutionsschritte tatsächlich zu einer Änderung der Charakteristika des betreffenden MDE Settings geführt haben. Einerseits bestärkt die ermittelte Vielfalt den Bedarf nach Analysetechniken, wie sie in dieser Dissertation eingeführt werden. Zum Anderen erscheint es nun, dass Evolution zumindest zum Teil die unterschiedlichen Ausprägungen von MDE Settings erklärt. Zusammenfassend wird studiert wie MDE Settings und deren Evolution in der Praxis ausgeprägt sind. Als Ergebnis, werden Techniken zur Identifikation von Risiken für Produktivitätseinflüsse bereitgestellt um den Einsatz von MDE Settings zu unterstützen.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Model-driven engineering"

1

Deved¿ic, Vladan. Model Driven Engineering and Ontology Development. Berlin, Heidelberg: Springer-Verlag Berlin Heidelberg, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Brambilla, Marco, Jordi Cabot, and Manuel Wimmer. Model-Driven Software Engineering in Practice. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-031-02549-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Khendek, Ferhat, Maria Toeroe, Abdelouahed Gherbi, and Rick Reed, eds. SDL 2013: Model-Driven Dependability Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-38911-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Hammoudi, Slimane, Luís Ferreira Pires, and Bran Selic, eds. Model-Driven Engineering and Software Development. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-11030-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Desfray, Philippe, Joaquim Filipe, Slimane Hammoudi, and Luís Ferreira Pires, eds. Model-Driven Engineering and Software Development. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-27869-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Hammoudi, Slimane, Luís Ferreira Pires, and Bran Selić, eds. Model-Driven Engineering and Software Development. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-37873-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Hammoudi, Slimane, Luís Ferreira Pires, Bran Selic, and Philippe Desfray, eds. Model-Driven Engineering and Software Development. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-66302-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Petriu, Dorina C., Nicolas Rouquette, and Øystein Haugen, eds. Model Driven Engineering Languages and Systems. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16129-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Petriu, Dorina C., Nicolas Rouquette, and Øystein Haugen, eds. Model Driven Engineering Languages and Systems. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16145-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Briand, Lionel, and Clay Williams, eds. Model Driven Engineering Languages and Systems. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11557432.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Model-driven engineering"

1

Topçu, Okan, Umut Durak, Halit Oğuztüzün, and Levent Yilmaz. "Model Driven Engineering." In Simulation Foundations, Methods and Applications, 23–38. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-03050-0_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Shekhar, Shashi, and Hui Xiong. "Model Driven Engineering." In Encyclopedia of GIS, 682. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-35973-1_803.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gaševic, Dragan, Dragan Djuric, and Vladan Devedžic. "Model Driven Engineering." In Model Driven Engineering and Ontology Development, 125–55. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-00282-3_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kent, Stuart. "Model Driven Engineering." In Lecture Notes in Computer Science, 286–98. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-47884-1_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Margaria, Tiziana, Anna-Lena Lamprecht, and Bernhard Steffen. "Continuous Model-Driven Engineering." In Software Technology: 10 Years of Innovation in IEEE Computer, 139–54. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2018. http://dx.doi.org/10.1002/9781119174240.ch8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bézivin, Jean, Nicolas Farcet, Jean-Marc Jézéquel, Benoît Langlois, and Damien Pollet. "Reflective Model Driven Engineering." In Lecture Notes in Computer Science, 175–89. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45221-8_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pan, Yue, Guotong Xie, Li Ma, Yang Yang, ZhaoMing Qiu, and Juhnyoung Lee. "Model-Driven Ontology Engineering." In Journal on Data Semantics VII, 57–78. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11890591_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

van Amstel, Marcel, Mark van den Brand, Zvezdan Protić, and Tom Verhoeff. "Model-Driven Software Engineering." In Automation in Warehouse Development, 45–58. London: Springer London, 2011. http://dx.doi.org/10.1007/978-0-85729-968-0_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Meixner, Gerrit, Marc Seissler, and Kai Breiner. "Model-Driven Useware Engineering." In Studies in Computational Intelligence, 1–26. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-14562-9_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Kordon, Fabrice, Jérôme Hugues, and Xavier Renault. "From Model Driven Engineering to Verification Driven Engineering." In Software Technologies for Embedded and Ubiquitous Systems, 381–93. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-87785-1_34.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Model-driven engineering"

1

Alamin, Khaled, Daniele Jahier Pagliari, Yukai Chen, Enrico Macii, Sara Vinco, and Massimo Poncino. "Model-Driven Feature Engineering for Data-Driven Battery SOH Model." In 2024 Design, Automation & Test in Europe Conference & Exhibition (DATE), 1–6. IEEE, 2024. http://dx.doi.org/10.23919/date58400.2024.10546702.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

van Lamsweerde, Axel. "Model engineering for model-driven engineering." In the 2nd ACM SIGCHI symposium. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1822018.1822020.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gray, Jeff, Jules White, and Aniruddha Gokhale. "Model-driven engineering." In the 48th Annual Southeast Regional Conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1900008.1900010.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Loniewski, Grzogorz, Ausias Armesto, and Emilio Insfran. "An architecture-oriented model-driven requirements engineering approach." In 2011 Model-Driven Requirements Engineering Workshop (MoDRE). IEEE, 2011. http://dx.doi.org/10.1109/modre.2011.6045364.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

"Model Driven Engineering of Cross-Layer Monitoring and Adaptation." In Special Session on Model-driven Software Adaptation. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004375203310340.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Selic, Bran. "From Model-Driven Development to Model-Driven Engineering." In 19th Euromicro Conference on Real-Time Systems (ECRTS'07). IEEE, 2007. http://dx.doi.org/10.1109/ecrts.2007.16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Calegari, Daniel, and Andrea Delgado. "Purpose-driven model-driven engineering education." In MODELS '22: ACM/IEEE 25th International Conference on Model Driven Engineering Languages and Systems. New York, NY, USA: ACM, 2022. http://dx.doi.org/10.1145/3550356.3556503.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Clarisó, Robert, and Jordi Cabot. "Model-Driven Prompt Engineering." In 2023 ACM/IEEE 26th International Conference on Model Driven Engineering Languages and Systems (MODELS). IEEE, 2023. http://dx.doi.org/10.1109/models58315.2023.00020.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Pascal, André. "Case Studies in Model-Driven Reverse Engineering." In 7th International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and Technology Publications, 2019. http://dx.doi.org/10.5220/0007312502560263.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Pascal, André. "Case Studies in Model-Driven Reverse Engineering." In 7th International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and Technology Publications, 2019. http://dx.doi.org/10.5220/0007312502580265.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Model-driven engineering"

1

Tse, Ronald, and Nick Nicholas, eds. OGC Testbed-17: Model-Driven Standards Engineering Report. Open Geospatial Consortium, Inc., March 2022. http://dx.doi.org/10.62973/21-035r1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Feiler, Peter H., Bruce Lewis, and Steve Vestal. The SAE Avionics Architecture Description Language (AADL) Standard: A Basis for Model-Based Architecture-Driven Embedded Systems Engineering. Fort Belvoir, VA: Defense Technical Information Center, April 2003. http://dx.doi.org/10.21236/ada612735.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Dutta, Sourav, Anna Wagner, Theadora Hall, and Nawa Raj Pradhan. Data-driven modeling of groundwater level using machine learning. Engineer Research and Development Center (U.S.), May 2024. http://dx.doi.org/10.21079/11681/48452.

Full text
Abstract:
This US Army Engineer Research and Development Center (ERDC), Coastal and Hydraulics Laboratory engineering technical note (CHETN) documents a preliminary study on the use of specialized machine learning (ML) methods to model the variations in groundwater level (GWL) with time. This approach uses historical groundwater observation data at seven gage locations in Wyoming, USA, available from the USGS database and historical data on several relevant meteorological variables obtained from the ERA5 reanalysis dataset produced by the Copernicus Climate Change Service (usually referred to as C3S) at the European Center for Medium-Range Weather Forecasts to predict future GWL values for a desired period of time. The results presented in this report indicate that the ML method has the potential to predict both short-term (4-hourly) as well as daily variations in GWL several days into the future for the chosen study region, thus alleviating the need for employing sophisticated process-based numerical models with complicated model structure configurations.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Model-driven engineering' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography