2012 28th IEEE International Conference on Software Maintenance (ICSM)最新文献_第5页

An empirical study on requirements traceability using eye-tracking 基于眼动追踪的需求追溯实证研究

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405271

Nasir Ali, Zohreh Sharafi, Yann-Gaël Guéhéneuc, G. Antoniol

{"title":"An empirical study on requirements traceability using eye-tracking","authors":"Nasir Ali, Zohreh Sharafi, Yann-Gaël Guéhéneuc, G. Antoniol","doi":"10.1109/ICSM.2012.6405271","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405271","url":null,"abstract":"Requirements traceability (RT) links help developers to understand programs and ensure that their source code is consistent with its documentation. Creating RT links is a laborious and resource-consuming task. Information Retrieval (IR) techniques are useful to automatically recover traceability links. However, IR-based approaches typically have low accuracy (precision and recall) and, thus, creating RT links remains a human intensive process. We conjecture that understanding how developers verify RT links could help improve the accuracy of IR-based approaches to recover RT links. Consequently, we perform an empirical study consisting of two controlled experiments. First, we use an eye-tracking system to capture developers' eye movements while they verify RT links. We analyse the obtained data to identify and rank developers' preferred source code entities (SCEs), e.g., class names, method names. Second, we use the ranked SCEs to propose two new weighting schemes called SE/IDF (source code entity/inverse document frequency) and DOI/IDF (domain or implementation/inverse document frequency) to recover RT links combined with an IR technique. SE/IDF is based on the developers preferred SCEs to verify RT links. DOI/IDF is an extension of SE/IDF distinguishing domain and implementation concepts. We use LSI combined with SE/IDF, DOI/IDF, and TF/IDF to show, using two systems, iTrust and Pooka, that LSIDOI/IDF statistically improves the accuracy of the recovered RT links over LSITF/IDF.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"70 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128782387","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}

引用次数: 38

Understanding model evolution through semantically lifting model differences with SiLift 通过语义提升与SiLift的模型差异来理解模型演化

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405342

Timo Kehrer, U. Kelter, Manuel Ohrndorf, Tim Sollbach

引用次数: 55

Code coverage-based regression test selection and prioritization in WebKit WebKit中基于代码覆盖率的回归测试选择和优先级

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405252

Árpád Beszédes, T. Gergely, L. Schrettner, J. Jász, Laszlo Lango, T. Gyimóthy

{"title":"Code coverage-based regression test selection and prioritization in WebKit","authors":"Árpád Beszédes, T. Gergely, L. Schrettner, J. Jász, Laszlo Lango, T. Gyimóthy","doi":"10.1109/ICSM.2012.6405252","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405252","url":null,"abstract":"Automated regression testing is often crucial in order to maintain the quality of a continuously evolving software system. However, in many cases regression test suites tend to grow too large to be suitable for full re-execution at each change of the software. In this case selective retesting can be applied to reduce the testing cost while maintaining similar defect detection capability. One of the basic test selection methods is the one based on code coverage information, where only those tests are included that cover some parts of the changes. We experimentally applied this method to the open source web browser engine project WebKit to find out the technical difficulties and the expected benefits if this method is to be introduced into the actual build process. Although the principle is simple, we had to solve a number of technical issues, so we report how this method was adapted to be used in the official build environment. Second, we present results about the selection capabilities for a selected set of revisions of WebKit, which are promising. We also applied different test case prioritization strategies to further reduce the number of tests to execute. We explain these strategies and compare their usefulness in terms of defect detection and test suite reduction.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"148 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121230686","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}

引用次数: 47

Inferring semantically related software terms and their taxonomy by leveraging collaborative tagging 通过利用协作标记推断语义相关的软件术语及其分类

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405332

Shaowei Wang, D. Lo, Lingxiao Jiang

