Relevant bibliographies by topics / Model Driven Development (MDD)

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Model Driven Development (MDD)'

Author: Grafiati
Published: 4 June 2021
Last updated: 18 June 2025

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Model Driven Development (MDD).'

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 Development (MDD)"

1

Pérez, Jennifer, Isidro Ramos, Jose Carsí, and Cristóbal Costa-Soria. "Model-Driven Development of Aspect-Oriented Software Architectures." JUCS - Journal of Universal Computer Science 19, no. (10) (2013): 1433–73. https://doi.org/10.3217/jucs-019-10-1433.

Full text
Abstract:
The Model-Driven Development (MDD) paradigm has become widely spread in the last few years due to being based on models instead of source code, and using automatic generation techniques to obtain the final software product. Until now, the most mature methodologies that have been proposed to develop software following MDD are mainly based on functional requirements by following the Object-Oriented Paradigm. Therefore, mature MDD methodologies are required for supporting the code generation from models that specify non-functional requirements. The Aspect-Oriented Software Development (AOSD) approach was created to provide explicit mechanisms for developing non-functional requirements through reusable elements called aspects. Aspect-Oriented Software Architectures (AOSA) emerged to deal with the design of both, functional requirements and non-functional requirements, which opened an important challenge in the software engineering field: the definition of a methodology for supporting the development of AOSAs following the MDD paradigm. This new methodology should allow the code generation from models which specify functional and non-functional requirements. This paper presents a mature approach, called PRISMA, which deals with this challenge. Therefore, this contribution takes a step forward in the area presenting in detail the PRISMA MDD process, which has been applied to generate the code of several real applications of the tele-operated robotics domain. PRISMA MDD approach provides complete support for the development of technology-independent AOSAs, which can be compiled from high-level, aspect-oriented architectural models into different technology platforms and languages following an MDD process. This contribution illustrates how to apply the PRISMA MDD approach through the modelling framework that has been developed to support it, and a case study of a tele-operated robot that has been completely developed using this approach. Finally, the results obtained from the application of PRISMA MDD process to develop applications of the tele-operation domain are analyzed in terms of code generation.
APA, Harvard, Vancouver, ISO, and other styles
2

Giachetti, Giovanni, Manuela Albert, Beatriz Marín, and Oscar Pastor. "Linking UML and MDD through UML Profiles: a Practical Approach based on the UML Association." JUCS - Journal of Universal Computer Science 16, no. (17) (2010): 2353–73. https://doi.org/10.3217/jucs-016-17-2353.

Full text
Abstract:
In a model-driven development context, the definition (or selection) of an appropriate modeling language is a crucial task. OMG, in the model-driven architecture specification, recommends the use of UML for model-driven developments. However, the lack of semantic precision in UML has led to different model-driven approaches proposing their own domain-specific modeling languages in order to introduce their modeling needs. This paper focuses on customizing the UML association in order to facilitate its application in model-driven development environments. To do this, a well-defined process is defined to integrate the abstract syntax of a domain-specific modeling language that supports a precise semantics for the association construct in UML by means of the automatic generation of a UML profile. Finally, a brief example shows how the results obtained by the application of the proposed process can generate software products through a real model compilation tool.
APA, Harvard, Vancouver, ISO, and other styles
3

Kardas, Geylani. "Model-driven development of multiagent systems: a survey and evaluation." Knowledge Engineering Review 28, no. 4 (2013): 479–503. http://dx.doi.org/10.1017/s0269888913000088.

Full text
Abstract:
AbstractTo work in a higher abstraction level is of critical importance for the development of multiagent systems (MAS) since it is almost impossible to observe code-level details of such systems due to their internal complexity, distributedness and openness. As one of the promising software development approaches, model-driven development (MDD) aims to change the focus of software development from code to models. This paradigm shift, introduced by the MDD, may also provide the desired abstraction level during the development of MASs. For this reason, MDD of autonomous agents and MASs has been recognized and become one of the research topics in agent-oriented software engineering (AOSE) area. Contributions are mainly based on the model-driven architecture (MDA), which is the most famous and in-use realization of MDD. Within this direction, AOSE researchers define MAS metamodels in various abstraction levels and apply model transformations between the instances of these metamodels in order to provide rapid and efficient implementation of the MASs in various platforms. Reorganization of the existing MAS development methodologies to support model-driven agent development is another emerging research track. In this paper, we give a state of the art survey on above mentioned model-driven MAS development research activities and evaluate the introduced approaches according to five quality criteria we define on model-driven MAS engineering: (1) definition of a platform independent MAS metamodel, (2) model-to-model transformability, (3) model-to-code transformability, (4) support for multiple MAS platforms and finally (5) tool support for software modeling and code generation. Our evaluation has shown that the researchers contributed to the area by providing MDD processes in which design of the MASs are realized at a very high abstraction level and the software for these MASs are developed as a result of the application of a series of model transformations. However, most of the approaches are incapable of supporting multiple MAS environments due to the restricted specifications of their metamodels and model transformations. Also efficiency and practicability of the proposed methodologies are under debate since the amount and quality of the executable MAS components, gained automatically, appear to be not sufficient.
APA, Harvard, Vancouver, ISO, and other styles
4

Knodel, Jens, Michalis Anastasopolous, Thomas Forster, and Dirk Muthig. "An Efficient Migration to Model-driven Development (MDD)." Electronic Notes in Theoretical Computer Science 137, no. 3 (2005): 17–27. http://dx.doi.org/10.1016/j.entcs.2005.07.002.

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

Umran Alrubaee, Afrah, Deniz Cetinkaya, Gernot Liebchen, and Huseyin Dogan. "A Process Model for Component-Based Model-Driven Software Development." Information 11, no. 6 (2020): 302. http://dx.doi.org/10.3390/info11060302.

Full text
Abstract:
Developing high quality, reliable and on time software systems is challenging due to the increasing size and complexity of these systems. Traditional software development approaches are not suitable for dealing with such challenges, so several approaches have been introduced to increase the productivity and reusability during the software development process. Two of these approaches are Component-Based Software Engineering (CBSE) and Model-Driven Software Development (MDD) which focus on reusing pre-developed code and using models throughout the development process respectively. There are many research studies that show the benefits of using software components and model-driven approaches. However, in many cases the development process is either ad-hoc or not well-defined. This paper proposes a new software development process model that merges CBSE and MDD principles to facilitate software development. The model is successfully tested by applying it to the development of an e-learning system as an exemplar case study.
APA, Harvard, Vancouver, ISO, and other styles
6

