Ana Carla Bibiano, Anderson G. Uchôa, W. K. Assunção, Daniel Oliveira, T. Colanzi, S. Vergilio, Alessandro F. Garcia
{"title":"Composite refactoring: Representations, characteristics and effects on software projects","authors":"Ana Carla Bibiano, Anderson G. Uchôa, W. K. Assunção, Daniel Oliveira, T. Colanzi, S. Vergilio, Alessandro F. Garcia","doi":"10.2139/ssrn.4119519","DOIUrl":"https://doi.org/10.2139/ssrn.4119519","url":null,"abstract":"","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130763134","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}
Julian Frattini, D. Fucci, Daniel Mendez, R. Spínola, Vladimir Mandic, Nebojša Taušan, M. Ahmad, J. Gonzalez-Huerta
Context: Advances in technical debt research demonstrate the benefits of applying the financial debt metaphor to support decision-making in software development activities. Although decision-making during requirements engineering has significant consequences, the debt metaphor in requirements engineering is inadequately explored. Objective: We aim to conceptualize how the debt metaphor applies to requirements engineering by organizing concepts related to practitioners' understanding and managing of requirements engineering debt (RED). Method: We conducted two in-depth expert interviews to identify key requirements engineering debt concepts and construct a survey instrument. We surveyed 69 practitioners worldwide regarding their perception of the concepts and developed an initial analytical theory. Results: We propose a RED theory that aligns key concepts from technical debt research but emphasizes the specific nature of requirements engineering. In particular, the theory consists of 23 falsifiable propositions derived from the literature, the interviews, and survey results. Conclusions: The concepts of requirements engineering debt are perceived to be similar to their technical debt counterpart. Nevertheless, measuring and tracking requirements engineering debt are immature in practice. Our proposed theory serves as the first guide toward further research in this area.
{"title":"An initial Theory to Understand and Manage Requirements Engineering Debt in Practice","authors":"Julian Frattini, D. Fucci, Daniel Mendez, R. Spínola, Vladimir Mandic, Nebojša Taušan, M. Ahmad, J. Gonzalez-Huerta","doi":"10.2139/ssrn.4252130","DOIUrl":"https://doi.org/10.2139/ssrn.4252130","url":null,"abstract":"Context: Advances in technical debt research demonstrate the benefits of applying the financial debt metaphor to support decision-making in software development activities. Although decision-making during requirements engineering has significant consequences, the debt metaphor in requirements engineering is inadequately explored. Objective: We aim to conceptualize how the debt metaphor applies to requirements engineering by organizing concepts related to practitioners' understanding and managing of requirements engineering debt (RED). Method: We conducted two in-depth expert interviews to identify key requirements engineering debt concepts and construct a survey instrument. We surveyed 69 practitioners worldwide regarding their perception of the concepts and developed an initial analytical theory. Results: We propose a RED theory that aligns key concepts from technical debt research but emphasizes the specific nature of requirements engineering. In particular, the theory consists of 23 falsifiable propositions derived from the literature, the interviews, and survey results. Conclusions: The concepts of requirements engineering debt are perceived to be similar to their technical debt counterpart. Nevertheless, measuring and tracking requirements engineering debt are immature in practice. Our proposed theory serves as the first guide toward further research in this area.","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"144 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123280901","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}
{"title":"Parallel evolutionary test case generation for web applications","authors":"Wen Wang, Shumei Wu, Zheng Li, Ruilian Zhao","doi":"10.2139/ssrn.4074850","DOIUrl":"https://doi.org/10.2139/ssrn.4074850","url":null,"abstract":"","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"105 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-11-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133095858","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}
Pub Date : 2022-08-01DOI: 10.1016/j.infsof.2022.107058
V. Stray, Rashina Hoda, M. Paasivaara, Valentina Lenarduzzi, D. Méndez
{"title":"Theories in Agile Software Development: Past, Present, and Future Introduction to the XP 2020 Special Section","authors":"V. Stray, Rashina Hoda, M. Paasivaara, Valentina Lenarduzzi, D. Méndez","doi":"10.1016/j.infsof.2022.107058","DOIUrl":"https://doi.org/10.1016/j.infsof.2022.107058","url":null,"abstract":"","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"118486627","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}
Pub Date : 2022-07-11DOI: 10.48550/arXiv.2207.05132
Arghavan Moradi Dakhel, M. Desmarais, Foutse Khomh
Accurate assessment of the domain expertise of developers is important for assigning the proper candidate to contribute to a project or to attend a job role. Since the potential candidate can come from a large pool, the automated assessment of this domain expertise is a desirable goal. While previous methods have had some success within a single software project, the assessment of a developer's domain expertise from contributions across multiple projects is more challenging. In this paper, we employ doc2vec to represent the domain expertise of developers as embedding vectors. These vectors are derived from different sources that contain evidence of developers' expertise, such as the description of repositories that they contributed, their issue resolving history, and API calls in their commits. We name it dev2vec and demonstrate its effectiveness in representing the technical specialization of developers. Our results indicate that encoding the expertise of developers in an embedding vector outperforms state-of-the-art methods and improves the F1-score up to 21%. Moreover, our findings suggest that ``issue resolving history'' of developers is the most informative source of information to represent the domain expertise of developers in embedding spaces.
{"title":"Dev2vec: Representing Domain Expertise of Developers in an Embedding Space","authors":"Arghavan Moradi Dakhel, M. Desmarais, Foutse Khomh","doi":"10.48550/arXiv.2207.05132","DOIUrl":"https://doi.org/10.48550/arXiv.2207.05132","url":null,"abstract":"Accurate assessment of the domain expertise of developers is important for assigning the proper candidate to contribute to a project or to attend a job role. Since the potential candidate can come from a large pool, the automated assessment of this domain expertise is a desirable goal. While previous methods have had some success within a single software project, the assessment of a developer's domain expertise from contributions across multiple projects is more challenging. In this paper, we employ doc2vec to represent the domain expertise of developers as embedding vectors. These vectors are derived from different sources that contain evidence of developers' expertise, such as the description of repositories that they contributed, their issue resolving history, and API calls in their commits. We name it dev2vec and demonstrate its effectiveness in representing the technical specialization of developers. Our results indicate that encoding the expertise of developers in an embedding vector outperforms state-of-the-art methods and improves the F1-score up to 21%. Moreover, our findings suggest that ``issue resolving history'' of developers is the most informative source of information to represent the domain expertise of developers in embedding spaces.","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"88 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-07-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114992862","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}
Pub Date : 2022-05-01DOI: 10.1016/j.infsof.2022.106824
A. Amna, G. Poels
{"title":"Ambiguity in user stories: A systematic literature review","authors":"A. Amna, G. Poels","doi":"10.1016/j.infsof.2022.106824","DOIUrl":"https://doi.org/10.1016/j.infsof.2022.106824","url":null,"abstract":"","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"109 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2022-05-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"119468144","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}
Pub Date : 2021-10-01DOI: 10.1016/J.INFSOF.2021.106627
Dragica Ranković, N. Ranković, M. Ivanović, L. Lazić
{"title":"Convergence rate of Artificial Neural Networks for estimation in software development projects","authors":"Dragica Ranković, N. Ranković, M. Ivanović, L. Lazić","doi":"10.1016/J.INFSOF.2021.106627","DOIUrl":"https://doi.org/10.1016/J.INFSOF.2021.106627","url":null,"abstract":"","PeriodicalId":133352,"journal":{"name":"Inf. Softw. Technol.","volume":"2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2021-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117882421","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}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：