Bibliografías temáticas / MDD (Model-Driven Development)

Índice

  1. Artículos de revistas
  2. Tesis
  3. Libros
  4. Capítulos de libros
  5. Actas de conferencias

Literatura académica sobre el tema "MDD (Model-Driven Development)"

Autor: Grafiati
Publicado: 4 de junio de 2021
Última modificación: 12 de febrero de 2022

Crea una cita precisa en los estilos APA, MLA, Chicago, Harvard y otros

Elija tipo de fuente:

Consulte las listas temáticas de artículos, libros, tesis, actas de conferencias y otras fuentes académicas sobre el tema "MDD (Model-Driven Development)".

Junto a cada fuente en la lista de referencias hay un botón "Agregar a la bibliografía". Pulsa este botón, y generaremos automáticamente la referencia bibliográfica para la obra elegida en el estilo de cita que necesites: APA, MLA, Harvard, Vancouver, Chicago, etc.

También puede descargar el texto completo de la publicación académica en formato pdf y leer en línea su resumen siempre que esté disponible en los metadatos.

Artículos de revistas sobre el tema "MDD (Model-Driven Development)"

1

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

WEISE, THOMAS, MICHAEL ZAPF, MOHAMMAD ULLAH KHAN y KURT GEIHS. "COMBINING GENETIC PROGRAMMING AND MODEL-DRIVEN DEVELOPMENT". International Journal of Computational Intelligence and Applications 08, n.º 01 (marzo de 2009): 37–52. http://dx.doi.org/10.1142/s1469026809002436.

Texto completo
Resumen
Genetic programming (GP) is known to provide good solutions for many problems like the evolution of network protocols and distributed algorithms. In most cases it is a hardwired module of a design framework assisting the engineer in optimizing specific aspects in system development. In this article, we show how the utility of GP can be increased remarkably by isolating it as a component and integrating it into the model-driven software development process. Our GP framework produces XMI-encoded UML models that can easily be loaded into widely available modeling tools, which in turn offer code generation as well as additional analysis and test capabilities. We use the evolution of a distributed election algorithm as an example to illustrate how GP can be combined with model-driven development (MDD).
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Romano, Breno Lisi y Adilson Marques da Cunha. "A Framework for Web Applications using an Agile and Collaborative Model Driven Development (AC-MDD)". Acta Scientiarum. Technology 41, n.º 1 (29 de mayo de 2019): 38349. http://dx.doi.org/10.4025/actascitechnol.v41i1.38349.

Texto completo
Resumen
This paper presents, as its main contribution, a Framework for Web Applications named Agile and Collaborative Model Driven Development (AC-MDD), seeking to reduce wastes on the modeling and documentation activities of web applications. The AC-MDD framework was elaborated based on related works that present Agile Model Driven Development processes (AMDD), but it deals with issues not yet considered by these researches. To adopt the AC-MDD framework, some visual elements from a novel Unified Modeling Language (UML) profile named Web-AML was designed, allowing to represent agile models of web applications. Besides that, in order to apply the proposed framework using these new models, a method was defined providing steps to transform agile models into web application source-codes. A case study was performed successfully in a real project that gives support to the population of a city located in the State of São Paulo (Brazil) to deal with the real flood problem they have been facing in recent years. This project was developed at the Federal Institute of Education, Science, and Technology of São Paulo to verify and validate the AC-MDD framework. Finally, a comparative analysis between the AC-MDD Framework and other AMDD processes was presented and highlighted the main aspects of the proposed framework.
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Kos, Tomaž, Marjan Mernik y Tomaž Kosar. "A Tool Support for Model-Driven Development: An Industrial Case Study from a Measurement Domain". Applied Sciences 9, n.º 21 (26 de octubre de 2019): 4553. http://dx.doi.org/10.3390/app9214553.