Vera, Pablo Martin. "Component Based Model Driven Development." International Journal of Information Technologies and Systems Approach 8, no. 2 (2015): 80–100. http://dx.doi.org/10.4018/ijitsa.2015070106.

Full text
Abstract:
Current MDD methodologies are complex to use and require doing lots of models and configurations. Usually after all that effort only some part of the application source code can be automatically created. It would be desirable to have a more simple technique, but powerful enough for automatically creating a fully functional application. This works introduces a component based model driven development approach where a set of user interface components will be configured to define system behavior. Component configuration will be direct, simple and supported by a modeling tool which also includes automatic transformations for reducing the modeling task. The methodology requires the designer to build only two models: a class diagram, representing the data model of the application and a component diagram defining the user interface and the system navigation. Both components are based on UML extended with stereotypes and tagged values allowing configuring the system behavior.
APA, Harvard, Vancouver, ISO, and other styles
7

Waluyo, Prihadi Beny, Gani Indriyanta, and Karel Tampubolon. "Pengaruh Pendekatan Test Driven, Behavior Driven dan Model Driven terhadap Pengembangan Perangkat Lunak Metode Scrum." Jurnal Terapan Teknologi Informasi 8, no. 2 (2025): 111–16. https://doi.org/10.21460/jutei.2024.82.385.

Full text
Abstract:
Penelitian ini mengkaji pengaruh pengintegrasian metodologi Test-Driven Development (TDD), Behavior-Driven Development (BDD), dan Model-Driven Development (MDD) dalam kerangka kerja Scrum terhadap efektivitas dan efisiensi dalam pengembangan perangkat lunak. Melalui analisis literatur yang komprehensif, penelitian ini mengeksplorasi bagaimana setiap metodologi memperkuat aspek tertentu dari proses Scrum. TDD ditemukan meningkatkan keandalan dan akurasi pengembangan dengan penekanan pada pengujian berkelanjutan, sedangkan BDD memperbaiki komunikasi dan kolaborasi antar stakeholder dengan menggunakan bahasa yang jelas dan mudah dipahami. MDD menyediakan mekanisme efisien untuk mengatasi desain sistem yang kompleks melalui model abstrak yang secara otomatis diubah menjadi kode. Hasil studi menunjukkan bahwa integrasi ketiga metodologi ini menawarkan peningkatan signifikan dalam kualitas dan kecepatan pengembangan, dengan memanfaatkan kekuatan spesifik dari setiap metodologi untuk mengoptimalkan siklus pengembangan dalam proyek Scrum. Implikasi dari temuan ini relevan bagi praktisi yang berkecimpung dalam pengembangan perangkat lunak Agile serta bagi akademisi yang tertarik dalam penelitian metodologi pengembangan lebih lanjut.
APA, Harvard, Vancouver, ISO, and other styles
8

Ormeño, Yeshica Isela, Jose Ignacio Panach, Nelly Condori-Fernández, and Óscar Pastor. "A Proposal to Elicit Usability Requirements within a Model-Driven Development Environment." International Journal of Information System Modeling and Design 5, no. 4 (2014): 1–21. http://dx.doi.org/10.4018/ijismd.2014100101.

Full text
Abstract:
Nowadays there are sound Model-Driven Development (MDD) methods that deal with functional requirements, but in general, usability is not considered from the early stages of the development. Analysts that work with MDD implement usability features manually once the code has been generated. This manual implementation contradicts the MDD paradigm and it may involve much rework. This paper proposes a method to elicit usability requirements at early stages of the software development process such a way non-experts at usability can use it. The approach consists of organizing several interface design guidelines and usability guidelines in a tree structure. These guidelines are shown to the analyst through questions that she/he must ask to the end-user. Answers to these questions mark the path throughout the tree structure. At the end of the process, the paper gathers all the answers of the end-user to obtain the set of usability requirements. If it represents usability requirements according to the conceptual models that compose the framework of a MDD method, these requirements can be the input for next steps of the software development process. The approach is validated with a laboratory demonstration.
APA, Harvard, Vancouver, ISO, and other styles
9

Bibbo, Luis Mariano, Claudia Pons, and Roxana Giandini. "Model-Driven Development of Groupware Systems." International Journal of e-Collaboration 18, no. 1 (2022): 1–28. http://dx.doi.org/10.4018/ijec.295151.

Full text
Abstract:
Building Collaborative systems with awareness (or groupware) is a very complex task. This article presents the use of the domain specific language CSSL v2.0 - Collaborative Software System Language -built as an extension of UML, using the metamodeling mechanism. CSSL provides simplicity, expressiveness and precision to model the main concepts of collaborative systems, especially collaborative processes, protocols and awareness.The CSSL concrete syntax is defined via a set of editors through which collaborative systems models are created. According to the MDD methodology, models are independent of the implementation platform and are formally prepared to be transformed. The target of the transformation is a web application that provides a set of basic functions that developers can refine to complete the development of the collaborative system. Finally, evaluation, validation and verification of the language is performed, determining that the CSSL tools allow developers to solve central aspects of collaborative systems implementation in a simple and reasonable way.
APA, Harvard, Vancouver, ISO, and other styles
10

André, Pascal, and Mohammed El Amin Tebib. "Assistance in Model Driven Development: Toward an Automated Transformation Design Process." Complex Systems Informatics and Modeling Quarterly, no. 38 (April 30, 2024): 54–99. http://dx.doi.org/10.7250/csimq.2024-38.03.

Full text
Abstract:
Model driven engineering aims to shorten the development cycle by focusing on abstractions and partially automating code generation. We long lived in the myth of automatic Model Driven Development (MDD) with promising approaches, techniques, and tools. Describing models should be a main concern in software development as well as model verification and model transformation to get running applications from high level models. We revisit the subject of MDD through the prism of experimentation and open mindness. In this article, we explore assistance for the stepwise transition from the model to the code to reduce the time between the analysis model and implementation. The current state of practice requires methods and tools. We provide a general process and detailed transformation specifications where reverse-engineering may play its part. We advocate a model transformation approach in which transformations remain simple, the complexity lies in the process of transformation that is adaptable and configurable. We demonstrate the usefulness, and scalability of our proposed MDD process by conducting experiments. We conduct experiments within a simple case study in software automation systems. It is both representative and scalable. The models are written in UML; the transformations are implemented mainly using ATL, and the programs are deployed on Android and Lego EV3. Last we report the lessons learned from experimentation for future community work.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Model Driven Development (MDD)"

