169 - Bridging the Gap: SE Technology Transfer into Practice - Study Design and Preliminary Results

Background: Particularly during and after research projects, technology transfer into practice plays an important role for academia to get technologies into use and for industry to improve their development. Objective: Our goal was to gain more and current knowledge about how technology transfer from software engineering (SE) research into industrial practice is accomplished best and how to measure the effectiveness of this transfer. Method: We conducted a study in the context of two German research projects, covering many different organizations from industry and academia. Results: This paper presents the design of the study and the survey performed. After introducing the concept of technology transfer we used and adapted, we present preliminary results. Conclusions: We observed that traditional means such as meetings or workshops are still the most widely used mediums for technology transfer in SE. We also discovered that, even though the duration of transfer depends on the object being transferred, the average duration is three years, which is far less than previously published (~18 years).

Software

© Fraunhofer IESE
BRIDIGING THE GAP: SE Technology Transfer into Practice Study Design and Preliminary Results
Philipp Diebold, Antonio Vetrò
8th International Symposium on Empirical Software Engineering and Measurement
19 September 2014 - Torino, Italy

© Fraunhofer IESE
2
Defintion Technology Transfer
Technology Transfer (TT) is defined as
“the process sharing knowledge, machines, equipment, methods, techniques, processes, […]
from transferors to transferees, who will exploit the technology into new products, processes, applications, and business models” [1]
[1] Teece, D.J. 1997. Technology transfer by multinational firms: The resource cost of transferring technological know-how. In Economics Journal, 242-261

© Fraunhofer IESE
4
Study Goal
Characterize the TT of SE objects with
respect to the current state of the practice
(SG1), the transfer mediums used (SG2), and
improvements or future transfer trends
(SG3) from the industry and researcher perspective within SE

© Fraunhofer IESE
5
Study Design Survey Structure
Start
Demographics
Current State
of Transfer
Medium Assessment
Transfer Improvement
End

© Fraunhofer IESE
6
Study Design Survey Structure – Motivation [9]
…

© Fraunhofer IESE
7
Study Design Survey Structure - Object
“[…] knowledge, machines, equipment, methods, techniques, processes, […]” [1]

© Fraunhofer IESE
8
Study Design Survey Structure - Process

© Fraunhofer IESE
9
Study Design Survey Structure – Time to transfer

© Fraunhofer IESE
10
Study Design Survey Structure - Trigger

© Fraunhofer IESE
11
Study Design Survey Structure – Mediums
64 different mediums
Models (1st layer)
2nd layer
3rd layer
People-mover model [2]
Personal exchange
…
Communication model [2]
Publications
Internet resources
Conferences, workshops, etc.
Guidelines
Vendor model [2]
Consultancy
On-the-shelf model [2]
Software, systems, and tool
Standards
Cooperative model
Co-working
Licensing
Research cooperation
Educational model
Educational programs

© Fraunhofer IESE
12
Study Design Survey Structure – Goals
…

© Fraunhofer IESE
14
Preliminary Results Time to Transfer
3
“[…] knowledge, machines, equipment, methods, techniques, processes, […]” [1]

© Fraunhofer IESE
15
Preliminary Results TT Mediums
22%
22%
16%
5%
5%
11%
5%
11%
61%
38%
38%
33%
33%
38%
33%
27%
33%
11%
5%
5%
16%
22%
44%
33%
50%
33%
33%
16%
16%
27%
38%
16%
11%
11%
11%
5%
16%
11%
27%
38%
22%
38.89%
27%
5%
5%
11%
5%
11%
5%
5%
11%
11%
38%
0%
50%
100%
Workshops
and meetings
Personnel
exchange
Co-working
Publications
Research
cooperation
Software,
systems, and…
Consultancy
Internet
resources
Conferences
Guidelines
Educational
programs
Licensing and
standards
Always
Often
Sometimes
Rarely
Never
human
intensive

© Fraunhofer IESE
16
Future Work Analyze Results

© Fraunhofer IESE
17
Future Work Extending / Spreading the survey
setechtransfer.wordpress.com

© Fraunhofer IESE
18
Questions?
Thank
you
“the process sharing knowledge, machines, equipment, methods, techniques, processes, from transferors to transferees” [1]
Transfer ObjectTransferorTransfereeTransactionTransfer Medium
+
Philipp Diebold
M. Sc.
@p_diebold
Process Management
Dep. MPE
Fraunhofer IESE Fraunhofer-Platz 1 | D-67663 Kaiserslautern
Phone: +49 (0) 631-6800-2183 Fax: +49 (0) 631-6800-9-2183 Email: philipp.diebold@iese.fraunhofer.de