Texto completo
Resumen
End-user programming may utilize Domain-Specific Modeling Languages (DSMLs) to develop applications in the form of models, using only abstractions found in a specific problem domain. Indeed, the productivity benefits reported from Model-Driven Development (MDD) are hard to ignore, and a number of MDD solutions are flourishing. However, not all stories from industry on MDD are successful. End-users, without having software development skills, are more likely to introduce software errors than professional programmers. In this study, we propose and encourage other DSML developers to extend the development of DSML with tool support. We believe the programming tools (e.g., debugger, testing tool, refactoring tool) are also needed for end-users to ensure the proper functioning of the products they develop. It is imperative that domain experts are provided with tools that work on the abstraction level that is familiar to them. In this paper, an industrial experience is presented for building various tools for usage in MDD. Debugger, automated testing infrastructure, refactoring, and other tools were implemented for Sequencer, a DSML. Our experience with the implementation of tool support for MDD confirms that these tools are indispensable for end-user programming in practice, and that implementing those tools might not be as costly as expected.
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

KARDAS, GEYLANI, ARDA GOKNIL, OGUZ DIKENELLI y N. YASEMIN TOPALOGLU. "MODEL DRIVEN DEVELOPMENT OF SEMANTIC WEB ENABLED MULTI-AGENT SYSTEMS". International Journal of Cooperative Information Systems 18, n.º 02 (junio de 2009): 261–308. http://dx.doi.org/10.1142/s0218843009002014.

Texto completo
Resumen
Semantic Web evolution brought a new vision into agent research. The interpretation of this second generation web will be realized by autonomous computational entities, called agents, to handle the semantic content on behalf of their human users. Surely, Semantic Web environment has specific architectural entities and a different semantic which must be considered to model a Multi-agent System (MAS) within this environment. Hence, in this study, we introduce a MAS development process which supports the Semantic Web environment. Our approach is based on Model Driven Development (MDD) which aims to change the focus of software development from code to models. We first define an architecture for Semantic Web enabled MASs and then provide a MAS metamodel which consists of the first class meta-entities derived from this architecture. We also define a model transformation process for MDD of such MASs. We present a complete transformation process in which the source and the target metamodels, entity mappings between models and the implementation of the transformation for two different real MAS frameworks by using a well-known model transformation language are all included. In addition to the model-to-model transformation, the implementation of the model-to-code transformation is given as the last step of the system development process. The evaluation of the proposed development process by considering its use within the scope of a real commercial software project is also discussed.
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

SOLBERG, ARNOR, DEVON SIMMONDS, RAGHU REDDY, ROBERT FRANCE, SUDIPTO GHOSH y JAN ØYVIND AAGEDAL. "DEVELOPING DISTRIBUTED SERVICES USING AN ASPECT ORIENTED MODEL DRIVEN FRAMEWORK". International Journal of Cooperative Information Systems 15, n.º 04 (diciembre de 2006): 535–64. http://dx.doi.org/10.1142/s0218843006001487.

Texto completo
Resumen
To manage the development of cooperative information systems that support the dynamics and mobility of modern businesses, separation of concern mechanisms and abstractions are needed. Model driven development (MDD) approaches utilize abstraction and transformation to handle complexity. In MDD, specifying transformations between models at various levels of abstraction can be a complex task. Specifying transformations for pervasive system services that are tangled with other system services is particularly difficult because the elements to be transformed are distributed across a model. This paper presents an aspect oriented model driven framework (AOMDF) that facilitates separation of pervasive services and supports their transformation across different levels of abstraction. The framework facilitates composition of pervasive services with enterprise services at various levels of abstraction. The framework is illustrated using an example in which a platform independent model of a banking service is transformed to a platform specific model.
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Tesis sobre el tema "MDD (Model-Driven Development)"

1

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
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/.

Texto completo
Resumen
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.
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
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/.

Texto completo
Resumen
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.
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
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.

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

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.

Texto completo
Resumen
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)
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
Capes
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.
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

SOUZA, Ricardo André Cavalcante de. "WE4UIV Web engineering for user interaction view". Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/1489.

