A Model for Technology Transfer in Practice

Gorschek, Tony; Wohlin, Claes; Carré, Patrick; Larsson, Stig

doi:10.1109/ms.2006.147

Cited by 272 publications

(218 citation statements)

References 7 publications

Supporting

Mentioning

205

Contrasting

Unclassified

Order By: Relevance

“…More strictly, a case study is purely observational while action research is focused on and involved in the change process. In software process improvement (Dittrich et al 2008;Iversen et al 2004) and technology transfer studies (Gorschek et al 2006), the research method should be characterized as action research. However, when studying the effects of a change, e.g.…”

Section: Methodsmentioning

confidence: 99%

Guidelines for conducting and reporting case study research in software engineering

2008

View full text Add to dashboard Cite

Case study is a suitable research methodology for software engineering research since it studies contemporary phenomena in its natural context. However, the understanding of what constitutes a case study varies, and hence the quality of the resulting studies. This paper aims at providing an introduction to case study methodology and guidelines for researchers conducting case studies and readers studying reports of such studies. The content is based on the authors' own experience from conducting and reading case studies. The terminology and guidelines are compiled from different methodology handbooks in other research domains, in particular social science and information systems, and adapted to the needs in software engineering. We present recommended practices for software engineering case studies as well as empirically derived and evaluated checklists for researchers and readers of case study research.

show abstract

Section: Methodsmentioning

confidence: 99%

Guidelines for conducting and reporting case study research in software engineering

2008

View full text Add to dashboard Cite

show abstract

“…We also present the design for evaluating this method and validating its results The SPI methodology used in this study is based on iFLAP [17] and its predecessor [12,13]. IFLAP was chosen mainly because of two factors: (1) iFLAP and its predecessors have been proven to be scalable and useful in industry, especially in the automotive domain [17,23], and (2) concerns the studied organizations' limitations in allocating the necessary resources for the SPI project. Commencing top-down SPI effort such as CMMI [24] or Automotive SPICE [25] would not have been possible due to the large amount of resources required [26].…”

Section: Methodsmentioning

confidence: 99%

“…Second, empirical research addressing the PD/Man interface in PD is limited [18] and SPI initiatives performed in the industrial setting studied here, has not been found. Even though above mentioned literature is relevant, it is important to understand and adopt specific organizational needs in the search for solutions to industrial problems that have been identified [23].…”

Section: Related Work and Motivationmentioning

confidence: 99%

Software Process Improvement in Inter-departmental Development of Software-Intensive Automotive Systems – A Case Study

Pernstål

Gorschek

Feldt

et al. 2013

Product-Focused Software Process Improvement

Self Cite

View full text Add to dashboard Cite

“…The model used in this review might need to be Fig. 5 Step-wise evaluation of technologies (adapted from (Gorschek et al 2006)) changed to reflect research in specific areas, i.e., different research areas might have different levels of validation and the model should be changed to reflect state-of-research in the area. While the model can and should be adapted to fit specific subject areas, it should also evolve towards a more precise and demanding model as research design, execution and reporting improve.…”

Section: Future Workmentioning

confidence: 99%

“…This may hamper progress in the field, as practitioners looking to adopt new technologies developed in academia are offered scarce decision support (Ivarsson and Gorschek 2009). In an applied research field such as software engineering, the transfer and widespread use of research results in industry ultimately determine the relevance and success (Sjøberg et al 2002;Gorschek et al 2006). Researchers should thus not only develop new technologies and advocate potential benefits but also base the information on the extent to which the technology has been validated (tested).…”

Section: Introductionmentioning

confidence: 99%

A method for evaluating rigor and industrial relevance of technology evaluations

2010

Self Cite

View full text Add to dashboard Cite

One of the main goals of an applied research field such as software engineering is the transfer and widespread use of research results in industry. To impact industry, researchers developing technologies in academia need to provide tangible evidence of the advantages of using them. This can be done trough step-wise validation, enabling researchers to gradually test and evaluate technologies to finally try them in real settings with real users and applications. The evidence obtained, together with detailed information on how the validation was conducted, offers rich decision support material for industry practitioners seeking to adopt new technologies and researchers looking for an empirical basis on which to build new or refined technologies. This paper presents model for evaluating the rigor and industrial relevance of technology evaluations in software engineering. The model is applied and validated in a comprehensive systematic literature review of evaluations of requirements engineering technologies published in software engineering journals. The aim is to show the applicability of the model and to characterize how evaluations are carried out and reported to evaluate the state-of-research. The review shows that the model can be applied to characterize evaluations in requirements engineering. The findings from applying the model also show that the majority of technology evaluations in requirements engineering lack both industrial relevance and rigor. In addition, the research field does not show any improvements in terms of industrial relevance over time.

show abstract

A Model for Technology Transfer in Practice

Cited by 272 publications

References 7 publications

Guidelines for conducting and reporting case study research in software engineering

Guidelines for conducting and reporting case study research in software engineering

Software Process Improvement in Inter-departmental Development of Software-Intensive Automotive Systems – A Case Study

A method for evaluating rigor and industrial relevance of technology evaluations

Contact Info

Product

Resources

About