1

Shappee, Bartlett A. "Test First Model-Driven Development." Digital WPI, 2012. https://digitalcommons.wpi.edu/etd-theses/339.

Full text
Abstract:
Test Driven Development (TDD), Model-Driven Development (MDD), and Test Case Generation with their associated practices and tools each in their own right promise to deliver robust higher quality code more economically then other approaches. These process are not mutually exclusive but are not typically used together. This thesis develops a combined approach using complimentary aspects of each of the above three process. Test cases are described, generated, and then injected back into the model, which is then used to produce the test and production code. We have enhanced a model-driven tool to support the approach, adding a test case generator, capable of understanding augmented MDD software model and utilizing the constraints captured in our test-centric language to generate model-level test cases back into the model. Our results show that, with a reduction in overall effort one can produce a tested model-based system in which its test and implementation for multiple platforms such as C and Java, using one of multiple test xUnit frameworks.
APA, Harvard, Vancouver, ISO, and other styles
2

Waldemarin, Ricardo Cacheta. "Suporte ao desenvolvimento e à integração de ontologias no domínio biomédico." Universidade de São Paulo, 2015. http://www.teses.usp.br/teses/disponiveis/95/95131/tde-18112015-100645/.

Full text
Abstract:
O surgimento e o uso crescente de novas tecnologias têm levado à produção e armazenamento de grandes volumes de dados biomédicos. Tais dados são provenientes de diferentes técnicas, armazenados em formatos de representação diversos e utilizados por diferentes ferramentas. Esta heterogeneidade representa um empecilho ao maior uso desses dados em abordagens integrativas de pesquisa como, por exemplo, a biologia sistêmica. Neste cenário, artefatos de modelagem conceitual, tais como ontologias, têm sido utilizados para organizar e integrar dados heterogêneos de uma forma coerente. A OBO Foundry representa, atualmente, o maior esforço no desenvolvimento de ontologias biomédicas de forma colaborativa. Dentre as ontologias desenvolvidas pela OBO Foundry, destaca-se Ontologia de Relacionamentos (RO-OBO). A RO-OBO provê definições formais para um conjunto de relacionamentos de propósito geral utilizados nas ontologias biomédicas e busca promover a criação de ontologias mais corretas e integráveis. Um perfil UML foi proposto para representar formalmente o conjunto de conceitos e relacionamentos existentes na RO-OBO. Este perfil permite desenvolver modelos UML utilizando os conceitos presentes nesta ontologia, bem como torna possível o desenvolvimento de suporte à validação sintática dos modelos criados em relação a um conjunto de restrições formalmente definidas. Adicionalmente, percebe-se na literatura que o suporte à integração de modelos UML e ontologias OBO, em particular as ontologias representadas na linguagem OBO File Format, é limitado. Neste sentido, este trabalho teve como objetivo geral investigar o suporte ao desenvolvimento de ontologias biomédicas na linguagem UML. De forma específica, investigou-se o desenvolvimento de um editor gráfico, chamado OBO-RO Editor, para o suporte à construção de ontologias utilizando o perfil UML proposto, bem como a integração de ontologias desenvolvidas utilizando UML e ontologias desenvolvidas na linguagem OBO File Format. De forma a atingir nossos objetivos, uma arquitetura de referência foi definida e um processo de desenvolvimento orientado a modelos foi utilizado. A arquitetura definida é composta por uma série de artefatos inter-relacionados os quais são transformados (semi) automaticamente em código de aplicação, possibilitando a obtenção de ciclos de desenvolvimento mais rápidos e confiáveis. O OBO-RO Editor disponibiliza um conjunto de elementos gráficos de modelagem definidos a partir do perfil UML proposto, bem como provê mecanismos para a validação sintática (semi) automática de uma ontologia desenvolvida segundo as restrições definidas neste perfil. Adicionalmente, o OBO-RO Editor também provê suporte à integração de modelos UML a outras ontologias da OBO Foundry, permitindo o reuso e o desenvolvimento menos propenso a erros de ontologias no domínio biomédico.<br>The development and increasing use of new technologies has resulted in the production and storage of a huge amount of biomedical data. These data are produced using different techniques, stored in different formats and consumed by different (software) tools. This heterogeneity hinders effective data usage in integrative research approaches, including systems biology. In this scenario, conceptual modeling artifacts, such as ontologies, have been used to organize and integrate heterogeneous data in a coherent manner. Nowadays, the OBO Foundry represents the most important effort for the collaborative development of ontologies in the biomedical domain. The OBO Relation Ontology (OBO-RO) can be considered one of the most relevant ontologies in the domain. This ontology provides formal definitions for a number of general purpose relationships used in biomedical ontologies, thus facilitating the integration of existing ontologies and the development of new ontologies in the domain. An UML profile has been proposed to formally define the different types of concepts and relationships provided by the OBO-RO. This profile enables the creation of UML models using such concepts and allows the development of support for the automatic validation of these models based on formal constraints. Additionally, the support for the integration between UML models and OBO ontologies, particularly ontologies represented using the OBO File Format, is limited. In this sense, this project aimed at investigating the support for the development of biomedical ontologies using UML. In particular, we investigated the development of a graphical editor, named OBO-RO Editor, to support ontology development using the proposed UML profile. Additionally, we also investigated the integration of ontologies developed using UML and ontologies developed using the OBO File Format. In order to achieve our goals, we have defined a reference architecture and a model-driven development process. The reference architecture consists of a number of related artifacts that are transformed to application code (semi) automatically. Such characteristic allowed us to obtain faster and more reliable development cycles. The OBO-RO Editor provides a number of graphical elements defined in the proposed UML profile for the modeling of biomedical ontologies and support the (semi) automatic syntactic validation of such ontologies against the contraints defined in the profile. Additionally, OBO-RO Editor also provides support for the integration of developed UML models and other OBO ontologies, allowing the reuse and the accurate development of biomedical ontologies.
APA, Harvard, Vancouver, ISO, and other styles
3

Belix, José Eduardo. "Um estudo sobre MDA: suporte fornecido pela UML e reuso de soluções pré-definidas." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-11052006-165548/.

