2016 23rd Asia-Pacific Software Engineering Conference (APSEC)最新文献_第5页

EXPSOL: Recommending Online Threads for Exception-Related Bug Reports 为异常相关的Bug报告推荐在线线程

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.015

Xiaoning Liu, Beijun Shen, Hao Zhong, Jiangang Zhu

{"title":"EXPSOL: Recommending Online Threads for Exception-Related Bug Reports","authors":"Xiaoning Liu, Beijun Shen, Hao Zhong, Jiangang Zhu","doi":"10.1109/APSEC.2016.015","DOIUrl":"https://doi.org/10.1109/APSEC.2016.015","url":null,"abstract":"An exception-related bug is a kind of program bug which causes exceptions. During software maintenance, when programmers repair exception-related bugs, they typically analyze thrown exceptions to understand the root causes of such bugs. When encountering unfamiliar thrown exceptions, programmers often refer to online forum threads (e.g. StackOverflow) to understand how to fix them. Although some general search engines are available and some research tools are proposed, they are insufficient to recommend threads for exception-related bugs from large-scale online resources. In this paper, we propose an approach, named EXPSOL, which recommends online threads as solutions for a newly reported exception-related bug with a model trained by support vector machines. We conduct two evaluations on thousands of threads from StackOverflow and fixed issues from GitHub. The results of our first evaluation show the significance of our internal features and highlight the importance of integrating different features. The results of our second evaluation show that, EXPSOL performs better in mean average precision, mean reciprocal rank and recall than those of the Google search engine, the internal search engine of StackOverflow, and other existing approaches.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"83 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116230507","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}

引用次数: 8

An Incremental V-Model Process for Automotive Development 汽车开发的增量v模型过程

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.040

Bohan Liu, He Zhang, Saichun Zhu

引用次数: 16

Dataset Coverage for Testing Machine Learning Computer Programs 测试机器学习计算机程序的数据集覆盖

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.049

S. Nakajima, Hai Ngoc Bui

引用次数: 30

Masking Soft Errors with Static Bitwise Analysis 用静态位分析掩盖软错误

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.047

Jianjun Xu, Xiankai Meng, QingPing Tan, Jingling Xue