This paper focuses on two case studies conducted in a Virtual Campus of Norwegian University of Science and Technology (NTNU). In these case studies the Virtual Campus acted as a venue for guest lectures and as a place for collaborative 3D educational visualizations and cross-cultural interaction. The data collected during the studies is analyzed to explore the technological, social and other issues using virtual worlds in educational settings, focusing on visualization of educational content. The paper concludes with some recommendations for future development of the Virtual Campus.

CASCON06.ppt

Ptidej Team

This document summarizes research on understanding how software engineers comprehend programs. Eye-tracking experiments were conducted to study engineers' eye movements when reviewing class diagrams. Preliminary findings showed their attention was focused locally around classes of interest and little attention was paid to binary relationships. More experiments were proposed to test hypotheses and improve understanding of the program comprehension process.

Short Stories

farida6

The document summarizes several short stories and poems that will be included in a readathon. It provides short summaries of the key events or themes in "Good-Hearted People" by T.S. Arthur, "The Lady or the Tiger?" by Frank Stockton, "The Star" by Esther Claes, and "The Bet" by Anton Chekhov. It also includes brief quotes from "The Bet" and a song, as well as a short saying. The summaries give a high-level overview of the essential information and main ideas from each of the works.

130 - Motivated software engineers are engaged and focused, while satisfied o...

Context – Motivation and job satisfaction are not the same thing, and although business organisation research recognised this a long time ago, in Software Engineering research, we have not. As a result, thirty years of research on motivation in software engineering has produced knowledge on what makes software engineers generally happier, but not about how to increase their motivation. Goal – In this article, we aim to identify visible signs of a software engineer who is motivated to work. Method – We describe a field study in which 62 practitioners in Brazil reported their view of "motivation" in the context of their practical work. Data was collected by means of audio-recorded semi-structured interviews, and a thematic analysis was applied to identify the most relevant descriptors of motivation. Results – Our data reveal that (1) motivated Software Engineers are engaged, focused, and collaborative; and (2) the term "motivation" is used as an umbrella term to cover several distinct organizational behaviours that are not necessarily related to the individual ́s desire to work. Conclusions – Without a clear picture of the difference between these two concepts, work-based motivation programs may not be designed effectively to address either turnover or performance issues. Overall, this work indicates the need for a more effective conceptual system to investigate and encourage both job satisfaction and work motivation in software engineering research and practice.

Cv jaspal singh

Jaspal Singh

Jaspal Singh is a textile technologist and garment professional with over 25 years of experience in merchandising, design, production planning, quality control, and sourcing roles. He holds qualifications in textile technology, fashion garment technology and management, and apparel export management. His career includes positions with various apparel export houses and textile manufacturers as a senior merchandiser, assistant marketing manager, and production coordinator. He is looking for a new opportunity to utilize his expertise in the apparel, home furnishings, or accessories industry.

Ricardo cortes ballerino -Evopoli

Ricardo Cortes Ballerino

222 - Design Pattern Decay: The Case for Class Grime

Context: We investigate class grime, a form of design pattern decay, wherein classes of the pattern realization have extraneous attributes or methods, which obfuscate the intended design of a pattern. Goal: To expand the taxonomy of class grime using properties of class cohesion. Using this expanded taxonomy we explore the effect that forms of class grime have on pattern realization understandability. Method: A pilot study utilizing a formal experiment to explore the effects of class grime on design pattern understandability. The experiments used simulated injection of 8 types of class grime into design pattern realizations randomly selected from 16 design pattern types from a set of 6541 realizations from 520 distinct software systems. Results: We found that for each of the 8 identified class grime forms, understandability was negatively affected. Conclusion: This work serves as early communication of research for the validation of the extended taxonomy as well as the method of grime injection used in the experiment.

Membuat Presentasi

Salsabila Rizky Fadhila