Full text
Abstract:
Este trabalho tem por objetivo propor a utilização de soluções pré-definidas e comprovadas na abordagem MDA, auxiliando o desenvolvedor na resolução de problemas recorrentes ao desenvolvimento de software. A utilização destas soluções pré-definidas leva a um aumento de produtividade no contexto MDA e na geração de software baseado em boas práticas. Para que este objetivo seja cumprido, é empreendida uma análise sobre o MDA e sobre como operacionalizar as transformações entre modelos. Também é empreendida uma análise sobre o suporte fornecido pela UML e sobre reutilização em desenvolvimento orientado a modelos. Por fim este trabalho apresenta partes de uma aplicação protótipo, construída para ser uma prova de conceito de código gerado através da combinação de UML e soluções pré-definidas.<br>The goal of this work is to propose the use of pre-defined solutions on MDA approach, supporting the developer in solving recurrent problems of software development. The use of these pre-defined solutions leads to an increase of productivity in MDA context, and in the generation of software based on best practices. To reach this goal, an analysis of MDA is undertaken, as well as an analysis of how to enable the transformations between models. It is also undertaken an analysis about the use of UML and the reuse in model driven development. Finally this work presents portions of a prototype application, constructed to be a proof-of-concept of generated code, combining UML and the pre-defined solutions.
APA, Harvard, Vancouver, ISO, and other styles
4

Zikra, Iyad. "Integration of Enterprise Modeling and Model Driven Development : A Meta-Model and a Tool Prototype." Licentiate thesis, Stockholms universitet, Institutionen för data- och systemvetenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:su:diva-103698.

Full text
Abstract:
The use of models for designing and developing Information Systems (IS) has changed in recent years. Models are no longer considered a peripheral documentation medium that is poorly maintained and often neglected. Rather, models are increasingly seen as essential parts of the final product—as central artifacts that drive and guide the development efforts. The knowledge that modelers rely on when designing models is represented as formal models and clearly defined rules for transforming the models. The flexibility, reliability, and effectiveness offered by the formal models and the transformations are making Model Driven Development (MDD) a popular choice for building IS. Models also serve in describing enterprise design, where enterprise-level models capture organizational knowledge and aid in understanding, improving, and growing the enterprise. Enterprise Modeling (EM) offers a structured and unified view of the enterprise, thereby enabling more informed and accurate decisions to be made. Many MDD approaches have been proposed to tackle a wide range of IS-related issues, but little attention is being paid to the source of the knowledge captured by the IS models. EM approaches capture organizational knowledge and provide the necessary input and underlying context for designing IS. However, the results produced by EM approaches need to be manually analyzed by modelers to create the initial MDD model. This interruption of the MDD process represents a gap between enterprise models and MDD models. Limited research has been done to connect EM to MDD in a systematic and structured manner based on the principles of model-driven development. This thesis proposes a unifying meta-model for integrating EM and MDD. The meta-model captures the inherent links that exist between organizational knowledge and IS design. This helps to improve the alignment between organizational goals and the IS that are created to support them. The research presented herein follows the guidelines of the design science research methodology. It starts with a state-of-the-art survey of the current relationship between MDD and prior stages of development. The findings of the survey are used to elicit a set of necessary properties for integrating EM and MDD. The unifying meta-model is then proposed as the basis for an integrated IS development approach that applies the principles of MDD and starts on the enterprise level by considering enterprise models in the development process. The design of the meta-model supports the elicited integration properties. The unifying meta-model is based on the Enterprise Knowledge Development (EKD) approach to EM. A prototype tool is developed to support the unifying meta-model, following a study to choose a suitable implementation environment. The use of the unifying meta-model is demonstrated through the implemented tool platform using an example case study, revealing its advantages and highlighting the potential for improvement and future development.
APA, Harvard, Vancouver, ISO, and other styles
5

Johannes, Jendrik. "Component-Based Model-Driven Software Development." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2011. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-63986.

Full text
Abstract:
Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD. We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD). For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models. To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework. To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.
APA, Harvard, Vancouver, ISO, and other styles
6

Baerisch, Stefan. "Domain-specific model-driven testing." Wiesbaden Vieweg + Teubner, 2009. http://d-nb.info/995466882/04.

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

LIBÓRIO, Luiz Felipe de Oliveira. "Desenvolvimento baseado em modelos de ferramentas para avaliação da aderência de processos de software em relação a modelos de maturidade." Universidade Federal de Pernambuco, 2014. https://repositorio.ufpe.br/handle/123456789/17729.

Full text
Abstract:
Submitted by Irene Nascimento (irene.kessia@ufpe.br) on 2016-08-22T18:54:13Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DissertacaoCD_LuizFelipeLiborio.pdf: 3777707 bytes, checksum: a7937e9fc359d5b560c37ea3abf5e74c (MD5)<br>Made available in DSpace on 2016-08-22T18:54:13Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DissertacaoCD_LuizFelipeLiborio.pdf: 3777707 bytes, checksum: a7937e9fc359d5b560c37ea3abf5e74c (MD5) Previous issue date: 2014-08-27<br>Capes<br>Atualmente, é cada vez mais exigido como critério competitivo a aderência do processo de software de uma organização a um modelo ou norma de qualidade. Alcançar altos níveis de aderência é uma tarefa complexa para as organizações, pois a atividade de avaliar essa aderência exige cuidado ao ser realizada. Com isso, busca-se cada vez mais o apoio de ferramentas de avaliação computadorizadas, cujo objetivo é agilizar e tornar mais confiável o processo de avaliação dos processos de software. Ainda assim, um dos fatores que tendem a dificultar a utilização e propagação do uso de ferramentas é a atualização das normas de qualidade e dos métodos de avaliação associados, que visam se adequar constantemente às boas práticas do mercado. Ora, se uma ferramenta é criada baseada na norma de qualidade e no seu método de avaliação, qualquer mudança em algum dos dois componentes significa mudanças na ferramenta, gerando custos de manutenção e de distribuição da nova versão da ferramenta. Este trabalho busca criar uma engine de geração que seja sensível a esses mudanças, sem que seu processo de desenvolvimento necessite ser executado novamente. Para isto, utiliza o processo MDD (Model-Driven Development) para atender a esses requisitos, dado que o seu objetivo é transformar elementos mais abstratos em elementos mais concretos utilizando uma sucessão de transformações, através de modelos. O objetivo deste trabalho é, então, aplicar as regras de MDD aos modelos de qualidade e métodos de avaliação. Isto torna possível a criação de ferramentas para avaliação baseada nos modelos necessários à avaliação. Ou seja, através de um modelo de processo e de um metamodelo da norma de qualidade, além do método de avaliação, é possível criar de forma automática via MDD uma ferramenta que possa ser atualizada sob demanda, sem que seu código-fonte precise ser alterado manualmente.<br>Nowadays, it is increasingly required as a competitive criteria the adherence of an organization to a software model or quality standard process. Achieving high levels of adherence is a complex task for organizations, because the activity of evaluating this adherence requires care to be performed. Thus, it is increasing the nedd of computerized evaluation tools whose goal is to speed up and make more reliable the process of evaluating software processes.Still, one of the factors that tend to hamper the use and propagation of tool use is the change of the quality standards and assessment methods, which aim to adapt constantly to best practices in the market. So, if a tool is created based on quality standard and its evaluation method, any change in any of the two components mean changes in the tool, generating costs of maintaining and distributing the new version of the tool. This work seeks to develop a tool that is sensitive to that changes, but without the need of performing its development process again. For that, it uses MDD (Model- Driven Development) processes meet these requirements, since their goal is to transform more abstract elements into more concrete elements using a succession of transformations, through models. So, the goal of this work is to apply the rules of MDD to quality models and assessment methods. It makes possible to create tools based on models. In other words, through a process model and a metamodel quality standard, besides the evaluation method, it is possible to create automatically via MDD a tool that can be updated on demand, without its source code need to be changed manually.
APA, Harvard, Vancouver, ISO, and other styles
8