Texto completo
Resumen
Made available in DSpace on 2014-06-12T15:50:30Z (GMT). No. of bitstreams: 2 arquivo1972_1.pdf: 2696080 bytes, checksum: 69e35c3af53ec4eeb4876270ddb417ad (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
No mundo globalizado e competitivo, a sobrevivência de uma organização está relacionada a atrair e, principalmente, manter clientes (consumidores) através da prestação de serviços de qualidade. Atualmente, a forma mais usual de comunicação direta entre as organizações e seus (possíveis) clientes é através de aplicações baseadas na Web. Entre as vantagens deste tipo de aplicação estão a disponibilidade em tempo integral (24/7/365) e a facilidade de acesso, tendo em vista que o requisito inicial é apenas um computador com acesso à Internet. No contexto da disciplina de Engenharia de Software, as aplicações Web possuem características específicas que as diferem de aplicações tradicionais, especialmente no que se refere à interação com os usuários, e que devem ser consideradas adequadamente no processo de desenvolvimento. Entretanto, os processos de software tradicionais são dirigidos à funcionalidade e a parte do sistema responsável pela interação com os usuários é tratada com menor ênfase usualmente apenas na etapa de Implementação, ocasionando deficiências no produto e insatisfação dos usuários quanto ao uso do sistema. Neste cenário, este trabalho apresenta o método WE4UIV (Web Engineering User Interaction View), dirigido a modelos e baseado em componentes, cujo propósito é tratar os aspectos relacionados à visão de interação com os usuários de aplicações Web, nos níveis de análise e projeto, de modo a fornecer subsídios para orientar a etapa de Implementação. Além disso, visando acelerar e tornar menos manual a etapa de Implementação, este trabalho também apresenta uma ferramenta integrada a um ambiente de desenvolvimento para geração de código fonte a partir de artefatos de projeto descritos em UML. A abordagem apresentada neste trabalho pressupõe melhorias quantitativas no processo de desenvolvimento da visão de interação com os usuários, especificamente redução do tempo da etapa de Implementação e do índice de trabalho adicional causado por solicitações de mudança. A abordagem proposta é validada através de um processo de experimentação no contexto de um projeto real de desenvolvimento de software
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Arndt, Bruno Felipe. "MME-MDD : um método para manutenção e evolução de sistemas baseados no MDD". Universidade Federal de São Carlos, 2016. https://repositorio.ufscar.br/handle/ufscar/8503.

Texto completo
Resumen
Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2017-02-07T10:21:15Z No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Approved for entry into archive by Camila Passos (camilapassos@ufscar.br) on 2017-02-08T12:04:07Z (GMT) No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Approved for entry into archive by Camila Passos (camilapassos@ufscar.br) on 2017-02-08T12:08:22Z (GMT) No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Made available in DSpace on 2017-02-08T12:09:45Z (GMT). No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5) Previous issue date: 2016-03-08
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Model-Driven Development (MDD) is proposed to reduce the semantic gap between problem and solution/implementation domains. Some tools are used, and the code generator is commonly used in this context. These generators are often implemented using templates. A Reference Implementation (RI) favoring the development/ maintenance of software facilitates this implementation’s types. However, RI requires a code migration process which consists in artifacts’ synchronization, and it is responsible for 20% to 25% of the time spent on development. The literature has no describe automatic solutions, but the group that this reaserch was included has develop tools that automate this process and reduce the time spent on some tasks. But each task has a different performance in relation to time spent, so automation of some tasks can be disadvantageous. Few reports describe such tasks and which ones are capable of automatic code migration. The aim of this study is to investigate the maintain and evolution process to identify and describe the types of maintain and evolution tasks that are essentially. Based on this study, a method (MME-MDD) that drives the developer during that proccess to guide the developer during the realization of each task, with the aim to maximize the benefits of this approach. The MME-MDD was validated by a case study and a empirical study and the method showed effective in most of tasks. In addition, studies show that using the proposed method brought a gain in the quality of the source code.
O MDD (Model-Driven Development) tem como proposta a redução da distância semântica entre os domínios problema e solução/implementação. Para isso, são utilizadas algumas ferramentas, sendo o gerador de código comumente usado neste contexto. Os geradores de código são frequentemente implementados com a utilização de templates. Para facilitar este tipo de implementação, usualmente é empregado uma Implementação de Referência (IR), favorecendo a evolução/ manutenção do software. Contudo, a IR traz a necessidade do processo de migração de código, que consiste na sincronização entre o seu código-fonte e os templates, sendo que este é responsável por 20 a 25% do tempo gasto no desenvolvimento. Na literatura não há relatos de solução automatizada, mas o grupo no qual esta pesquisa se insere vem desenvolvendo ferramentas que automatizam este processo e reduzem o tempo aplicado em algumas tarefas testadas. Porém, cada tarefa tem um desempenho diferente em relação ao tempo gasto e, portanto, a automação de algumas tarefas pode ser desvantajosa. Existem poucos relatos na literatura descrevendo tais tarefas e quais são os passos necessários para realizá-las. O objetivo deste estudo foi a investigação do processo de manutenção e evolução de sistemas baseados em MDD com a finalidade de identificar e descrever os tipos de tarefas de manutenção e evolução. Com base nesse estudo, foi elaborado o método MMEMDD que conduz o desenvolvedor durante o processo de manutenção e evolução de sistemas, visando guiar o desenvolvedor durante a realização de cada um dos tipos de tarefas, com o intuito de maximizar os benefícios da utilização dessa abordagem. O método foi validado por meio de um estudo de caso e um estudo experimental, sendo que o método se mostrou efetivo em grande parte das tarefas testadas. Além disso, os estudos apontaram que a utilização do método proposto trouxe ganho na qualidade do código-fonte.
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