Technology transfer by Zade Manasi S. M pharm 1st yr, Bharati vidyapeeth College of pharmacy, Kolhapur . 1. Introduction :-Technology transfer is the practice of transferring scientific findings from one organization to another for further development. Which is mainly concerned with the transfer of technology from research areas to “Production and Quality Assurance” environment. The process by which existing knowledge, facilities or capabilities developed under R & D are utilized to fulfil public and private need. Technology transfer is the intersection between business, science, engineering, law and government. Definition :-Transfer of technology is defined as “a logical procedure that controls the transfer of any process together with its documentation and professional expertise between development and manufacture or between manufacture sites” . 3. Objective :-To offer guidance & assistance to inventors & corporation. -To provide a hands-on learning opportunity. -To increase the general awareness. -To accelerate scale-up and cost reduction. 4. Development of technology from Research & D to production :-R&D provides technology transfer dossier (TTD) document to product development laboratory, which contains all information of formulation and drug product as follows- Master Formula Card (MFC)– Includes product name along with its strength, generic name, MFC number, page number, effective date, shelf life and market. Master Packing Card– Gives information about packaging type, material used for packaging, stability profile and shelf life of packaging. Master Formula– 5. Success of technology transfer :-It depends on :- -Communication -Open communication between all team members -Direct communication between technical members -Effective and timely communication with regulators *Sending and Receiving Unit - Technology transfer is not a “one way street” The sending unit and receiving unit must be equally involved in the process to ensure success -Team work at all time 6. Checklist for technology transfer :-It consists of: Production master formula. Manufacturing and Dispensing instructions. Analytical methods. Cleaning instructions and previous cleaning validation. Active specifications and source. Primary packaging material specifications and source. Packaging instructions. Process deviations file, Analytical deviations file. Specimen manufacturing batch record. 7. Technology transfer team :- The technology transfer team consists of :  Process Technologist QA Representative Production Representative  Engineering representative  QC Representative 8. Steps in technology transfer process :-A] Development of technology by R&D( Reaserch Phase): (a) Design of procedure and selection of excipients by R&D (b) Identification of specifications and quality by R&D B] Technology transfer from R&D to production (Development Phase): (a)Master Formula Card (MFC) (b) Master Packing Card (c) Master Formula (d) Specifications

An Approach of Improve Efficiencies through DevOps Adoption

IRJET Journal

This document discusses adopting DevOps practices to improve organizational efficiencies. It begins with an abstract discussing how organizations waste resources and how DevOps aims to address this through lean principles and continuous feedback. It then discusses the history and concepts of DevOps, proposing a DevOps adoption model. It outlines factors that affect IT performance and cultural transformation. The document also describes the research design of a study conducted through interviews with DevOps professionals. It identifies four main challenges to DevOps adoption: lack of awareness, lack of support, implementing technologies, and adapting processes. The analysis focuses on the lack of awareness challenge, noting confusion around DevOps definitions and resistance to "buzzwords".

EADTU 2018 conference e-LIVES project

Manuel Castro

Business modelling in the fuzzy front end of innovation camera ready 29june11

Sander Limonard

8. Transfer of Technology to Market and Commercial Exploitation of Results - ...

RIILP

This document discusses technology transfer and commercialization. It defines technology transfer as bringing research results to public use through commercialization. The key stakeholders are identified as the general public, research community, and the market. The technology transfer process involves moving innovation from research labs to the market through licensing, spin-outs or start-ups. Licensing and spin-outs are described as the main commercialization strategies, along with their advantages and risks. A case study on the MateCat machine translation tool is provided to illustrate this process.

An Exploratory Study on Technology Transfer in Software Engineering

Daniel Mendez

[OOFHEC2018] Manuel Castro: Identifying the best practices in e-engineering t...

EADTU

Chapter 2 The Project Management and Information Technology Context.ppt

This document provides an overview of key topics from the textbook "Information Technology Project Management, Seventh Edition". It discusses the systems view of project management and how it applies to IT projects. It explains that stakeholder management and top management commitment are critical for project success. It also describes organizational structures, culture, and trends in IT project management such as agile project management and globalization.

Project Communications Management

Andersson Lujan Ojeda

This document discusses planning project communications. It provides details on analyzing stakeholder communication needs, choosing appropriate communication technologies and methods, and developing a Communications Management Plan. The plan identifies the communication requirements and an approach for effectively engaging stakeholders throughout the project. Meetings are an important interactive method that must be carefully planned, executed and followed up on. The overall goal is to establish a process for maintaining regular, clear communication with all parties involved in the project.

Technology Transfer: Plan for Success

Jennifer Flagg

Technology transfer models.pptx

sneha_pharmacist

1. The document discusses qualitative and quantitative models of technology transfer. Qualitative models delineate activities and factors that influence success, while quantitative models aim to quantify parameters and minimize incompatibility between transferors and transferees. 2. Several qualitative models are described, including the Bar-Zakay, Behrman and Wallender, Dahlman and Westphal, and Schlie, Radnor and Wad models. These models outline stages of the technology transfer process and factors that influence effectiveness. 3. Quantitative models discussed aim to measure parameters like potential technological distance between transferors and transferees, and examine the technological "catch-up" process when a leader assists a follower.