SILVA, Edson Alves da. "Um catálogo de regras para transformação automática de esquemas EER em código SQL-Relacional: uma visão MDD com foco em restrições estruturais não triviais." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/18303.

Full text
Abstract:
Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-13T15:18:50Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) [dsc] Edson Alves v.1.5.6.pdf: 4201919 bytes, checksum: c682b493376c27a9896e5215c62283a1 (MD5)<br>Made available in DSpace on 2017-02-13T15:18:50Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) [dsc] Edson Alves v.1.5.6.pdf: 4201919 bytes, checksum: c682b493376c27a9896e5215c62283a1 (MD5) Previous issue date: 2015-03-02<br>CNPq<br>Model Driven Development (MDD) é um paradigma para geração automática de código executável que utiliza modelos como o seu artefato primário. No escopo de Banco de Dados, apesar das regras para transformação de esquemas Enhanced Entity Relationship (EER) em código da Structured Query Language (SQL)-Relacional já terem sido amplamente exploradas na literatura, não se encontrou um trabalho que ao mesmo tempo especifique tradutores MDD capazes de transformar, automaticamente, esquemas EER em códigos SQL-Relacional e aborde restrições como: Participação em Relacionamento, Disjunção e Completude em Herança ou Categoria são transformadas em estruturas SQL-Relacional. Neste contexto, visando dar uma contribuição às limitações mencionadas, esta dissertação apresenta duas macros contribuições: 1) um Catálogo de regras para transformar um esquema EER em um esquema Relacional e este em código SQL; e 2) um algoritmo que especifica uma ordem correta para a execução automática destas regras. De modo a mostrar a viabilidade e aplicação prática deste trabalho, o Catálogo de regras de transformação e o algoritmo para automatização do Catálogo são codificados na linguagem Query/View/Transformation-Relations (QVT-R) e implementados na ferramenta EERCASE. A avaliação do trabalho foi feita a partir da transformação de esquemas EER (não triviais) em códigos SQLRelacional, os quais são conferidos por especialistas de Banco de Dados. Por fim, comparando o trabalho proposto com os trabalhos relacionados investigados, constatou-se que o trabalho desta dissertação avança o estado da arte, pois é o único que é baseado em MDD e garante que as restrições de Participação em Relacionamento, Disjunção e Completude em Herança ou Categoria sejam automaticamente geradas para serem garantidas diretamente pelo Sistema de Gerenciamento de Banco de Dados.<br>Model Driven Development (MDD) is a paradigm for automatic generation of executable code that uses models as its primary artifact. In the database scope, despite the rules for transformation of Enhanced Entity Relationship (EER) schemas in code of Structured Query Language (SQL)-Relational have already been widely explored in the literature, we did not find a work that, at the same time, specifies MDD translators capable of transforming, automatically, EER schemas in SQL-Relational codes and addresses restrictions such as: Participation in Relationship, Disjunction and Completeness in Inheritance or Category are transformed into SQL-relational structures. In this context, in order to contribute for the mentioned limitations, this dissertation presents two macro contributions: 1) a rule Catalog to transform an EER schema into a Relational schema and this SQL code; and 2) an algorithm that specifies a correct order for the automatic enforcement of these rules. In order to show the feasibility and practical application of this work, the Catalog of transformation rules and the algorithm for Catalog automation are encoded in Query/View/TransformationRelations (QVT-R) language and implemented in EERCASE tool. The evaluation of the work was made from the processing of EER schemas (nontrivial) in SQL-Relational codes, which are conferred by database experts. Finally, comparing the proposed work with the related work investigated, it was found that the proposed work advances the state of the art, as it is the only one that is based on MDD and ensures that the restrictions on Participation in Relationship, Disjunction in Inheritance and Completeness in Inheritance or Category are guaranteed by the Database Management System.
APA, Harvard, Vancouver, ISO, and other styles
9

SINDICO, ANDREA. "Model driven development of context aware software systems." Doctoral thesis, Università degli Studi di Roma "Tor Vergata", 2009. http://hdl.handle.net/2108/1018.

Full text
Abstract:
In questa tesi viene descritto il lavoro svolto nella realizzazione di un framework model driven per la progettazione e lo sviluppo di sistemi software context aware ovvero capaci di adattare il proprio comportamento in funzione delle informazioni afferenti ad un "contesto" percepito. Il framework si basa su due linguaggi di modellazione e programmazione "domain specific", CAMEL (Context Aware ModEling Language) e JCOOL (Java COntext Oriented Language), appositamente definiti e per i quali sono stati sviluppati editor ed interpreti. L'obiettivo è quello di poter fornire al progettista strumenti che permettano di meglio gestire la progettazione di comportamenti dipendenti dal contesto anche rispetto a sistemi già esistenti.<br>With the aim to provide a contribute toward a major comprehension of the context awareness issues in software engineering in this thesis we present a modeling framework that can be used by engineers to model systems’ context aware characteristics independently of the possible implementation they could have. To this end we have appositely defined proper domain specific modeling and programming languages, respectively named CAMEL (Context Aware ModEling Language) and JCOOL (Java COntext Oriented Language), which allow the designer to be focused on the information related to the entities involved into the realization of a context aware behaviour making easy to share his/her understanding of such concern with other designers or developers. Moreover our modeling approach is based on aspect oriented modeling techniques so that it is possible to model context aware behaviours for already existing systems without having to modify their original models but only referring to their elements. Models based on this framework can be therefore object of transformation processes aimed at producing usefull artifacts such as: metrics or other measurments giving the designer feedbacks about his/her desigin choices; documentation which can be shared with the system’s stakeholders; code which actually implements them.
APA, Harvard, Vancouver, ISO, and other styles
10