demirci, özlem. "Development of MBSE/UML Maturity Model". Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH, Data- och elektroteknik, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-13159.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Neto, David Fernandes. "CoMDD: uma abordagem colaborativa para auxiliar o desenvolvimento orientado a modelos". Universidade de São Paulo, 2012. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-04092012-155208/.

Texto completo
Resumen
O desenvolvimento orientado a modelos (Model Driven Development - MDD) é uma abordagem que tem ganhado cada vez mais espaço na indústria e na academia, trazendo grandes benefícios, como o aumento de produtividade. Uma forma de se trabalhar usando MDD em equipe é usando uma IDE (Integrated Development Environment) associada a um sistema de versionamento. Entretanto, trabalhar colaborativamente usando uma IDE associada a um sistema de versionamento pode trazer algumas complicações para o desenvolvimento como: conflitos de modelos, documentação descontinuada, dificuldades por parte dos interessados em usar sistemas de versionamento, etc. Nesse contexto, este trabalho propõe uma abordagem de uso de wiki para desenvolvimento de MDD, de modo que o desenvolvedor seja capaz de criar modelos, gerar código fonte, compartilhar e versionar os modelos e ainda documentar colaborativamente, de maneira mais simples e fácil do que abordagens tradicionais. Isso possibilita que mais usuários não desenvolvedores possam participar mais no processo de desenvolvimento e ainda permite o aumento de produtividade. Para tentar evidenciar de que é possível uma wiki ser usada para desenvolver software, foi criada uma Domain Specific Language - DSL em uma wiki e foram realizados três estudos de caso: um com estudantes do ensino médio e que representam os não desenvolvedores, um com quatro alunos de pós-graduação com experiência de desenvolvimento na indústria e o último estudo de caso foi realizado com 48 participantes entre desenvolvedores e alunos de pósgraduação em Ciências da Computação. Os estudos de caso mostraram que é viável usar uma wiki para desenvolvimento, que não desenvolvedores se adaptam bem à abordagem e que 86% dos desenvolvedores usariam a abordagem proposta se tivessem que trabalhar com MDD. Os estudos de caso também levantaram as principais barreiras para aumentar a aceitação da abordagem. Com isso, este trabalho apresenta além de uma abordagem relativamente inédita na literatura, resultados sobre uso de sistemas de versionamento, de IDEs e de desenvolvimento colaborativo
The Model Driven Development (MDD) is an approach that has gained more space in industry and academia, bringing great benefits such as increased productivity. One way of working in teams with MDD is using an IDE (Integrated Development Environment) with a versioning system. However, to collaboratively work with an IDE and a versioning system may have implications and problems for the development as: conflicts of models, documentation discontinued, difficulties for stakeholders to use versioning systems, etc. In this context, this work proposes an approach to use a wiki to develop MDD, so that the developer is able to create models, generate source code, sharing and versioning models and also to collaboratively document, in a more simple and easy way than the traditional approaches. This enables non developers can participate more in the development process and also allows increasing productivity. To try to show that a wiki can be used to develop software, we created a Domain Specific Language (DSL) in a wiki and were performed three case studies: one with high school students and represent the non developers, another one with four graduate students with experience in software development in the industry, and the last case study was conducted with 48 participants among developers and graduate students in Computer Science. The case studies showed the feasibility of using a wiki for development, that non developers adapted well to the approach and 86 % of the developers would use a wiki to develop MDD. The study also raised the main barriers to increase the acceptance of the approach. Therefore, this work presents also a relatively new approach in the literature and results on the use of versioning systems, IDEs and collaboratively development
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

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.

