Results 261 to 270 of about 1,764,289 (298)
Some of the next articles are maybe not open access.

Model-driven engineering practices in industry

Proceedings of the 33rd International Conference on Software Engineering, 2011
In this paper, we attempt to address the relative absence of empirical studies of model driven engineering through describing the practices of three commercial organizations as they adopted a model driven engineering approach to their software development.
Hutchinson, John   +2 more
openaire   +1 more source

Model Driven Engineering

2016
The objective of this chapter is to introduce the fundamental concepts, principles and processes of Model Driven Engineering (MDE). The role of MDE for code generation in simulation software engineering, interoperability, model replicability and computational reproducibility are discussed.
Okan Topçu   +3 more
openaire   +1 more source

Model-driven visual requirements engineering

13th IEEE International Conference on Requirements Engineering (RE'05), 2005
This paper describes the requirements handling process of a set of research projects, the ATHENA IP, and how this process is supported by modeling and visualizing requirement structures. First, users and external stakeholders register requirements through easy-to-use Web interfaces.
Helge Grenager Solheim   +4 more
openaire   +1 more source

Textual Views in Model Driven Engineering

2009 35th Euromicro Conference on Software Engineering and Advanced Applications, 2009
Building views on abstract models is one of the key concepts of model-driven engineering. Different views help to present concepts behind a model in a way that they can be understood and edited by different stakeholders or developers in different roles.
Thomas Goldschmidt   +2 more
openaire   +1 more source

Model Driven Engineering with Ontology Technologies

2010
Ontologies constitute formal models of some aspect of the world that may be used for drawing interesting logical conclusions even for large models. Software models capture relevant characteristics of a software artifact to be developed, yet, most often these software models have limited formal semantics, or the underlying (often graphical) software ...
Steffen Staab   +3 more
openaire   +1 more source

Model Patches in Model-Driven Engineering

2010
Increasingly, recording the various kinds of design-level structural evolution that a system undergoes throughout its entire life-cycle is gaining relevance in software modeling and development. In this respect, an interesting and useful operation between subsequent system versions is model difference consisting in calculation, representation, and ...
Antonio Cicchetti   +2 more
openaire   +2 more sources

Coupled Evolution in Model-Driven Engineering

IEEE Software, 2012
Model-driven engineering bases a wide range of artifacts on metamodels. When such metamodels evolve, such as a new version of Unified Modeling Language or Business Process Execution Notation or a company-specific metamodel, underlying artifacts often become invalid. In this article, the authors provide an overview of coupled evolution methods and tools
Davide Di Ruscio   +2 more
openaire   +2 more sources

Experiences with Model-Driven Engineering in Neurorobotics

2016
Model-driven engineering MDE has been successfully adopted in domains such as automation or embedded systems. However, in many other domains, MDE is rarely applied. In this paper, we describe our experiences of applying MDE techniques in the domain of neurorobotics --- a combination of neuroscience and robotics, studying the embodiment of autonomous ...
Georg Hinkel   +3 more
openaire   +1 more source

Model-Driven Prompt Engineering

2023 ACM/IEEE 26th International Conference on Model Driven Engineering Languages and Systems (MODELS), 2023
Robert Clarisó, Jordi Cabot
openaire   +1 more source

Cost Estimation for Model-Driven Engineering

2012
Cost estimation studies in model-driven engineering (MDE) are scarce; first, due to difficulty in quantifying qualitative characteristics of MDE that supposedly influence software development effort and second, due to the complexity of measuring varied artifacts that are generated and used in an end-to-end MDE toolset.
Sagar Sunkle, Vinay Kulkarni 0001
openaire   +1 more source

Home - About - Disclaimer - Privacy