Lochmann, Henrik. "HybridMDSD: Multi-Domain Engineering with Model-Driven Software Development using Ontological Foundations." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2010. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-27380.

Full text
Abstract:
Software development is a complex task. Executable applications comprise a mutlitude of diverse components that are developed with various frameworks, libraries, or communication platforms. The technical complexity in development retains resources, hampers efficient problem solving, and thus increases the overall cost of software production. Another significant challenge in market-driven software engineering is the variety of customer needs. It necessitates a maximum of flexibility in software implementations to facilitate the deployment of different products that are based on one single core. To reduce technical complexity, the paradigm of Model-Driven Software Development (MDSD) facilitates the abstract specification of software based on modeling languages. Corresponding models are used to generate actual programming code without the need for creating manually written, error-prone assets. Modeling languages that are tailored towards a particular domain are called domain-specific languages (DSLs). Domain-specific modeling (DSM) approximates technical solutions with intentional problems and fosters the unfolding of specialized expertise. To cope with feature diversity in applications, the Software Product Line Engineering (SPLE) community provides means for the management of variability in software products, such as feature models and appropriate tools for mapping features to implementation assets. Model-driven development, domain-specific modeling, and the dedicated management of variability in SPLE are vital for the success of software enterprises. Yet, these paradigms exist in isolation and need to be integrated in order to exhaust the advantages of every single approach. In this thesis, we propose a way to do so. We introduce the paradigm of Multi-Domain Engineering (MDE) which means model-driven development with multiple domain-specific languages in variability-intensive scenarios. MDE strongly emphasize the advantages of MDSD with multiple DSLs as a neccessity for efficiency in software development and treats the paradigm of SPLE as indispensable means to achieve a maximum degree of reuse and flexibility. We present HybridMDSD as our solution approach to implement the MDE paradigm. The core idea of HybidMDSD is to capture the semantics of particular DSLs based on properly defined semantics for software models contained in a central upper ontology. Then, the resulting semantic foundation can be used to establish references between arbitrary domain-specific models (DSMs) and sophisticated instance level reasoning ensures integrity and allows to handle partiucular change adaptation scenarios. Moreover, we present an approach to automatically generate composition code that integrates generated assets from separate DSLs. All necessary development tasks are arranged in a comprehensive development process. Finally, we validate the introduced approach with a profound prototypical implementation and an industrial-scale case study<br>Softwareentwicklung ist komplex: ausführbare Anwendungen beinhalten und vereinen eine Vielzahl an Komponenten, die mit unterschiedlichen Frameworks, Bibliotheken oder Kommunikationsplattformen entwickelt werden. Die technische Komplexität in der Entwicklung bindet Ressourcen, verhindert effiziente Problemlösung und führt zu insgesamt hohen Kosten bei der Produktion von Software. Zusätzliche Herausforderungen entstehen durch die Vielfalt und Unterschiedlichkeit an Kundenwünschen, die der Entwicklung ein hohes Maß an Flexibilität in Software-Implementierungen abverlangen und die Auslieferung verschiedener Produkte auf Grundlage einer Basis-Implementierung nötig machen. Zur Reduktion der technischen Komplexität bietet sich das Paradigma der modellgetriebenen Softwareentwicklung (MDSD) an. Software-Spezifikationen in Form abstrakter Modelle werden hier verwendet um Programmcode zu generieren, was die fehleranfällige, manuelle Programmierung ähnlicher Komponenten überflüssig macht. Modellierungssprachen, die auf eine bestimmte Problemdomäne zugeschnitten sind, nennt man domänenspezifische Sprachen (DSLs). Domänenspezifische Modellierung (DSM) vereint technische Lösungen mit intentionalen Problemen und ermöglicht die Entfaltung spezialisierter Expertise. Um der Funktionsvielfalt in Software Herr zu werden, bietet der Forschungszweig der Softwareproduktlinienentwicklung (SPLE) verschiedene Mittel zur Verwaltung von Variabilität in Software-Produkten an. Hierzu zählen Feature-Modelle sowie passende Werkzeuge, um Features auf Implementierungsbestandteile abzubilden. Modellgetriebene Entwicklung, domänenspezifische Modellierung und eine spezielle Handhabung von Variabilität in Softwareproduktlinien sind von entscheidender Bedeutung für den Erfolg von Softwarefirmen. Zur Zeit bestehen diese Paradigmen losgelöst voneinander und müssen integriert werden, damit die Vorteile jedes einzelnen für die Gesamtheit der Softwareentwicklung entfaltet werden können. In dieser Arbeit wird ein Ansatz vorgestellt, der dies ermöglicht. Es wird das Multi-Domain Engineering Paradigma (MDE) eingeführt, welches die modellgetriebene Softwareentwicklung mit mehreren domänenspezifischen Sprachen in variabilitätszentrierten Szenarien beschreibt. MDE stellt die Vorteile modellgetriebener Entwicklung mit mehreren DSLs als eine Notwendigkeit für Effizienz in der Entwicklung heraus und betrachtet das SPLE-Paradigma als unabdingbares Mittel um ein Maximum an Wiederverwendbarkeit und Flexibilität zu erzielen. In der Arbeit wird ein Ansatz zur Implementierung des MDE-Paradigmas, mit dem Namen HybridMDSD, vorgestellt
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Model Driven Development (MDD)"

1

B, Warmer Jos, and Bast Wim, eds. MDA explained: The model driven architecture : practice and promise. Addison-Wesley, 2003.

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

Beydeda, Sami, Matthias Book, and Volker Gruhn, eds. Model-Driven Software Development. Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/3-540-28554-7.

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

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

Find 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. 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. 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. 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. 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

