2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)最新文献_第3页

Noises in Interaction Traces Data and Their Impact on Previous Research Studies 相互作用中的噪声跟踪数据及其对先前研究的影响

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321209

Z. Soh, Thomas Drioul, Pierre-Antoine Rappe, Foutse Khomh, Yann-Gaël Guéhéneuc, N. Habra

{"title":"Noises in Interaction Traces Data and Their Impact on Previous Research Studies","authors":"Z. Soh, Thomas Drioul, Pierre-Antoine Rappe, Foutse Khomh, Yann-Gaël Guéhéneuc, N. Habra","doi":"10.1109/ESEM.2015.7321209","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321209","url":null,"abstract":"Context: Developers' interaction traces (ITs) are commonly used in software engineering to understand how developers maintain and evolve software systems. Researchers make several assumptions when mining ITs, e.g., edit events are considered to be change activities and the time mined from ITs is considered to be the time spent by the developers performing the maintenance task. Goal: We investigate the extent to which these assumptions are correct. We examine noises in developers'''' ITs data and the impact of these noises on previous results derived from these traces. Approach: We perform an experiment with 15 participants, whom we asked to perform bug-fixing activities and collect Mylyn ITs and VLC video captures. We then investigate noises between the two data sets and propose an approach to correct noises in ITs. Results: We find that Mylyn ITs can miss on average about 6% of the time spent performing a task and contain on average about 28% of false edit-events. We report that these noises may have led researchers to mislabel some participants'''' editing styles in about 34% of the cases and that the numbers of edit-events performed by developers and the times that they spent on tasks are correlated, when they were considered not to be. Conclusion: We show that ITs must be carefully cleaned before being used in research studies.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133656644","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 9

Will This Bug-Fixing Change Break Regression Testing? 这个bug修复变更会破坏回归测试吗?

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321218

Xinye Tang, Song Wang, Ke Mao

{"title":"Will This Bug-Fixing Change Break Regression Testing?","authors":"Xinye Tang, Song Wang, Ke Mao","doi":"10.1109/ESEM.2015.7321218","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321218","url":null,"abstract":"Context: Software source code is frequently changed for fixing revealed bugs. These bug-fixing changes might introduce unintended system behaviors, which are inconsistent with scenarios of existing regression test cases, and consequently break regression testing. For validating the quality of changes, regression testing is a required process before submitting changes during the development of software projects. Our pilot study shows that 48.7% bug-fixing changes might break regression testing at first run, which means developers have to run regression testing at least a couple of times for 48.7% changes. Such process can be tedious and time consuming. Thus, before running regression test suite, finding these changes and corresponding regression test cases could be helpful for developers to quickly fix these changes and improve the efficiency of regression testing. Goal: This paper proposes bug- fixing change impact prediction (BFCP), for predicting whether a bug-fixing change will break regression testing or not before running regression test cases, by mining software change histories. Method: Our approach employs the machine learning algorithms and static call graph analysis technique. Given a bug-fixing change, BFCP first predicts whether it will break existing regression test cases; second, if the change is predicted to break regression test cases, BFCP can further identify the might-be-broken test cases. Results: Results of experiments on 552 real bug-fixing changes from four large open source projects show that BFCP could achieve prediction precision up to 83.3%, recall up to 92.3%, and F-score up to 81.4%. For identifying the might-be-broken test cases, BFCP could achieve 100% recall.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"49 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124334762","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 15

Navigate, Understand, Communicate: How Developers Locate Performance Bugs 导航，理解，沟通:开发者如何定位性能漏洞

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321208

Sebastian Baltes, Oliver Moseler, Fabian Beck, S. Diehl

{"title":"Navigate, Understand, Communicate: How Developers Locate Performance Bugs","authors":"Sebastian Baltes, Oliver Moseler, Fabian Beck, S. Diehl","doi":"10.1109/ESEM.2015.7321208","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321208","url":null,"abstract":"Background: Performance bugs can lead to severe issues regarding computation efficiency, power consumption, and user experience. Locating these bugs is a difficult task because developers have to judge for every costly operation whether runtime is consumed necessarily or unnecessarily. Objective: We wanted to investigate how developers, when locating performance bugs, navigate through the code, understand the program, and communicate the detected issues. Method: We performed a qualitative user study observing twelve developers trying to fix documented performance bugs in two open source projects. The developers worked with a profiling and analysis tool that visually depicts runtime information in a list representation and embedded into the source code view. Results: We identified typical navigation strategies developers used for pinpointing the bug, for instance, following method calls based on runtime consumption. The integration of visualization and code helped developers to understand the bug. Sketches visualizing data structures and algorithms turned out to be valuable for externalizing and communicating the comprehension process for complex bugs. Conclusion: Fixing a performance bug is a code comprehension and navigation problem. Flexible navigation features based on executed methods and a close integration of source code and performance information support the process.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122819636","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 22

Improving Performance and Maintainability of Object Cloning with Lazy Clones: An Empirical Evaluation 用惰性克隆提高对象克隆的性能和可维护性:一个经验评价

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321202

Bruno Cartaxo, Paulo Borba, S. Soares, Helio Fugimoto

{"title":"Improving Performance and Maintainability of Object Cloning with Lazy Clones: An Empirical Evaluation","authors":"Bruno Cartaxo, Paulo Borba, S. Soares, Helio Fugimoto","doi":"10.1109/ESEM.2015.7321202","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321202","url":null,"abstract":"Object cloning is demanded by the prototype design pattern, copy-on-write strategy, some graph transformations, and many other scenarios. We have been developing a static analysis tool that clones objects frequently. In that context, issues related to performance, memory usage, and code maintainability might arise. Traditional deep cloning with dynamic allocation, reflection, and serialization, have not fulfilled those requirements. Thus, we developed novel implementations of lazy cloning with dynamic proxies and aspect-oriented programming (AOP). We defined benchmarks based on real workload to quantitatively assess the benefits of each implementation. AOP was chosen since it better harmonizes performance, memory usage and code maintainability. It was 88% faster than serialization, consumed 9 times less memory than reflection, and required 25 times less modifications on source code than dynamic allocation. In summary, we believe that the results can be extrapolated to broader contexts helping developers to make evidence-based decisions when object cloning is needed.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"51 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125700142","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 3

Award vs. Worker Behaviors in Competitive Crowdsourcing Tasks 奖励与竞争性众包任务中的员工行为

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321192

Ye Yang, R. Saremi

{"title":"Award vs. Worker Behaviors in Competitive Crowdsourcing Tasks","authors":"Ye Yang, R. Saremi","doi":"10.1109/ESEM.2015.7321192","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321192","url":null,"abstract":"Context: Existing studies have shown that award settings for software crowdsourcing tasks can be accurately predictable to reflect the size and complexity of the tasks. However, as one of the most important motivating factors for on line crowdsourcing workers, it is more important for the task requesters to not only be able to estimate \"what the nominal price should be?\" for their tasks, but also to justify \"what the strategic price should be?\" in order to incentivize broader worker participation as well as higher quality of final submissions. Goal: To address the above questions, this paper reports an empirical study to develop further understanding about the relationship between tasks award and associated worker behaviors. Method: We develop a conceptual award-behavior model, formulate a set of research questions about the relationships of award and worker's behavior and performance, and conduct 4 empirical studies on 514 crowdsourcing tasks extracted from TopCoder platform. Results: Major results include: (1) in general, negative correlations between award and worker behavior metrics; (2) a decreasing tendency in making submission as the number of registrants increases; (3) a weak positive correlation of 0.19 between number of registrants and score of the winning submission; and (4) for similar tasks, the relationship of award on worker behavior follows a variety of inverted U-shape curves. Conclusions: We believe the preliminary findings are helpful for task requesters in better task planning, and hope to stimulate further discussions and research in strategic crowd coordination.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115374850","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 33

How to Make Best Use of Cross-Company Data for Web Effort Estimation? 如何充分利用跨公司数据进行网络工作量估算?

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321199

Leandro L. Minku, Federica Sarro, E. Mendes, F. Ferrucci

{"title":"How to Make Best Use of Cross-Company Data for Web Effort Estimation?","authors":"Leandro L. Minku, Federica Sarro, E. Mendes, F. Ferrucci","doi":"10.1109/ESEM.2015.7321199","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321199","url":null,"abstract":"[Context]: The numerous challenges that can hinder software companies from gathering their own data have motivated over the past 15 years research on the use of cross-company (CC) datasets for software effort prediction. Part of this research focused on Web effort prediction, given the large increase worldwide in the development of Web applications. Some of these studies indicate that it may be possible to achieve better performance using CC models if some strategy to make the CC data more similar to the within-company (WC) data is adopted. [Goal]: This study investigates the use of a recently proposed approach called Dycom to assess to what extent Web effort predictions obtained using CC datasets are effective in relation to the predictions obtained using WC data when explicitly mapping the CC models to the WC context. [Method]: Data on 125 Web projects from eight different companies part of the Tukutuku database were used to build prediction models. We benchmarked these models against baseline models (mean and median effort) and a WC base learner that does not benefit of the mapping. We also compared Dycom against a competitive CC approach from the literature (NN-filtering). We report a company-by- company analysis. [Results]: Dycom usually managed to achieve similar or better performance than a WC model while using only half of the WC training data. These results are also an improvement over previous studies that investigated the use of different strategies to adapt CC models to the WC data for Web effort estimation. [Conclusions]: We conclude that the use of Dycom for Web effort prediction is quite promising and in general supports previous results when applying Dycom to conventional software datasets.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"139 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131598866","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 34

Ramp-Up Journey of New Hires: Tug of War of Aids and Impediments 新员工的提升之旅:艾滋病和障碍的拉锯战

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321212

Ayushi Rastogi, Suresh Thummalapenta, Thomas Zimmermann, Nachiappan Nagappan, J. Czerwonka

{"title":"Ramp-Up Journey of New Hires: Tug of War of Aids and Impediments","authors":"Ayushi Rastogi, Suresh Thummalapenta, Thomas Zimmermann, Nachiappan Nagappan, J. Czerwonka","doi":"10.1109/ESEM.2015.7321212","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321212","url":null,"abstract":"Hiring top talent is essential for any software company's success. After joining the company, new hires often spend weeks or months before making any major contribution and attaining the same productivity level as existing employees. We use the term ramp-up journey to refer to this transition of new hires from novice to experts. There can be several factors, such as lack of experience or lack of familiarity with processes unique to the new company, which influence the ramp-up journey. To understand such aids and impediments in the ramp-up journey, we conducted a study by analyzing data extracted from version control systems of eight large and popular product groups in Microsoft with several thousand software developers. In particular, we studied two aspects of the ramp-up journey. First, we studied time taken to make the first check-in into the version control system, an important milestone in the ramp-up journey indicating the first contribution. Second, we analyzed the time taken to reach the same productivity level as existing employees in terms of check-ins. We further augmented our quantitative study with qualitative results derived by surveying 411 professional developers. Our study produced promising results, including factors such as having a mentor, prior knowledge of required skill sets, and proactively asking questions, that could help reduce the ramp-up journey of new hires.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132123756","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 1

Using Trac for Empirical Data Collection and Analysis in Developing Small and Medium-Sized Enterprise Systems 在中小企业系统开发中使用Trac进行实证数据收集与分析

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321217

Naoki Ohsugi, Kyohei Fushida, Nobuto Inoguchi, Hiroyuki Arai, Hiroyuki Yamanaka, Takashi Niwa, Misa Fujinuki, Motohisa Tomura, Tuyoshi Kitani

{"title":"Using Trac for Empirical Data Collection and Analysis in Developing Small and Medium-Sized Enterprise Systems","authors":"Naoki Ohsugi, Kyohei Fushida, Nobuto Inoguchi, Hiroyuki Arai, Hiroyuki Yamanaka, Takashi Niwa, Misa Fujinuki, Motohisa Tomura, Tuyoshi Kitani","doi":"10.1109/ESEM.2015.7321217","DOIUrl":"https://doi.org/10.1109/ESEM.2015.7321217","url":null,"abstract":"This paper describes practical case studies of using Trac as a platform for collecting empirical data in the development of small and medium-sized enterprise systems. Project managers have been using various empirical data such as size, development efforts and number of bugs found. These data are vital for management, although the cost entailed is not small in preparing an effective combination of measurement tools, procedures and continuous monitoring to collect reliable data, and many small and medium-sized projects are constrained by budget limitations. This paper describes practical examples of data collection at low cost in the development of two enterprise systems. The examples consist of a small project (5 development personnel at the peak period, down to 3 during the maintenance) and a medium-sized project (80 personnel at the peak, down to 28), used to develop two different enterprise systems. Over 29 months, ten basic metrics and seven derived metrics were collected regarding effort, size and quality, and were used for progress management, estimation, and quality assurance.","PeriodicalId":258843,"journal":{"name":"2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124790678","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 3

The Importance of Being Isolated: An Empirical Study on Chromium Reviews 被隔离的重要性:铬评论的实证研究

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321215

Subhajit Datta, Devarshi Bhatt, Manish Jain, Proshanta Sarkar, S. Sarkar

引用次数: 2

Identifying Metrics' Biases When Measuring or Approximating Size in Heterogeneous Languages 在异质语言中测量或近似大小时识别度量标准的偏差

2015 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM) Pub Date : 2015-10-01 DOI: 10.1109/ESEM.2015.7321201

R. Hebig, Jesper Derehag, M. Chaudron

引用次数: 3