Chapter 1 Introduction to Project Management.ppt

This document provides an overview of the 7th edition of the textbook "Information Technology Project Management". It discusses key topics covered in the textbook such as the history and growth of project management as a profession, the role of the Project Management Institute in establishing standards, and factors that contribute to IT project success or failure. The document also previews several chapters that will cover frameworks for project management, the role of the project manager, and emerging trends in the field.

Information Technology Project Management - part 01

This document provides an overview of the 7th edition of the textbook "Information Technology Project Management". It discusses key topics covered in the textbook such as the history and growth of project management as a profession, the role of the project manager, challenges in IT project management, and best practices for project success. The textbook aims to explain fundamental concepts in project management and discuss their application to information technology projects.

Technology Tranfer models

Pritam Kolge

This document discusses technology transfer models in pharmaceuticals. It begins with an introduction that defines technology transfer as the movement of technology between different stakeholders. It then discusses four qualitative models of technology transfer: the Bar-Zakay model, the Behrman and Wallender model, the Dahlman and Westphal model, and the Chantramonklasri model. It also discusses three quantitative models proposed by Sharif and Haq, Raz et al., and Klein and Lim. The document concludes that technology transfer is a complex process that requires a holistic approach and dedicated organizations to facilitate the transfer of technology from development to commercialization.

Sibilla 2017 a meaningful mapping approach for the complex design

msibilla

Developing the ability to manage complexity has become an essential element for the training of designers. In such a context, complexity mainly arises from the need to integrate knowledge and expertise. The project is grounded in a hypothesis of systematizing Meaningful Learning Activities with computer applications dedicated to the elaboration of cognitive maps, in order to develop the ability to manage the complexity of high-interaction flows which can be found in the project of energy efficiency in historic buildings. This paper focuses on two experimental courses, with the aim to assess the formative approach adopted. The results highlight an innovative procedure and a tool helpful both to trainers and to learners to assess and direct the quality of the complex design process.

Information Technology Project Management - part 02

This document discusses key topics from the textbook "Information Technology Project Management, Seventh Edition" including: the systems view of project management and how it applies to IT projects; understanding organizations and their structures/cultures; the importance of stakeholder management and top management commitment; project phases and life cycles; attributes and diversity of IT projects; and recent trends like globalization, outsourcing, virtual teams, and agile project management.

2006-03-21 Work Group Meeting on IT Techniques, Tools and Philosophies for Mo...

Rudolf Husar

The document summarizes a work group meeting on techniques and tools for model intercomparison studies. It discusses several past and ongoing intercomparison projects, including City-Delta, AEROCOM, GEMS, and ENSEMBLE. It proposes the development of an "Atmospheric Tracer Model Intercomparison Tools Initiative" to facilitate data sharing and analysis across different intercomparison projects through the use of common standards, tools, and databases. The initiative would focus on model documentation, quality control, comparison, benchmarking, and improvement.

Seminar and Project Manager and Resourceful Trainer(SMART)

IOSR Journals

Abstract: This paper presents an approach to eradicate all of the confusion which surrounds anyone while preparing for the project and seminar. Also it aims in helping the institution to manage the previous batch’s seminars and project. Seminar and project activity mainly deals with effective data searching and keeping pace with emerging technologies. This paper focuses the concepts like keeping data at one place, providing guidance related to Projects and seminars. This paper can represent an application that can be used by anyone for solving queries related to project and seminar.

Digital Business Engineering: Findings from the Install4Schenker case

Sebastian Opriel

The development of digital business models is a key field of research in the age of digitization. As companies embark on the journey to develop digital business models, the need for a methodology which supports their journey is imminent. This paper contributes to sharpening the methodological foundation of Digital Business Engineering by conducting a single case study exemplified by Install4Schenker. Install4Schenker is a digital service coordinating, controlling and validating external craftsmen with the goal of avoiding two-men-handling while delivering products requiring installation such as heaters. Based on this case study, this paper aims to identify the potential for further research, optimizations, and clarifications for the Digital Business Engineering methodology.

MDE Program Presentation - EMNantes

Gisela BONNAUD

Keynote 2 - The 20% of software engineering practices that contribute to 80% ...

This presentation will challenge the application of metrics and other software engineering practices in commercial companies that do not have to comply with safety/ regulatory standards and thus can chose the SDLC approach that they feel more appropriate and cost effective for the intended purpose. Which are the practices that are really applied to make things happen under the tight constraints of time to market and profitability? A snapshot of the "hands-on" situation from the perspective of a large consulting company engaged with many customers in various markets and domains. Bio: Gualtiero Bazzana is Chairman of ITA-STQB, Head of Marketing WG for ISTQB and Managing Director of Alten Italia. He has been working in the IT domain since 20 years with a long lasting experience in the areas of testing, process improvement, quality. He has authored 50+ papers at international conferences on such subjects