Texto completo
Resumen
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)
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
CNPq
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.
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Libros sobre el tema "MDD (Model-Driven Development)"

1

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

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

John, Parodi, ed. Real-life MDA: Solving business problems with model driven architecture. Amsterdam: Elsevier/Morgan Kaufmann Publishers, 2007.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

J, Mellor Stephen, ed. MDA distilled: Principles of model-driven architecture. Boston: Addison-Wesley, 2004.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Pons, Claudia, Roxana Silvia Giandini y Gabriela Pérez. Desarrollo de software dirigido por modelos. Editorial de la Universidad Nacional de La Plata (EDULP) / McGraw-Hill Educación, 2010. http://dx.doi.org/10.35537/10915/26667.

Texto completo
Resumen
El Desarrollo de Software Dirigido por Modelos (MDD en su acepción en inglés “Model-Driven Development”) es una disciplina que está generando muchas expectativas como alternativa sobresaliente a los métodos convencionales de producción de software, más orientado al Espacio de la Solución que al Espacio del Problema. Después de muchos años intentándolo, parece que por fin la comunidad de la Ingeniería del Software acepta que un proceso robusto de producción de software debe estar soportado por Modelos Conceptuales y dirigido por las Transformaciones correspondientes entre Modelos definidas de forma precisa. Una gran cantidad de trabajos teóricos y prácticos acompañan a este movimiento. Existen también herramientas que lo hacen ya realidad a nivel comercial. Pero a menudo se olvida un componente fundamental para que su éxito sea una realidad tangible: la necesidad de disponer de material didáctico ágil, actualizado, preciso y riguroso, que permita entender los fundamentos del MDD, las abstracciones en que se basa, los estándares que lo soportan, los problemas que hay que abordar para ponerlo en práctica exitosamente, y las ventajas concretas derivadas de su adopción. Ese es justamente el gran valor proporcionado por este libro. Sus autoras proyectan toda su amplia experiencia didáctica e investigadora en ambientes MDD sobre un documento que introduce al lector de una manera clara, sencilla, eficaz y eficiente en el mundo del MDD y de todo lo que representa. Sus contenidos están actualizados, e incluyen todos los temas que son hoy en día esenciales para entender las peculiaridades del Desarrollo Dirigido por Modelos.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Model Driven Architecture: Applying MDA to Enterprise Computing. Wiley, 2003.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Frankel, David S. Model Driven Architecture: Applying MDA to Enterprise Computing. Wiley & Sons, Incorporated, John, 2003.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Kleppe, Anneke, Jos Warmer y Wim Bast. MDA Explained: The Model Driven Architecture(TM): Practice and Promise (The Addison-Wesley Object Technology Series). Addison-Wesley Professional, 2003.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Parodi, John y Michael Guttman. Real-Life MDA: Solving Business Problems with Model Driven Architecture (The OMG Press). Morgan Kaufmann, 2006.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Uwe, Assmann, Akşit Mehmet, Rensink Arend, LINK (Online service), MDAFA 2003 (2003 : Twente, Netherlands) y MDAFA 2004 (2004 : Linköping, Sweden), eds. Model driven architecture: European MDA workshops: foundations and applications, MDAFA 2003 and MDAFA 2004, Twente, The Netherlands, June 26-27, 2003 and Linköping, Sweden, June 10-11, 2004 : revised selected papers. Berlin: Springer, 2005.