{"title":"Inferring semantically related software terms and their taxonomy by leveraging collaborative tagging","authors":"Shaowei Wang, D. Lo, Lingxiao Jiang","doi":"10.1109/ICSM.2012.6405332","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405332","url":null,"abstract":"Many software engineering tasks, such as feature location and duplicate bug report detection, leverages similarities among textual corpora. However, due to the different words used by developers to express the same concept, exact matching of words is insufficient. One document can contain a particular word while the other document may contain another word that is semantically related but is not the same. Such word differences may cause inaccuracies in subsequent software engineering tasks. Recently, tagging has impacted the software engineering community. Developers increasingly use tags to describe important features of a software product. Many project hosting sites allow users to tag various projects with their own words. It becomes increasingly important to understand and relate these tags. Based on the tags available from software project hosting websites, we propose a similarity metric to infer semantically related terms, each of which is a tag, and build a taxonomy that could further describe the relationships among these terms. We have built a sample taxonomy from tens of thousands of projects and their tags. Our user studies show that our proposed similarity metric for tags are indeed related to the semantic similarity of the terms, and the resultant semantic taxonomy among terms is reasonably good.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116252372","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}

引用次数: 58

Sustainability guidelines for long-living software systems 长期软件系统的可持续性指导方针

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405316

Zoya Durdik, Benjamin Klatt, H. Koziolek, K. Krogmann, J. Stammel, R. Weiss

引用次数: 70

When would this bug get reported? 什么时候会报告这个bug ?

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405302

Ferdian Thung, D. Lo, Lingxiao Jiang, Lucia, Foyzur Rahman, Premkumar T. Devanbu

{"title":"When would this bug get reported?","authors":"Ferdian Thung, D. Lo, Lingxiao Jiang, Lucia, Foyzur Rahman, Premkumar T. Devanbu","doi":"10.1109/ICSM.2012.6405302","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405302","url":null,"abstract":"Not all bugs in software would be experienced and reported by end users right away: Some bugs manifest themselves quickly and may be reported by users a few days after they get into the code base; others manifest many months or even years later, and may only be experienced and reported by a small number of users. We refer to the period of time between the time when a bug is introduced into code and the time when it is reported by a user as bug reporting latency. Knowledge of bug reporting latencies has an implication on prioritization of bug fixing activities-bugs with low reporting latencies may be fixed earlier than those with high latencies to shift debugging resources towards bugs highly concerning users. To investigate bug reporting latencies, we analyze bugs from three Java software systems: AspectJ, Rhino, and Lucene. We extract bug reporting data from their version control repositories and bug tracking systems, identify bug locations based on bug fixes, and back-trace bug introducing time based on change histories of the buggy code. Also, we remove non-essential changes, and most importantly, recover root causes of bugs from their treatments/fixes. We then calculate the bug reporting latencies, and find that bugs have diverse reporting latencies. Based on the calculated reporting latencies and features we extract from bugs, we build classification models that can predict whether a bug would be reported early (within 30 days) or later, which may be helpful for prioritizing bug fixing activities. Our evaluation on the three software systems shows that our bug reporting latency prediction models could achieve an AUC (Area Under the Receiving Operating Characteristics Curve) of 70.869%.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126720530","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

A framework for incremental quality analysis of large software systems 用于大型软件系统的增量质量分析的框架

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405318

V. Bauer, L. Heinemann, B. Hummel, Elmar Jürgens, M. Conradt

引用次数: 14

LINSEN: An efficient approach to split identifiers and expand abbreviations LINSEN:分割标识符和展开缩写的有效方法

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405277

A. Corazza, S. Martino, Valerio Maggio

{"title":"LINSEN: An efficient approach to split identifiers and expand abbreviations","authors":"A. Corazza, S. Martino, Valerio Maggio","doi":"10.1109/ICSM.2012.6405277","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405277","url":null,"abstract":"Information Retrieval (IR) techniques are being exploited by an increasing number of tools supporting Software Maintenance activities. Indeed the lexical information embedded in the source code can be valuable for tasks such as concept location, clustering or recovery of traceability links. The application of such IR-based techniques relies on the consistency of the lexicon available in the different artifacts, and their effectiveness can worsen if programmers introduce abbreviations (e.g: rect) and/or do not strictly follow naming conventions such as Camel Case (e.g: UTFtoASCII). In this paper we propose an approach to automatically split identifiers in their composing words, and expand abbreviations. The solution is based on a graph model and performs in linear time with respect to the size of the dictionary, taking advantage of an approximate string matching technique. The proposed technique exploits a number of different dictionaries, referring to increasingly broader contexts, in order to achieve a disambiguation strategy based on the knowledge gathered from the most appropriate domain. The approach has been compared to other splitting and expansion techniques, using freely available oracles for the identifiers extracted from 24 C/C++ and Java open source systems. Results show an improvement in both splitting and expanding performance, in addition to a strong enhancement in the computational efficiency.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122495280","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}

引用次数: 67

Triaging incoming change requests: Bug or commit history, or code authorship? 对传入的变更请求进行分类:Bug或提交历史记录，还是代码作者?

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405306

M. Vásquez, Kamal Hossen, Hoang Dang, Huzefa H. Kagdi, Malcom Gethers, D. Poshyvanyk

{"title":"Triaging incoming change requests: Bug or commit history, or code authorship?","authors":"M. Vásquez, Kamal Hossen, Hoang Dang, Huzefa H. Kagdi, Malcom Gethers, D. Poshyvanyk","doi":"10.1109/ICSM.2012.6405306","DOIUrl":"https://doi.org/10.1109/ICSM.2012.6405306","url":null,"abstract":"There is a tremendous wealth of code authorship information available in source code. Motivated with the presence of this information, in a number of open source projects, an approach to recommend expert developers to assist with a software change request (e.g., a bug fixes or feature) is presented. It employs a combination of an information retrieval technique and processing of the source code authorship information. The relevant source code files to the textual description of a change request are first located. The authors listed in the header comments in these files are then analyzed to arrive at a ranked list of the most suitable developers. The approach fundamentally differs from its previously reported counterparts, as it does not require software repository mining. Neither does it require training from past bugs/issues, which is often done with sophisticated techniques such as machine learning, nor mining of source code repositories, i.e., commits. An empirical study to evaluate the effectiveness of the approach on three open source systems, ArgoUML, JEdit, and MuCommander, is reported. Our approach is compared with two representative approaches: (1) using machine learning on past bug reports, and (2) based on commit logs. The presented approach is found to provide recommendation accuracies that are equivalent or better than the two compared approaches. These findings are encouraging, as it opens up a promising and orthogonal possibility of recommending developers without the need of any historical change information.","PeriodicalId":348790,"journal":{"name":"2012 28th IEEE International Conference on Software Maintenance (ICSM)","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126667242","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}

引用次数: 101

Measuring software library stability through historical version analysis 通过历史版本分析测量软件库的稳定性

2012 28th IEEE International Conference on Software Maintenance (ICSM) Pub Date : 2012-09-23 DOI: 10.1109/ICSM.2012.6405296

S. Raemaekers, A. Deursen, Joost Visser

引用次数: 133