Keynote 1 - Engineering Software Analytics Studies

Performing quantitative software analytics studies can be an immensely rewarding activity for scientists performing empirical research. However, such studies often pose numerous engineering challenges. The researcher must hunt down appropriate data sets, devise bespoke collection and processing tools, and optimise performance to match the size of the collected data. I will discuss principles and strategies that can be used to deal with these problems, and present examples of associated tools and techniques. Some particularly effective strategies associated with data set construction involve recursion, web searching, synthesis, probing, instrumentation, and the nurturing of alliances. On the processing front approaches include the opportunistic scavenging of tool front-ends, the exploratory development of pipelines, as well as the exploitation of tool interoperability, scripting languages, and their rich libraries. The required performance can be obtained through parallelism, stream processing, the judicious use of low-level facilities, and the choice of appropriate samples. I will finish the presentation with an overview of open problems and challenges in software analytics in vertical domains, data analysis, and under-represented stakeholders.

Similar to 169 - Bridging the Gap: SE Technology Transfer into Practice - Study Design and Preliminary Results

Technology transfer MANASI .pptx

ZadeMS

An Approach of Improve Efficiencies through DevOps Adoption

IRJET Journal

EADTU 2018 conference e-LIVES project

Manuel Castro

Business modelling in the fuzzy front end of innovation camera ready 29june11

Sander Limonard

8. Transfer of Technology to Market and Commercial Exploitation of Results - ...

RIILP

An Exploratory Study on Technology Transfer in Software Engineering

Daniel Mendez

[OOFHEC2018] Manuel Castro: Identifying the best practices in e-engineering t...

EADTU

Chapter 2 The Project Management and Information Technology Context.ppt

Project Communications Management

Andersson Lujan Ojeda

Technology Transfer: Plan for Success

Jennifer Flagg

Technology transfer models.pptx

sneha_pharmacist

Chapter 1 Introduction to Project Management.ppt

Information Technology Project Management - part 01

This document provides an overview of the 7th edition of the textbook "Information Technology Project Management". It discusses key topics covered in the textbook such as the history and growth of project management as a profession, the role of the project manager, challenges in IT project management, and best practices for project success. The textbook aims to explain fundamental concepts in project management and discuss their application to information technology projects.

Technology Tranfer models

Pritam Kolge

Sibilla 2017 a meaningful mapping approach for the complex design

msibilla

Information Technology Project Management - part 02

2006-03-21 Work Group Meeting on IT Techniques, Tools and Philosophies for Mo...

Rudolf Husar

Seminar and Project Manager and Resourceful Trainer(SMART)

IOSR Journals

Digital Business Engineering: Findings from the Install4Schenker case

Sebastian Opriel

MDE Program Presentation - EMNantes

Gisela BONNAUD

Similar to 169 - Bridging the Gap: SE Technology Transfer into Practice - Study Design and Preliminary Results (20)

Technology transfer MANASI .pptx

An Approach of Improve Efficiencies through DevOps Adoption

EADTU 2018 conference e-LIVES project

Business modelling in the fuzzy front end of innovation camera ready 29june11

8. Transfer of Technology to Market and Commercial Exploitation of Results - ...

An Exploratory Study on Technology Transfer in Software Engineering

[OOFHEC2018] Manuel Castro: Identifying the best practices in e-engineering t...

Chapter 2 The Project Management and Information Technology Context.ppt

Project Communications Management

Technology Transfer: Plan for Success

Technology transfer models.pptx

Chapter 1 Introduction to Project Management.ppt

Information Technology Project Management - part 01

Technology Tranfer models

Sibilla 2017 a meaningful mapping approach for the complex design

Information Technology Project Management - part 02

2006-03-21 Work Group Meeting on IT Techniques, Tools and Philosophies for Mo...

Seminar and Project Manager and Resourceful Trainer(SMART)

Digital Business Engineering: Findings from the Install4Schenker case

MDE Program Presentation - EMNantes

More from ESEM 2014

Keynote 2 - The 20% of software engineering practices that contribute to 80% ...

Keynote 1 - Engineering Software Analytics Studies

33 - On Knowledge Transfer Skill in Pair Programming