Deved¿ic, Vladan, Dragan Djuric, and Dragan Ga¿evic. Model Driven Engineering and Ontology Development. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-00282-3.

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

Pires, Luís Ferreira, Slimane Hammoudi, and Bran Selic, eds. Model-Driven Engineering and Software Development. Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-94764-8.

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

Hammoudi, Slimane, Luís Ferreira Pires, Joaquim Filipe, and Rui César das Neves, eds. Model-Driven Engineering and Software Development. Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-25156-1.

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

Book chapters on the topic "Model Driven Development (MDD)"

1

Barbier, Franck, and Jean-Luc Recoussine. "Model-Driven Development (MDD)." In Cobol Software Modernization. John Wiley & Sons, Inc., 2015. http://dx.doi.org/10.1002/9781119073147.ch6.

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

Rios, Erkuden, Teodora Bozheva, Aitor Bediaga, and Nathalie Guilloreau. "MDD Maturity Model: A Roadmap for Introducing Model-Driven Development." In Model Driven Architecture – Foundations and Applications. Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11787044_7.

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

Aulagnier, Denis, Ali Koudri, Stéphane Lecomte, et al. "SoC/SoPC Development using MDD and MARTE Profile." In Model-Driven Engineering for Distributed Real-Time Systems. John Wiley & Sons, Inc., 2013. http://dx.doi.org/10.1002/9781118558096.ch8.

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

Brandon, Colm, Amandeep Singh, and Tiziana Margaria. "Model Driven Development for AI-Based Healthcare Systems: A Review." In Lecture Notes in Computer Science. Springer Nature Switzerland, 2024. http://dx.doi.org/10.1007/978-3-031-73741-1_15.

Full text
Abstract:
AbstractWe review our experience with integrating Artificial Intelligence (AI) into healthcare systems following the Model-Driven Development (MDD) approach. At a time when AI has the potential to instigate a paradigm shift in the health sector, better integrating healthcare experts in the development of these technologies is of paramount importance. We see MDD as a useful way to better embed non-technical stakeholders in the development process. The main goal of this review is to reflect on our experiences to date with MDD and AI in the context of developing healthcare systems. Four case studies that fall within that scope but have different profiles are introduced and summarised: the MyMM application for Multiple Myeloma diagnosis; CNN-HAR, that studies the ability to do AI on the edge for IoT-supported human activity recognition; the HIPPP web based portal for patient information in public health; and Cinco de Bio, a new model driven platform used for the first time to support a better cell-level understanding of diseases. Based on the aforementioned case studies we discuss the characteristics, the challenges faced and the postive outcomes achieved.
APA, Harvard, Vancouver, ISO, and other styles
5

Becker, Philipp, Dennis Christmann, and Reinhard Gotzhein. "Model-Driven Development of Time-Critical Protocols with SDL-MDD." In Lecture Notes in Computer Science. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-04554-7_3.

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

Greifenberg, Timo, Steffen Hillemacher, and Katrin Hölldobler. "Applied Artifact-Based Analysis for Architecture Consistency Checking." In Ernst Denert Award for Software Engineering 2019. Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58617-1_5.

Full text
Abstract:
AbstractThe usage of models within model-driven software development aims at facilitating complexity management of the system under development and closing the gap between the problem and the solution domain. Utilizing model-driven software development (MDD) tools for agile development can also increase the complexity within a project. The huge number of different artifacts and relations, their different kinds, and the high degree of automation hinder the understanding, maintenance, and evolution within MDD projects. A systematic approach to understand and manage MDD projects with a focus on its artifacts and corresponding relations is necessary to handle the complexity. The artifact-based analysis presented in this paper is such an approach. This paper gives an overview of different contributions of the artifact-based analysis but focuses on a specific kind of analysis: architecture consistency checking of model-driven development projects. By applying this kind of analyses, differences between the desired architecture and the actual architecture of the project at a specific point in time can be revealed.
APA, Harvard, Vancouver, ISO, and other styles
7

Böhme, Harald, Glenn Schütze, and Konrad Voigt. "Component Development: MDA Based Transformation from eODL to CIDL." In SDL 2005: Model Driven. Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11506843_5.

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

Gaševic, Dragan, Dragan Djuric, and Vladan Devedžic. "The MDA-Based Ontology Infrastructure." In Model Driven Engineering and Ontology Development. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-00282-3_7.

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

Gaševic, Dragan, Dragan Djuric, and Vladan Devedžic. "An MDA Based Ontology Platform: AIR." In Model Driven Engineering and Ontology Development. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-00282-3_12.

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

Gaševic, Dragan, Dragan Djuric, and Vladan Devedžic. "Mappings of MDA-Based Languages and Ontologies." In Model Driven Engineering and Ontology Development. Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-00282-3_10.

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

Conference papers on the topic "Model Driven Development (MDD)"

1

"A General Framework for the Development of MDD Projects." In International Conference on Model-Driven Engineering and Software Development. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004319402570260.

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

"Using MDD to Extend the IMS LD Standard with Adaptability." In International Workshop on Future Trends of Model-Driven Development. SciTePress - Science and and Technology Publications, 2010. http://dx.doi.org/10.5220/0003025600800086.

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

"REACT-MDD - Reactive Traceability in Model-driven Development." In 12th International Conference on Enterprise Information Systems. SciTePress - Science and and Technology Publications, 2010. http://dx.doi.org/10.5220/0002908304830488.

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

Jr., Ademir Carvalho, Thiago S. M. C. Farias, João Marcelo X. N. Teixeira, Veronica Teichrieb, and Judith Kelner. "Aplicando Model-Driven Development à Plataforma GPGPU." In Simpósio em Sistemas Computacionais de Alto Desempenho. Sociedade Brasileira de Computação, 2009. http://dx.doi.org/10.5753/wscad.2009.17402.

Full text
Abstract:
GPUs (Graphics Processing Units) são dispositivos gráficos que vêm ganhando destaque nos últimos anos pela sua eficiência em processamento paralelo. Neste contexto, o termo GPGPU (General-Purpose computation on GPU) é um novo conceito que visa explorar as vantagens das GPUs em áreas não necessariamente relacionadas a processamento gráfico. Este trabalho aplica princípios do MDD (Model-Driven Development) ao desenvolvimento de aplicações para GPU, visando produzir um ambiente mais adequado para a construção desse tipo de software. O resultado do trabalho foi o desenvolvimento de uma ferramenta que enxerga uma aplicação como um modelo e gera automaticamente parte significativa do código desta aplicação. O código gerado é expresso na linguagem definida por CUDA (Compute Unified Device Architecture), uma plataforma de programação para GPGPU.
APA, Harvard, Vancouver, ISO, and other styles
5