Buscar texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Straaijer, Robin. The usage guide. Oxford University Press, 2017. http://dx.doi.org/10.1093/oso/9780198808206.003.0002.

Texto completo
Resumen
Drawing on data from the Hyper Usage Guide of English (HUGE) database (Straaijer 2014), this chapter sets the context for the other chapters of the collection by exploring the usage guide as a genre since the earliest publication in 1770. While modern usage guides overlap in form and content with other genres of works about language, there are distinct characteristics that identify them as a separate genre. After this genre had slowly been evolving for 150 years, H. W. Fowler’s Dictionary of Modern English Usage (1926) became a model for future publications. However, the usage guide remains a strongly author-driven genre, resulting in much variation in form and content. After continued development and professionalization from the mid-twentieth century onwards, two subtypes within the genre seem to have emerged: one striving for comprehensiveness and the other offering entertaining narrative. This variety may account for the enduring popularity of the genre.
Los estilos APA, Harvard, Vancouver, ISO, etc.

Capítulos de libros sobre el tema "MDD (Model-Driven Development)"

1

Barbier, Franck y Jean-Luc Recoussine. "Model-Driven Development (MDD)". En Cobol Software Modernization, 109–33. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2015. http://dx.doi.org/10.1002/9781119073147.ch6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Aulagnier, Denis, Ali Koudri, Stéphane Lecomte, Philippe Soulard, Joël Champeau, Jorgiano Vidal, Gilles Perrouin y Pierre Leray. "SoC/SoPC Development using MDD and MARTE Profile". En Model-Driven Engineering for Distributed Real-Time Systems, 201–32. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2013. http://dx.doi.org/10.1002/9781118558096.ch8.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Butting, Arvid y Andreas Wortmann. "Language Engineering for Heterogeneous Collaborative Embedded Systems". En Model-Based Engineering of Collaborative Embedded Systems, 239–53. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-62136-0_11.

Texto completo
Resumen
AbstractAt the core of model-driven development (MDD) of collaborative embedded systems (CESs) are models that realize the different participating stakeholders’ views of the systems. For CESs, these views contain various models to represent requirements, logical functions, collaboration functions, and technical realizations. To enable automated processing, these models must conform to modeling languages. Domain-specific languages (DSLs) that leverage concepts and terminology established by the stakeholders are key to their success. The variety of domains in which CESs are applied has led to a magnitude of different DSLs. These are manually engineered, composed, and customized for different applications, a process which is costly and error-prone. We present an approach for engineering independent language components and composing these using systematic composition operators. To support structured reuse of language components, we further present a methodology for building up product lines of such language components. This fosters engineering of collaborative embedded systems with modeling techniques tailored to each application.
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.

Actas de conferencias sobre el tema "MDD (Model-Driven Development)"

1

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Zupeli, Breno Leite y Vítor E. Silva Souza. "Integração de um Gerador de Código ao FrameWeb Editor". En 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.

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

"An Outline of Conceptual Framework for Certification of MDA Tools". En 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.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

André, Pascal y Mohammed Tebib. "Refining Automation System Control with MDE". En 8th International Conference on Model-Driven Engineering and Software Development. SCITEPRESS - Science and Technology Publications, 2020. http://dx.doi.org/10.5220/0009147804250432.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

"A MDE Framework for Semi-automatic Development of Web Applications". En International Conference on Model-Driven Engineering and Software Development. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004321302410246.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
También puede estar interesado en las bibliografías ampliadas sobre el tema "MDD (Model-Driven Development)" para tipos de fuentes particulares:
Artículos de revistas Tesis
Ofrecemos descuentos en todos los planes premium para autores cuyas obras están incluidas en selecciones literarias temáticas. ¡Contáctenos para obtener un código promocional único!

Pasar a la bibliografía