Context: General knowledge transfer is often considered a valuable effect or side-effect of pair programming, but even more important is its role for the success of the pair programming session itself: The partners often need to explain an idea to carry the process forward. Goal: Understand the mechanisms at work when knowledge is transferred during a pair programming session; provide practical advice for constructive behavior. Method: Qualitative data analysis of recordings of actual industrial pair programming sessions. Results: Some pairs are much more efficient in their knowledge transfer than others. These pairs manage to (1) not attempt to explain multiple things at once, (2) not lose sight of a topic, (3) clarify dicult points in stages. Conclusions: Pair programming requires skill beyond software development skill. To be able to identify knowledge needs and then push such knowledge to or pull it from the partner success- fully is one aspect of such skill. We characterize a number of its elements.

210 - Software Population Pyramids: The Current and the Future of OSS Develop...

This document presents a study on software population pyramids, which graphically represent the distribution of contributors to open source software projects over time. The study analyzed activity data from 90 open source projects on GitHub. It identified four common shapes of software population pyramids and showed how the pyramids for two projects, homebrew and blueprint-css, evolved over multiple time periods. The software pyramids provide insights into the current status and future sustainability of open source development communities.

196 - Evaluation in Practice: Artifact-based Requirements Engineering and Sc...

Context: In the context of the research and development project ARAMiS, multiple partners from research and industry are collaborating in the development of new methods and technologies in the field of multicore systems. Goal: We designed and executed studies for evaluating the results of the ARAMiS sub-project responsible for requirements engineering: an artifact-based requirements engineering approach, its tooling, and a cross-domain scenario. Method: This evaluation was performed along with the dissemination of the results in the project. The evaluation included two studies aimed at collecting the opinions of the project participants regarding the requirements engineering results from the viewpoints of industry and research. Results: The mainly positive results showed us that the different parts of the requirements engineering approach in this project are being accepted. Conclusions: Nonetheless, especially the results for the scenario revealed some weaknesses, such as the so-called “ARAMiS gap”, i.e., a gap between the high-level requirements engineering artifacts and the detailed engineering artifacts.

42- Using Templates to Elicit Implied Security Requirements from Functional R...

Context: Security requirements for software systems can be challenging to identify and are often overlooked during the requirements engineering process. Existing functional requirements of a system can imply the need for security requirements. Systems having similar security objectives (e.g., confidentiality) often also share security requirements that can be captured in the form of reusable templates and instantiated in the context of a system to specify security requirements. Goal: We seek to improve the security requirements elicitation process by automatically suggesting appropriate security requirement templates implied by existing functional requirements. Method: We conducted a controlled experiment involving 50 graduate students enrolled in a software security course to evaluate the use of automatically-suggested templates in eliciting implied security requirements. Participants were divided into treatment (automatically-suggested templates) and control groups (no templates provided). Results: Participants using our templates identified 42% of all the implied security requirements in the oracle as compared to the control group, which identified only 16% of the implied security requirements. Template usage increased the efficiency of security requirements identified per unit of time. Conclusion: Automatically-suggested templates helped participants (security non-experts) think about security implications for the software system and consider more security requirements than they would have otherwise. We found that participants need more incentive than just a participatory grade when completing the task. Further, we recommend to ensure task completeness, participants either need a step-driven (i.e., wizard) approach or progress indicators to identify remaining work.

166 - ISBSG variables most frequently used for software effort estimation: A ...

Background: The International Software Benchmarking Standards Group (ISBSG) dataset makes it possible to estimate a project’s size, effort, duration, and cost. Aim: The aim was to analyze the ISBSG variables that have been used by researchers for software effort estimation from 2000, when the first papers were published, until the end of 2013. Method: A systematic mapping review was applied to over 167 papers obtained after the filtering process. From these, it was found that 133 papers produce effort estimation and only 107 list the independent variables used in the effort estimation models. Results: Seventy-one out of 118 ISBSG variables have been used at least once. There is a group of 20 variables that appear in more than 50% of the papers and include Functional Size (62%), Development Type (58%), Language Type (53%), and Development Platform (52%) following ISBSG recommendations. Sizing and Size attributes altogether represent the most relevant group along with Project attributes that includes 24 technical features of the project and the development platform. All in all, variables that have more missing values are used less frequently. Conclusions: This work presents a snapshot of the existing usage of ISBSG variables in software development estimation. Moreover, some insights are provided to guide future studies.

112 - The Role of Mentoring and Project Characteristics for Onboarding in Ope...