Zupeli, Breno Leite, and Vítor E. Silva Souza. "Integração de um Gerador de Código ao FrameWeb Editor." In XXIV Simpósio Brasileiro de Sistemas Multimídia e Web. Sociedade Brasileira de Computação - SBC, 2018. http://dx.doi.org/10.5753/webmedia.2018.4578.

Full text
Abstract:
FrameWeb (Framework-based Design Method for Web Engineering) incorporates concepts from categories of frameworks commonly used in the development of Web-based Information Systems into design models, defining the syntax of such models with meta-models. Based on Model-Driven Development (MDD) techniques, a CASE tool called FrameWeb Editor was built. In a separate eff ort, a code generation tool was proposed, but did not use the method’s MDD foundations. In this paper, we report on the integration of the code generator into the FrameWeb Editor and the FrameWeb meta-model.
APA, Harvard, Vancouver, ISO, and other styles
6

"An Outline of Conceptual Framework for Certification of MDA Tools." In International Workshop on Model-Driven Architecture and Modeling Theory-Driven Development. SciTePress - Science and and Technology Publications, 2010. http://dx.doi.org/10.5220/0003044400600069.

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

"MDE for Enterprise Application Systems." In International Conference on Model-Driven Engineering and Software Development. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004311502530256.

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

"Short Seminars on MDE Technologies - International Experiences." In International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and and Technology Publications, 2014. http://dx.doi.org/10.5220/0004876101320137.

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

Solomencevs, Arturs. "Topological Functioning Model for Software Development within MDA (Survey)." In Special Session on Model-Driven Innovations for Software Engineering. SCITEPRESS - Science and and Technology Publications, 2016. http://dx.doi.org/10.5220/0005922803150326.

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

Gamboa, Miguel Andrés, and Eugene Syriani. "Automating Activities in MDE Tools." In 4th International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and and Technology Publications, 2016. http://dx.doi.org/10.5220/0005760701230133.

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

Reports on the topic "Model Driven Development (MDD)"

1

Tse, Ronald, Carsten Roensdorf, Allan Jamieson, Nick Nicholas, and Jeffrey Lau, eds. OGC Guidance for the Development of Model-Driven Standards. Open Geospatial Consortium, Inc., 2024. http://dx.doi.org/10.62973/23-040.

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

DeLoach, Scott A., and Robby. Organization-based Model-driven Development of High-assurance Multiagent Systems. Defense Technical Information Center, 2009. http://dx.doi.org/10.21236/ada586694.

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

Cleaveland, Rance, Steve Sims, David Hansel, and Dan DuVarney. A Software Hub for High Assurance Model-Driven Development and Analysis. Defense Technical Information Center, 2007. http://dx.doi.org/10.21236/ada475038.

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

Peters, Hartmut. Development of a Two-Equation Turbulence Model for Mean Shear- and Internal Wave-Driven Mixing. Defense Technical Information Center, 2010. http://dx.doi.org/10.21236/ada542572.

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

Benkovitz, C. M. Development and testing of a high-resolution model for tropospheric sulfate driven by observation-derived meteorology. Office of Scientific and Technical Information (OSTI), 1994. http://dx.doi.org/10.2172/10165317.

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

Wu, S. T., and A. H. Wang. Development of a Data Driven Three-dimensional Magnetohydrodynamic Model With Radiation Effects to Study Photosphere-Coronal Coupling. Defense Technical Information Center, 2011. http://dx.doi.org/10.21236/ada563642.

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

Huerta, Gabriel. Collaborative Project: The problem of bias in defining uncertainty in computationally enabled strategies for data-driven climate model development. Office of Scientific and Technical Information (OSTI), 2014. http://dx.doi.org/10.2172/1149493.

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

Huerta, Gabriel. Collaborative Project: The problem of bias in defining uncertainty in computationally enabled strategies for data-driven climate model development. Final Technical Report. Office of Scientific and Technical Information (OSTI), 2016. http://dx.doi.org/10.2172/1252216.

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

White, Ed.D., Latia P., and Alexandra Merritt Johnson, Ph.D. Realizing District-Community Driven Outcomes Through Inclusive Innovation. Digital Promise, 2024. http://dx.doi.org/10.51388/20.500.12265/214.

Full text
Abstract:
This report examines the implementation of the Inclusive Innovation model across various pilot districts, spotlighting the collaborative processes of co-research and co-design involving students, educators, administrators, and community members. By centering the voices of students and communities who typically are furthest from opportunity, Inclusive Innovation fosters the development of solutions intended to mitigate education inequities. The report illustrates how Inclusive Innovation, through the co-creation of solutions by district-community teams focused on equity-centered outcomes, not only achieves perceived success in meeting those outcomes but also fosters a sense of empowerment and ownership among all participants.
APA, Harvard, Vancouver, ISO, and other styles
10

Baldos, Uris Lantz, and Thomas Hertel. Bursting the Bubble: A Long Run Perspective on Crop Commodity Prices. GTAP Working Paper, 2014. http://dx.doi.org/10.21642/gtap.wp80.

Full text
Abstract:
Contrary to the opinions expressed by many commentators, the recent price spike in agricultural commodities is a transitory phenomenon. Using projections from SIMPLE – a global model of the farm and food system – we argue that, in the long run, food prices will most likely resume their historical downward trend. We begin with an evaluation of the historical period 1961 to 2006 wherein the growth in agricultural productivity outpaced that of global crop demand, the latter being fueled by rising population and incomes. As a consequence, we observed a historical decline in global crop prices, which the SIMPLE model faithfully reproduces. Moving forward to 2051, we establish a set of projections in global crop prices given expected developments in population, incomes, agricultural productivity and biofuel use. We project that global crop prices will continue their long run decline in the coming decades, albeit at a slower pace. However, we recognize that, under some circumstances, global crop prices could still increase by mid-century. To formally assess the likelihood of future price changes, we conduct Monte Carlo simulations given distributions in the growth rates of both drivers and economic responses. Results show that 72% of the realizations produce price declines from 2006 to 2051. Keywords: crop commodity prices, long run projections, population growth, income growth, biofuels, crop productivity JEL: Q11, Q12, Q18
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Model Driven Development (MDD)' 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