A modeling language's evolution driven by tight interaction between academia and industry

Aschauer, Thomas; Dauenhauer, Gerd; Pree, Wolfgang

doi:10.1145/1810295.1810304

Cited by 11 publications

(15 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There the risks and potentials of different structural evolution steps were theoretically discussed, and the existence and commonness of such evolution steps, which affect the composition/structure of an MDE setting, have been studied [covering steps (1) and (2)]. In this paper, we extend this research in several directions.…”

Section: Introductionmentioning

confidence: 87%

“…Note that we focused on non-purchase tool chains. We identified thirteen reports that describe MDE introduction or usage ( [2,3,7,10,20,24,29,33,36,38] and three case studies in [17]). We filtered the reports to ensure that the captured period of time is long enough to be able to observe evolution.…”

Section: Literature Reportsmentioning

confidence: 99%

“…Thus, reports that focus only on the initial introduction of MDE or on settings that were used for a single project only, were not suitable. Therefore, we excluded five reports ( [2,7,24,33,38] as well as the telecom case study in [17], where the described example was only used during one project). Finally, we chose seven reports ( [29] (CsTe), [10] (CsBA), [36] (CsFO), [20] (CsFBL), [3] (CsMo), as well as the case studies of the printer company (CsPC) and the car company (CsCC) [17]), which stem from different domains, such as the telecommunication industry, financial organizations, and development of control systems.…”

Section: Literature Reportsmentioning

confidence: 99%

“…1. 2 Manual activities, e.g., "Manipulate Implementation," and automated activities, e.g., "Generate Java Code," consume, manipulate, or create the different model and code artifacts, e.g., "Interface Implementation." These artifacts can be specified using different (modeling) languages, e.g., Ecore or Java.…”

Section: Introductionmentioning

confidence: 99%

“…In context of Software Configuration Management, an MDE settings might be considered as model-based configuration 2. The EMF generation is described in detail in http://www.vogella.de/ articles/EclipseEMF/article.html.…”

mentioning

confidence: 99%

See 4 more Smart Citations

On the complex nature of MDE evolution and its impact on changeability

Hebig

Giese

2015

Softw Syst Model

View full text Add to dashboard Cite

In model-driven engineering (MDE), a particular MDE setting of employed languages and automated and manual activities has major impact on productivity. Furthermore, it has been observed that such MDE settings evolve over time. However, currently not much is known about this evolution and its impact on the MDE setting's maturity, i.e., on changeability and other productivity dimensions. Research so far focuses on evolution of separate building blocks, such as (modeling-) languages, tools, or transformation, only. In this article, we address the lack of knowledge about evolution of MDE settings by investigating case studies from different companies. The first results reveal (1) that there is evolution that affects the composition of an MDE setting (structural evolution) and has the potential to strongly impact aspects, such as changeability and (2) that this structural evolution actually occurs in practice. Based on these first results, we investigated (3) whether there are cases in practice, where structural evolution already altered the risks of changeability given by the respective MDE setting. Therefore, we search and identify examples for such evolution steps on MDE settings from practice and collected six case studies on evolution histories in detail. As a result, we show in this paper that structural evolution (a) is not seldom in practice and (b) sometimes leads to the introduction of changeability risks.

show abstract

Section: Introductionmentioning

confidence: 87%

Section: Literature Reportsmentioning

confidence: 99%

Section: Literature Reportsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

mentioning

confidence: 99%

See 3 more Smart Citations

On the complex nature of MDE evolution and its impact on changeability

Hebig

Giese

2015

Softw Syst Model

View full text Add to dashboard Cite

show abstract

Approaches, success factors, and barriers for technology transfer in software engineering—Results of a systematic literature review

Brings

Daun

Brinckmann

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

Introduction: Technology transfer aims at supporting the transfer of results from software engineering research from academia to industrial application.Objective: This paper reports on the current state of technology transfer in software engineering.Method: We conducted a systematic literature review, in which we investigated 3070 papers. We identified in total 70 relevant papers, which were subject of a detailed analysis.Results: Many different approaches are proposed to foster technology transfer in software engineering. The majority of these approaches suggest direct collaboration between industry and academia or teaching new technologies in industrial training or university education. In addition, a considerable number of experience reports on technology transfer exist. Hence, a multitude of best practices, success stories, and lessons learned is reported. Among others, empirical evidence, maturity, and adaptability of the technology seem important preconditions for successful transfer, while social and organizational factors seem important barriers to successful technology transfer.Conclusion: Our findings can aid software engineering researchers in determining how best to support the transfer of their research results into practice. Furthermore, analysis of the literature also revealed that no reports exist on the combination of various technology transfer approaches, which could increase advantages of existing approaches while reducing their disadvantages. KEYWORDS software engineering, systematic literature review, technology transfer 1 | BACKGROUND AND MOTIVATION Software engineering research aims at solving real-world problems (cf Wieringa 1 ) and demands the evaluation of a proposed solution in an industrial setting (cf Basili 2 and Salman et al 3 ). However, there is often still a gap between academic solution proposals and industrial needs, and for many results from software engineering research, it takes a long time to have an impact on software engineering practices. 4 This is not only due to the fact that novel results from academic research are often unknown to practitioners but also that those research results are often not directly applicable to industry. 5To close this gap, software engineering research also deals with technology transfer itself (cf Pfleeger 6 ). Technology transfer aims at supporting the transfer of research results from academia to practice and is thus of interest to many scientific disciplines (cf, eg, Teece 7 ). While some challenges remain the same regardless of the technology to be transferred, others are particular to the software engineering field, as software engineering technologies typically evolve in a short time and thus the state of the art constantly changes (cf Boehm 8 and Finkelstein and Kramer 9 ).There exists a plethora of proposed solution approaches to foster technology transfer in software engineering as well as experience reports on successful technology transfer projects. Nevertheless, there is a need to support researchers in identifying proper technol...

show abstract

An industry survey on approaches, success factors, and barriers for technology transfer in software engineering

et al. 2023

View full text Add to dashboard Cite

One central aspect of software engineering research is the transfer of the proposed approaches into industrial practice. In the past, a number of technology transfer approaches and experiences from technology transfer projects in software engineering have already been reported. However, many researchers still struggle to get their research results noticed by practitioners. To investigate what is important to practitioners, we conducted a mixed‐methods study that provides us with reliable quantitative data as well as deeper insights from qualitative data. Our results show that there is a mismatch between industry professionals' needs and commonly proposed technology transfer approaches in the software engineering field. For instance, collaboration between industry and academia as well as participation in empirical evaluations is not deemed important from an industry point of view. In contrast, industry professionals emphasize the use of company‐specific pilot projects conducted by industry and the need for experts to be available in every phase of technology transfer.

show abstract

A modeling language's evolution driven by tight interaction between academia and industry

Cited by 11 publications

References 26 publications

On the complex nature of MDE evolution and its impact on changeability

On the complex nature of MDE evolution and its impact on changeability

Approaches, success factors, and barriers for technology transfer in software engineering—Results of a systematic literature review

An industry survey on approaches, success factors, and barriers for technology transfer in software engineering

Contact Info

Product

Resources

About