Context: Onboarding is a process that helps newcomers become integrated members of their organisation. Successful onboarding programs can result in increased performance in conventional organisations, but there is little guidance on how to onboard new developers in Open Source Software (OSS) projects. Goal: In this study, we examine how mentoring and project characteristics influence the effectiveness and efficiency of the onboarding process. We study a collaboration program involving a total of nine Open Source Software projects and more than 120 students from dfferent universities around the world as part of Facebook’s Education Modernization Program. Method: We use quantitative measurements of source code repositories, issue tracking systems, and discussion fora to examine how newcomers become contributing members of their OSS projects. Results: We found that developers receiving deliberate onboarding support through mentoring were more active at an earlier stage than developers entering projects through conventional means. Also, we found that project size and lifetime influenced onboarding. Conclusion: Empirical decision support can contribute to a more effective onboarding process in OSS projects. Mentor support in critical stages can accelerate the process, but project maturity is also a significant factor that increases the effect of onboarding.

224 - Factors Impacting Rapid Releases: An Industrial Case Study

Context: Software release teams try to reduce the time needed for the transit of features or bug fixes from the development environment to the production, crossing all the quality gates. However, little is known about the factors that influence the time-to-production and how they might be controlled in order to speed up the release cycles. Goal:This paper examines step by step the release process of an industrial software organization aiming to identify factors that have a significant impact on the lead time and outcomes of the software releases. Method:Over 14 months of release data have been analyzed (246 releases from the isolated source code branches to the production environment). Results:We discuss three dimensions under which a series of factors could be addressed: technical, organizational, and interactional. We present our findings in terms of implications for release process improvements. Conclusions: Our analyzes reveal that testing is the most time consuming activities (86%) along with the need for more congruence among teams, especially in the context of parallel development.

215 Towards a Framework to Support Large Scale Sampling in Software Engineeri...

Context: The low quality and small size of samples in empirical studies in software engineering hamper the interpretation and generalization of their results. Therefore, enlarging sample sizes and improving their quality represent an important research challenge. Goal: We aim to define a conceptual framework, including requirements for establishing adequate sources for sampling subjects in software engineering surveys. Method: We use previous experience on applying systematic sampling strategies combined with contemporary web technologies in previously executed surveys, to organize the conceptual framework. We analyze its application to different sources of sampling. Results: The framework was observed to be feasible after its application to nine different large-scale sources of sampling. Conclusions: The analyzed crowdsourcing tools do not support essential requirements to be considered sources of sampling, while free- lancing tools and professional social networks do.

214 - Sampling Improvement in Software Engineering Surveys

Context: Small and non-probabilistic samples represent relevant issues when discussing the external validity of empirical studies in Software Engineering. Goal: To investigate alternatives to improve the quality of samples (size, heterogeneity and level of confidence). Method: To replicate a survey on characteristics of agility in software processes by applying a systematic recruitment strategy over a professional social network. Results: It resulted in a sampling frame composed by 19 groups stratified according two perspectives: sharing of groups' members and main software engineering skills reported by the subjects. In total, 7,745 subjects were randomly recruited, resulting in 291 contributions. Conclusions: This sample was significantly larger, more heterogeneous and presents some strata with higher confidence levels than previous trials samples.

201 - Using Qualitative Metasummary to Synthesize Empirical Findings in Liter...

This document describes a study that used qualitative metasummary to synthesize findings from multiple empirical studies on software engineering teams. It discusses the metasummary method, which involves extracting findings, grouping them, abstracting them, and calculating frequency and intensity effect sizes. The researchers applied this method to studies on software engineering team performance. They found it produced a synthesis highly connected to the original findings but had limitations in comparability and integrating mixed data. Overall, qualitative metasummary was found to be useful for literature reviews in software engineering but could be improved.

178 - A replicated study on duplicate detection: Using Apache Lucene to searc...

Context: Duplicate detection is a fundamental part of issue management. Systems able to predict whether a new defect report will be closed as a duplicate, may decrease costs by limiting rework and collecting related pieces of information. Goal: Our work explores using Apache Lucene for large- scale duplicate detection based on textual content. Also, we evaluate the previous claim that results are improved if the title is weighted as more important than the description. Method: We conduct a conceptual replication of a well-cited study conducted at Sony Ericsson, using Lucene for searching in the public Android defect repository. In line with the original study, we explore how varying the weight- ing of the title and the description affects the accuracy. Results: We show that Lucene obtains the best results when the defect report title is weighted three times higher than the description, a bigger difference than has been previously acknowledged. Conclusions: Our work shows the potential of using Lucene as a scalable solution for duplicate detection.

124 - Impact of Developer Reputation on Code Review Outcomes in OSS Projects:...