{"title":"Masking Soft Errors with Static Bitwise Analysis","authors":"Jianjun Xu, Xiankai Meng, QingPing Tan, Jingling Xue","doi":"10.1109/APSEC.2016.047","DOIUrl":"https://doi.org/10.1109/APSEC.2016.047","url":null,"abstract":"Due to continuous improvements in the VLSI technologies, the dependability of computing, caused by soft errors, has become increasingly a design challenge. Current protection techniques usually incur significant economic costs, performance degradation or resource consumption. This paper introduces a lightweight software approach for mitigating soft errors. By exploiting the facts that many data values have narrow width or constant bits, indicating that a large fraction of binary bits are unused or constant, we can predict these data values before program execution. First of all, invariants concerning bit-level data widths and values are identified by performing two bitwise data-flow analyses. Based on the bitwise analysis results, the masking operations are inserted to clear the possible errors in the known-value bits for reducing the window of vulnerability. Then the program reliability is improved with minimum penalty. To improve the effectiveness, the covered mask analysis can remove the non-vital masking operations without affecting the dependability. We have implemented our approach in the LLVM compiler. The fault injection experimental results for the MiBench benchmarks indicate that our approach improves the reliability of programs by 8.03% while incurring only 1.61% performance overhead.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122113757","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}

引用次数: 0

Toward Developer-like Automated Program Repair — Modification Comparisons between GenProg and Developers 面向开发人员的自动程序修复- GenProg和开发人员之间的修改比较

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.042

Hiroki Nakajima, Yoshiki Higo, Haruki Yokoyama, S. Kusumoto

{"title":"Toward Developer-like Automated Program Repair — Modification Comparisons between GenProg and Developers","authors":"Hiroki Nakajima, Yoshiki Higo, Haruki Yokoyama, S. Kusumoto","doi":"10.1109/APSEC.2016.042","DOIUrl":"https://doi.org/10.1109/APSEC.2016.042","url":null,"abstract":"Automated program repair is a way to reduce costs on program debuggingto a large extent. Repair techniques using genetic programming havebeen attracting much attention. They were applied to actual softwaresystems and they were able to fix several dozen of actual faults. However, programs generated by such techniques often include some sourcecode changes not related to fixing a given fault even if they pass allgiven test cases. Furthermore, some researchers found that suchtechniques occasionally induce new faults which are not covered byexisting test cases. The reason why those problems arise is that suchtechniques consider only given test cases. On the other hand, developers consider program behaviors not covered by test cases. Thus, those problems arise less frequently in programs modified by developers. Consequently, the authors suppose that if we make automated programmodifications close to developers' ones, we may be able to relieve thoseproblems. At this moment, there is no research study investigatingdifferences between automated modifications and developers' ones. Inthis paper, we compare GenProg's modifications with developers'ones for the same faults. As a result, we found that developers tend to(1) change more different functions, (2) change control flows in sourcecode, and (3) add/delete more code lines.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"305 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123121972","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}

引用次数: 7

Guiding Identification of Missing Scenarios for Dynamic Feature Location 动态特征定位中缺失场景的指导性识别

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.068

Shinpei Hayashi, H. Kazato, Takashi Kobayashi, T. Oshima, Katsuyuki Natsukawa, T. Hoshino, M. Saeki

引用次数: 4

Examination of Coding Violations Focusing on Their Change Patterns over Releases 检查代码违例，关注它们在发布版本上的变更模式

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.027

Aji Ery Burhandenny, Hirohisa Aman, Minoru Kawahara

{"title":"Examination of Coding Violations Focusing on Their Change Patterns over Releases","authors":"Aji Ery Burhandenny, Hirohisa Aman, Minoru Kawahara","doi":"10.1109/APSEC.2016.027","DOIUrl":"https://doi.org/10.1109/APSEC.2016.027","url":null,"abstract":"Code review is an essential activity to ensure the quality of code being developed, and there have been static code checkers for aiding an effective code review. However, such tools have not been actively utilized in the world of programmers due to a lot of coding violations (warning) produced by tools and their false-positiveness. In order to analyze the automatically pointed violations and the actual attentions which programmers paid to those violations, this paper proposes a novel metric— the Index of Programmers' Attention (IPA)—and conducts an empirical study focusing on the change patterns of violations over the releases of popular seven open source software products, under two research questions (RQs): (RQ1) What kind of coding violations are related to the parts that many programmers tend to improve? and what kind of coding violations are likely to be disregarded?; (RQ2) How can we reduce the meaningless violations for programmers by omitting disregarded coding violations?The empirical results showed the following findings: (1) important violations (having high IPA values) may vary from project to project; (2) there are some unimportant violations common to different projects, but they are a minority of automatically detected violations (about 12%). Therefore, while many violations may be made by a code checker, most of them are likely to be worthy in improving the code quality, and it is ineffective to reduce the violations by eliminating such unimportant violations.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133752501","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}

引用次数: 5

Does the Role Matter? An Investigation of the Code Quality of Casual Contributors in GitHub 角色重要吗?GitHub中临时贡献者的代码质量调查

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.018

Yao Lu, Xinjun Mao, Zude Li, Yang Zhang, Tao Wang, Gang Yin

{"title":"Does the Role Matter? An Investigation of the Code Quality of Casual Contributors in GitHub","authors":"Yao Lu, Xinjun Mao, Zude Li, Yang Zhang, Tao Wang, Gang Yin","doi":"10.1109/APSEC.2016.018","DOIUrl":"https://doi.org/10.1109/APSEC.2016.018","url":null,"abstract":"For popular Open Source Software (OSS) projects there are always a large number of worldwide developers who have been glued to making code contributions, while most of these developers play the role of casual contributors due to their very limited code commits (for fixing defects and enhancing features, casually). The frequent turnover of such group of casual developers and the wide variations among their coding experiences challenge the project management on code and quality.This paper describes a case study which aims to estimate the quality of code made by casual contributors in 21 popular GitHub projects. The results of this case study show that: (1) casual contributors introduced greater quantity and severity of Code Quality Issues (CQIs) than main contributors; (2) developers who contribute in different projects as main and casual contributors didn't perform statistically differently in terms of code quality; (3) casual contributors who have few project stars introduced more CQIs than those who have many. Furthermore, the paper lists the CQI categories which are most frequently introduced by casual contributors in the investigated projects. These findings provide valuable insights into code quality in the OSS context, and can guide OSS developers in improving the quality of the code contributions.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129488544","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

History-Based Test Case Prioritization for Failure Information 失败信息的基于历史的测试用例优先级

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.066

Younghwan Cho, Jeongho Kim, Eunseok Lee

{"title":"History-Based Test Case Prioritization for Failure Information","authors":"Younghwan Cho, Jeongho Kim, Eunseok Lee","doi":"10.1109/APSEC.2016.066","DOIUrl":"https://doi.org/10.1109/APSEC.2016.066","url":null,"abstract":"From regression tests, developers seek to determine not only the existence of faults, but also failure information such as what test cases failed. Failure information can assist in identifying suspicious modules or functions in order to fix the detected faults. In continuous integration environments, this can also help managers of the source code repository address unexpected situations caused by regression faults. We introduce an approach, referred to as AFSAC, which is a test case prioritization technique based on history data, that can be used to effectively obtain failure information. Our approach is composed of two stages. First, we statistically analyze the failure history for each test case to order the test cases. Next, we reorder the test cases utilizing the correlation data of test cases acquired by previous test results. We performed an empirical study on two open-source Apache software projects (i.e., Tomcat and Camel) to evaluate our approach. The results of the empirical study show that our approach provides failure information to testers and developers more effectively than other prioritization techniques, and each prioritizing method of our approach improves the ability to obtain failure information.","PeriodicalId":339123,"journal":{"name":"2016 23rd Asia-Pacific Software Engineering Conference (APSEC)","volume":"140 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115757459","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}

引用次数: 20

Does it Fit Me Better? User Segmentation in Requirements Engineering 它更适合我吗?需求工程中的用户分割

2016 23rd Asia-Pacific Software Engineering Conference (APSEC) Pub Date : 1900-01-01 DOI: 10.1109/APSEC.2016.020

Mohammadhossein Sherkat, Tim Miller, Antonette Mendoza

引用次数: 3