Connecting research and practice: an experience report on research infusion with software architecture visualization and evaluation

Lindvall, Mikael; Stratton, William C.; Sibol, Deane E.; Ackermann, Christopher; Reid, W. Mark; Ganesan, Dharmalingam; McComas, David; Bartholomew, Maureen; Godfrey, Sally

doi:10.1007/s11334-010-0135-y

Cited by 6 publications

(4 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The IC1, IC2, EC4, EC5, and EC6 criteria were applied. Finally, after applying the three rounds and the IC and EC, 36 primary studies were obtained (see Table 3 ). The data extraction and synthesis processes for the 36 primary studies were conducted by using a form in which each study was identified with ID [13–15, 18, 22–53 ] and classified according to its context, validation, terminology, and usefulness in answering each research question.…”

Section: Methodsmentioning

confidence: 99%

“…The 41 papers obtained from conducting the review phase were coded as in [3, 11, 13–15, 18, 22–56 ]. They are the primary studies used to address the three research questions (see references and Complementary data (https://bit.ly/34rAYkm )).…”

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

“…Lindvall et al . [34 ] presented a process that analyses constraints violations and compares architectures in legacy systems written in C, C++, or Java. The process consists of five steps: (i) extraction: recover the software architecture from the source code (current architecture), (ii) visualisation: represent the extraction in a UML class diagram, (iii) graphical editing: construct a new architecture by manipulating and refactoring the current architecture, (iv) rules specification: define architecture rules that the new architecture should accomplish, and (v) mapping and evaluation of components: compare the current architecture and the newly designed architecture, then evaluate the designed rules to select a final decision.…”

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

See 2 more Smart Citations

Towards a reference process for software architecture reconstruction

et al. 2020

View full text Add to dashboard Cite

Nowadays, software systems remain useful and competitive; entail the inevitable need to change over time and to be adapted to new technologies, platforms, and architectures. These quick changes imply following systematic, automated, or standardised processes that provide recommendations and guidelines to architects during software architecture reconstruction. Considerable research work on architecture reconstruction has been conducted. However, it needs to be studied thoroughly to determine what are the common activities and elements to reconstruct software architectures, and to define a reference process for systematically guiding the evolution of software architectures. This work addresses the need for defining a process for software architecture reconstruction called software improvement in the reconstruction of architectures (SIRA). This process has been rigorously designed from the results of a systematic literature review and a small survey of related work. As a result, SIRA integrates and extends previous research and can be conceived as a reference process to reconstruct software architectures in a semi‐automated way. In addition, this work also determines the common elements of the architecture reconstruction process: (i) techniques and activities; (ii) architectural elements, patterns, and attributes; (iii) mechanisms and strategies; and (iv) the automation and recommendation tasks of the process.

show abstract

Section: Methodsmentioning

confidence: 99%

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

Section: Reconstruction and Reverse Engineering Of Software Architementioning

confidence: 99%

See 1 more Smart Citation

Towards a reference process for software architecture reconstruction

et al. 2020

View full text Add to dashboard Cite

show abstract

“…Fraser and Mancl report on their experiences in introducing new telecommunication systems. Hinchey et al report on the introduction of software assurance techniques, Zelkowitz on the introduction of formal inspections, and Lindvall et al on the introduction of tools in the space and aerospace domain.…”

Section: Background and Motivationmentioning

confidence: 99%

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