This document studies the impact of developer reputation on code review outcomes in open source software projects. It analyzes code review data from 8 open source projects to test hypotheses about whether core developers, who have higher reputation, have shorter feedback and review intervals, higher acceptance rates, and fewer required patchsets than peripheral developers. The results provide empirical evidence that core developers do receive preferential treatment in code reviews, supporting all the hypotheses. This suggests reputation influences code review behaviors and outcomes for developers in open source projects.

18 - Impact of Process Conformance on the Effects of Test-driven Development

Context: One limitation of the empirical studies about test- driven development (TDD) is knowing whether the developers followed the advocated test-code-refactor cycle. Re- search dealt with the issue of process conformance only in terms of internal validity, while investigating the role of other confounding variables that might explain the contro- versial e↵ects of TDD. None of the research included process conformance as a fundamental part of the analysis. Goal: We aim to examine the impact of process conformance on the claimed effects of TDD on external quality, developers’ productivity and test quality. Method: We used data collected during a previous study to create regression models in which the level of process conformance was used to predict external quality, productivity, and tests thoroughness. Result: Based on our analysis of the available data (n = 22), we observe that neither quality (p value = 0.21), productivity (p value = 0.80), number of tests (p value = 0.39) nor coverage (pvalue = 0.09) was correlated with the level of TDD process conformance. Conclusion: While based on a small sample, we raise concerns about how TDD is interpreted. We also question whether the cost of strictly following TDD will pay-o↵ in terms of external quality, productivity, and tests thoroughness.

65 - An Empirical Simulation-based Study of Real-Time Speech Translation for ...

Context: Real-time speech translation technology is today available but still lacks a complete understanding of how such technology may affect communication in global software projects. Goal: To investigate the adoption of combining speech recognition and machine translation in order to overcome language barriers among stakeholders who are remotely negotiating software requirements. Method: We performed an empirical simulation-based study including: Google Web Speech API and Google Translate service, two groups of four subjects, speaking Italian and Brazilian Portuguese, and a test set of 60 technical and non-technical utterances. Results: Our findings revealed that, overall: (i) a satisfactory accuracy in terms of speech recognition was achieved, although significantly affected by speaker and utterance differences; (ii) adequate translations tend to follow accurate transcripts, meaning that speech recognition is the most critical part for speech translation technology. Conclusions: Results provide a positive albeit initial evidence towards the possibility to use speech translation technologies to help globally distributed team members to communicate in their native languages.

52 - The Impact of Test Ownership and Team Structure on the Reliability and E...

Context: Software testing is a crucial step in most software development processes. Testing software is a key component to manage and assess the risk of shipping quality products to customers. But testing is also an expensive process and changes to the system need to be tested thoroughly which may take time. Thus, the quality of a software product depends on the quality of its underlying testing process and on the effectiveness and reliability of individual test cases. Goal: In this paper, we investigate the impact of the organizational structure of test owners on the reliability and effectiveness of the corresponding test cases. Prior empirical research on organizational structure has focused only on developer activity. We expand the scope of empirical knowledge by assessing the impact of organizational structure on testing activities. Method: We performed an empirical study on the Windows build verification test suites (BVT) and relate effectiveness and reliability measures of each test run to the complexity and size of the organizational sub-structure that enclose all owners of test cases executed. Results: Our results show, that organizational structure impacts both test effectiveness and test execution reliability. We are also able to predict effectiveness and reliability with fairly high precision and recall values. Conclusion: We suggest to review test suites with respect to their organizational composition. As indicated by the results of this study, this would increase the effectiveness and reliability, development speed and developer satisfaction.

167 - Productivity for proof engineering

This document summarizes a study on proof productivity in formal verification projects. It analyzes data from 9 proof projects involving the seL4 microkernel. The study found that total project effort is strongly correlated with final proof size. Additionally, individual contributors' effort is also strongly correlated with their proof output size. While schedule pressure and team size may impact effort, the sample size was too small to draw significant conclusions. The study aims to improve understanding of cost effectiveness in formal proof engineering.

181 - Evaluating strategies for study selection in systematic literature studies

Context: The study selection process is critical to improve the reliability of secondary studies. Goal: To evaluate the selection strategies commonly employed in secondary studies in software engineering. Method: Building on these strategies, a study selection process was formulated and evalu- ated in a systematic review. Results: The selection process used a more inclusive strategy than the one typically used in secondary studies, which led to additional relevant articles. Conclusions: The results indicates that a good-enough sample could be obtained by following a less inclusive but more efficient strategy, if the articles identified as relevant for the study are a representative sample of the population, and there is a homogeneity of results and quality of the articles.

What Do Game Developers Test in Their Products?