Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering最新文献_第5页

On the Benefits/Limitations of Agile Software Development: An Interview Study with Brazilian Companies 敏捷软件开发的好处/局限性:对巴西公司的访谈研究

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084278

F. Kamei, G. Pinto, Bruno Cartaxo, A. Vasconcelos

{"title":"On the Benefits/Limitations of Agile Software Development: An Interview Study with Brazilian Companies","authors":"F. Kamei, G. Pinto, Bruno Cartaxo, A. Vasconcelos","doi":"10.1145/3084226.3084278","DOIUrl":"https://doi.org/10.1145/3084226.3084278","url":null,"abstract":"Context: For more than 15 years, Agile Software Development (ASD) has been used to improve software development, process, and quality. However, there are scenarios where the effectiveness of these methods and practices has not been rigorously evaluated. Objective: Understand the benefits and limitations related to these methods and practices in a particular context: two software companies based on Pernambuco's Technology Park, Brazil. Method: In this paper, we conducted 22 semi-structured interviews to understand the benefits and limitations of ASD in an industrial context. The data were extracted using open coding and analyzed through qualitative techniques. Results: Our preliminary analysis identified a core of 28 benefits and 20 limitations with the usage of ASD. As for benefits, we found that facilitates project monitoring and tracking as well as the interaction and collaboration. As for limitations, we found that it difficulty working with user stories and to work with large teams. Conclusion: This study serves as a practical guide for software companies interested in adopting and improving the use of ASD.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129813572","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}

引用次数: 12

Motivation and Autonomy in Global Software Development: An Empirical Study 全球软件开发中的动机与自主性:一个实证研究

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084277

J. Noll, M. Razzak, Sarah Beecham

{"title":"Motivation and Autonomy in Global Software Development: An Empirical Study","authors":"J. Noll, M. Razzak, Sarah Beecham","doi":"10.1145/3084226.3084277","DOIUrl":"https://doi.org/10.1145/3084226.3084277","url":null,"abstract":"Distributed development involving globally distributed teams in different countries and timezones adds additional complexity into an already complex undertaking. This paper focuses on the effect of global software development on motivation. Specifically, we ask, what impact does misalignment between needed and actual autonomy have on global team motivation? We studied members of two distributed software development teams with different degrees of distribution, both following the Scrum approach to software development. One team's members are distributed across Ireland, England and Wales; the other has members in locations across Europe and North America. We observed the teams during their Scrum \"ceremonies,\" and interviewed each team member, during which asked we asked team members to rate their motivation on a 5 point ordinal scale. Considering both the reported motivation levels, and qualitative analysis of our observations and interviews, our results suggest that autonomy appears to be just one of three job aspects that affect motivation, the others being competence and relatedness. We hypothesize that (1) autonomy is a necessary but not sufficient condition for motivation among experienced team members, and (2) autonomy is not a motivator unless accompanied by sufficient competence.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116562452","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}

引用次数: 19

Evaluating Software Architecture Evaluation Methods: An Internal Replication 评估软件架构评估方法:内部复制

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084253

S. Abrahão, E. Insfrán

{"title":"Evaluating Software Architecture Evaluation Methods: An Internal Replication","authors":"S. Abrahão, E. Insfrán","doi":"10.1145/3084226.3084253","DOIUrl":"https://doi.org/10.1145/3084226.3084253","url":null,"abstract":"Context: The size and complexity of software systems along with the demand for ensuring quality requirements have fostered the interest in software architecture evaluation methods. Although several empirical studies have been reported, the actual body of knowledge is still insufficient. To address this concern, we presented a family of four controlled experiments that compares a recently proposed method, the Quality-Driven Architecture Derivation and Improvement (QuaDAI) method against the well-known Architecture Tradeoff Analysis Method (ATAM). Objective: To provide further evidence on the efficiency, effectiveness, and perceived satisfaction of participants using these two software architecture evaluation methods. We report the results of a differentiated internal replication study. Method: The same materials used in the baseline experiments were employed in this replication but the participants were sixteen practitioners. In addition, we used a simpler design to reduce the treatments' application sequences. Results: The participants obtained architectures with better quality when applying QuaDAI, and they found this method to be more useful and likely to be used than ATAM, but no difference in terms of efficiency and perceived ease of use were found. Conclusions: The results are in line with the baseline experiments and support the hypothesis that QuaDAI achieve better results than ATAM when performing architectural evaluations; however, further work is need to improve the methods usability.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134550828","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

Cataloging GitHub Repositories 对GitHub仓库进行编目

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084287

Abhishek Sharma, Ferdian Thung, Pavneet Singh Kochhar, Agus Sulistya, D. Lo

{"title":"Cataloging GitHub Repositories","authors":"Abhishek Sharma, Ferdian Thung, Pavneet Singh Kochhar, Agus Sulistya, D. Lo","doi":"10.1145/3084226.3084287","DOIUrl":"https://doi.org/10.1145/3084226.3084287","url":null,"abstract":"GitHub is one of the largest and most popular repository hosting service today, having about 14 million users and more than 54 million repositories as of March 2017. This makes it an excellent platform to find projects that developers are interested in exploring. GitHub showcases its most popular projects by cataloging them manually into categories such as DevOps tools, web application frameworks, and game engines. We propose that such cataloging should not be limited only to popular projects. We explore the possibility of developing such cataloging system by automatically extracting functionality descriptive text segments from readme files of GitHub repositories. These descriptions are then input to LDA-GA, a state-of-the-art topic modeling algorithm, to identify categories. Our preliminary experiments demonstrate that additional meaningful categories which complement existing GitHub categories can be inferred. Moreover, for inferred categories that match GitHub categories, our approach can identify additional projects belonging to them. Our experimental results establish a promising direction in realizing automatic cataloging system for GitHub.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115699140","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}

引用次数: 39

Towards Confidence with Capture-recapture Estimation: An Exploratory Study of Dependence within Inspections 用捕获-再捕获估计实现信心:检验中依赖性的探索性研究

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084250

Guoping Rong, Bohan Liu, He Zhang, Qiuping Zhang, Dong Shao

{"title":"Towards Confidence with Capture-recapture Estimation: An Exploratory Study of Dependence within Inspections","authors":"Guoping Rong, Bohan Liu, He Zhang, Qiuping Zhang, Dong Shao","doi":"10.1145/3084226.3084250","DOIUrl":"https://doi.org/10.1145/3084226.3084250","url":null,"abstract":"Background: Capture-ReCapture (CRC), as a technique for post-inspection defect estimation, has been studied in Software Engineering (SE) community since 1990s. While most studies focused on the performance evaluation of various CRC models and estimators, few have been done on the assessment of the credibility of estimation results, rendering the difficulty of decision-making for quality management when applying CRC for defect estimation. Objective: This research aims to explore and investigate a reliable and practical approach to assess the credibility of CRC based defect estimation. Method: One fundamental assumption of applying CRC method is the statistical independence of samples that can be measured by 'Coefficient of CoVariation' (CCV). We applied CCV as an indicator of the statistical dependence between the observations (i.e., the defects detected by inspectors), and assessed the estimation results of CRC with the published datasets in SE literature by examining the correlation between Relative Error (RE) and CCV. Based on the observed correlation, we further propose CĈV, which replaces the unknown N (the actual number of defects) with the estimated number (N), to assess the credibility of CRC estimates. Results: We found that most datasets are with non-zero CCVs and the R2 (Coefficient of Determination) of non-linear curve-fitting for their CCVs and REs is higher than 0.8. Conclusions: Our study shows the evidence that the statistical dependence among inspectors is ubiquitous in the existing CRC-related studies. Besides, the significant correlation between CCV (by CĈV in practice) and RE may enable the possibility of the assessment of CRC-based estimation in support of quality management.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"11 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114879119","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

Toward the use of blog articles as a source of evidence for software engineering research 将博客文章作为软件工程研究的证据来源

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084268

A. Williams, A. Rainer

{"title":"Toward the use of blog articles as a source of evidence for software engineering research","authors":"A. Williams, A. Rainer","doi":"10.1145/3084226.3084268","DOIUrl":"https://doi.org/10.1145/3084226.3084268","url":null,"abstract":"Background: Blog articles have potential value as a source of practitioner-generated evidence to complement already accepted sources of evidence in software engineering research e.g. interviews and surveys. To be valuable to research, a method for extracting the high quality articles from the vast quantity available needs to be developed. Objective: To better define the benefits and challenges, scope the problem, develop a set of criteria for evaluating blog articles to be used in the method, and propose research questions. Method: We conducted a two-phase pilot study, using a preliminary set of criteria, to explore the challenges of classifying blog articles. We analyse credibility criteria that have been used in previous research, and cross reference those criteria with previous research in evidence-based software engineering. Results: Based on our analysis, we decide that blog articles need to be rigorous, relevant, well written and experience based for them to be considered credible to researchers. Conclusion: Our work provides an overview of the problem domain, as well as presenting criteria and suggested measurements for these criteria. These can be used by others to find blog articles of potential value to their research.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122038370","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}

引用次数: 13

Hands-Free Research Workflow 免提研究工作流程

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084266

P. R. Lorenzo, J. Nalepa, L. Ramos, J. Ranilla

{"title":"Hands-Free Research Workflow","authors":"P. R. Lorenzo, J. Nalepa, L. Ramos, J. Ranilla","doi":"10.1145/3084226.3084266","DOIUrl":"https://doi.org/10.1145/3084226.3084266","url":null,"abstract":"Over the last years, research has been placed at the core of numerous software products resulting from the ubiquitous presence of multimedia devices in our lives. Besides the need of acquiring specialized hardware, performing reliable and reproducible research requires the exploitation of specialized tools that are not traditionally present in the agile enterprise ecosystem. This might be a factor that ultimately draws many organizations away from introducing research into their software products. In this work, we propose a hands-free workflow that exploits widely available tools in the enterprise, like source control (SC) and continuous integration (CI) systems. We demonstrate that this workflow acts as a single-step end-to-end solution, maximizing the usage of the available hardware, and ensuring the repeatability of the performed experiments. The probability of human errors is minimized by automating all file transfers, and feedback is provided at the end of every trial with the location of the results. Generated artifacts are automatically archived, alongside the initial conditions of the experiment allowing for its full recreation. Although in our solution we exploit Git and Jenkins, this workflow can also be implemented with any of the SC and CI tools typically available in the enterprise.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128767954","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

Attributes that Predict which Features to Fix: Lessons for App Store Mining 预测修复哪些功能的属性:应用商店挖掘的经验教训

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-06-15 DOI: 10.1145/3084226.3084246

Sherlock A. Licorish, Bastin Tony Roy Savarimuthu, Swetha Keertipati

{"title":"Attributes that Predict which Features to Fix: Lessons for App Store Mining","authors":"Sherlock A. Licorish, Bastin Tony Roy Savarimuthu, Swetha Keertipati","doi":"10.1145/3084226.3084246","DOIUrl":"https://doi.org/10.1145/3084226.3084246","url":null,"abstract":"Requirements engineering is assessed as the most important phase of the software development process. This process is especially challenging for app developers, who tend to gather crowd-based feedback after releasing their apps. This feedback is often voluminous, posing prioritization challenges for developers identifying features to fix or add. While previous work has identified frequently mentioned features, and some effort has been dedicated towards providing various prioritization and classification techniques, these do not quite address the prioritization challenge faced by app developers given voluminous app reviews. In fact, there is also need to assess the scale of app reviews' usefulness. We use content analysis and regression to contribute towards this cause by exploring the usefulness of app reviews, and the attributes that predict which app features to fix, respectively. Our outcomes show that reviews tended to either provide information of little value (i.e., no actionable information) or highlighted problems that may directly affect the functionality of app features. For two different apps, we also observe that features that were mentioned the most (the feature frequency attribute) in lower ranked reviews provided by users had the strongest predictive power for identifying severely broken features (as perceived by a developer). However, the ordering did not match with the frequency with which reports were made by users. There were also variances in the attributes that predict which features to fix, for the reviews of different apps. Review mining and prioritization challenges remain given variances in app reviews' content and structure. These findings also point to the need to redesign app review interfaces to consider how reviews are captured.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-06-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127726287","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}

引用次数: 26

On Using Active Learning and Self-training when Mining Performance Discussions on Stack Overflow 基于主动学习和自训练的堆栈溢出挖掘性能讨论

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-04-26 DOI: 10.1145/3084226.3084273

Markus Borg, Iben Lennerstad, R. Ros, E. Bjarnason

{"title":"On Using Active Learning and Self-training when Mining Performance Discussions on Stack Overflow","authors":"Markus Borg, Iben Lennerstad, R. Ros, E. Bjarnason","doi":"10.1145/3084226.3084273","DOIUrl":"https://doi.org/10.1145/3084226.3084273","url":null,"abstract":"Abundant data is the key to successful machine learning. However, supervised learning requires annotated data that are often hard to obtain. In a classification task with limited resources, Active Learning (AL) promises to guide annotators to examples that bring the most value for a classifier. AL can be successfully combined with self-training, i.e., extending a training set with the unlabelled examples for which a classifier is the most certain. We report our experiences on using AL in a systematic manner to train an SVM classifier for Stack Overflow posts discussing performance of software components. We show that the training examples deemed as the most valuable to the classifier are also the most difficult for humans to annotate. Despite carefully evolved annotation criteria, we report low inter-rater agreement, but we also propose mitigation strategies. Finally, based on one annotator's work, we show that self-training can improve the classification accuracy. We conclude the paper by discussing implication for future text miners aspiring to use AL and self-training.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-04-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117353864","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

On the Unhappiness of Software Developers 论软件开发人员的不快乐

Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering Pub Date : 2017-03-15 DOI: 10.1145/3084226.3084242

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang, P. Abrahamsson

{"title":"On the Unhappiness of Software Developers","authors":"D. Graziotin, Fabian Fagerholm, Xiaofeng Wang, P. Abrahamsson","doi":"10.1145/3084226.3084242","DOIUrl":"https://doi.org/10.1145/3084226.3084242","url":null,"abstract":"The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners. However, the literature suggests that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness. Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers. Simultaneously, a baseline assessment of (un)happiness and knowledge about how developers experience it are missing. In this paper, we broaden the understanding of unhappiness among software developers in terms of (1) the software developer population distribution of (un)happiness, and (2) the causes of unhappiness while developing software. We conducted a large-scale quantitative and qualitative survey, incorporating a psychometrically validated instrument for measuring (un)happiness, with 2 220 developers, yielding a rich and balanced sample of 1318 complete responses. Our results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains. We also identified 219 factors representing causes of unhappiness while developing software. Our results, which are available as open data, can act as guidelines for practitioners in management positions and developers in general for fostering happiness on the job. We suggest considering happiness in future studies of both human and technical aspects in software engineering.","PeriodicalId":192290,"journal":{"name":"Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-03-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129688393","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}

引用次数: 59