High-level software requirements and iteration changes: a predictive model. Blincoe, K., Dehghan, A., Salaou, A., Neal, A., Linaker, J., & Damian, D. Empirical Software Engineering, 24(3):1610–1648, 2019. tex.author_keywords: Completion prediction; Machine learning; Mining software repositories; Release planning; Software requirements tex.document_type: Article tex.source: Scopus
Paper doi abstract bibtex Knowing whether a software feature will be completed in its planned iteration can help with release planning decisions. However, existing research has focused on predictions of only low-level software tasks, like bug fixes. In this paper, we describe a mixed-method empirical study on three large IBM projects. We investigated the types of iteration changes that occur. We show that up to 54
@article{Blincoe20191610,
title = {High-level software requirements and iteration changes: a predictive model},
volume = {24},
url = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85055479920&doi=10.1007%2fs10664-018-9656-z&partnerID=40&md5=ee7395b9fb0e8aea21dad136c911f1a3},
doi = {10.1007/s10664-018-9656-z},
abstract = {Knowing whether a software feature will be completed in its planned iteration can help with release planning decisions. However, existing research has focused on predictions of only low-level software tasks, like bug fixes. In this paper, we describe a mixed-method empirical study on three large IBM projects. We investigated the types of iteration changes that occur. We show that up to 54},
number = {3},
journal = {Empirical Software Engineering},
author = {Blincoe, K. and Dehghan, A. and Salaou, A.-D. and Neal, A. and Linaker, J. and Damian, D.},
year = {2019},
note = {tex.author\_keywords: Completion prediction; Machine learning; Mining software repositories; Release planning; Software requirements
tex.document\_type: Article
tex.source: Scopus},
keywords = {\#nosource},
pages = {1610--1648},
}
Downloads: 0
{"_id":"coJR7CBvzCvXDhBRd","bibbaseid":"blincoe-dehghan-salaou-neal-linaker-damian-highlevelsoftwarerequirementsanditerationchangesapredictivemodel-2019","author_short":["Blincoe, K.","Dehghan, A.","Salaou, A.","Neal, A.","Linaker, J.","Damian, D."],"bibdata":{"bibtype":"article","type":"article","title":"High-level software requirements and iteration changes: a predictive model","volume":"24","url":"https://www.scopus.com/inward/record.uri?eid=2-s2.0-85055479920&doi=10.1007%2fs10664-018-9656-z&partnerID=40&md5=ee7395b9fb0e8aea21dad136c911f1a3","doi":"10.1007/s10664-018-9656-z","abstract":"Knowing whether a software feature will be completed in its planned iteration can help with release planning decisions. However, existing research has focused on predictions of only low-level software tasks, like bug fixes. In this paper, we describe a mixed-method empirical study on three large IBM projects. We investigated the types of iteration changes that occur. We show that up to 54","number":"3","journal":"Empirical Software Engineering","author":[{"propositions":[],"lastnames":["Blincoe"],"firstnames":["K."],"suffixes":[]},{"propositions":[],"lastnames":["Dehghan"],"firstnames":["A."],"suffixes":[]},{"propositions":[],"lastnames":["Salaou"],"firstnames":["A.-D."],"suffixes":[]},{"propositions":[],"lastnames":["Neal"],"firstnames":["A."],"suffixes":[]},{"propositions":[],"lastnames":["Linaker"],"firstnames":["J."],"suffixes":[]},{"propositions":[],"lastnames":["Damian"],"firstnames":["D."],"suffixes":[]}],"year":"2019","note":"tex.author_keywords: Completion prediction; Machine learning; Mining software repositories; Release planning; Software requirements tex.document_type: Article tex.source: Scopus","keywords":"#nosource","pages":"1610–1648","bibtex":"@article{Blincoe20191610,\n\ttitle = {High-level software requirements and iteration changes: a predictive model},\n\tvolume = {24},\n\turl = {https://www.scopus.com/inward/record.uri?eid=2-s2.0-85055479920&doi=10.1007%2fs10664-018-9656-z&partnerID=40&md5=ee7395b9fb0e8aea21dad136c911f1a3},\n\tdoi = {10.1007/s10664-018-9656-z},\n\tabstract = {Knowing whether a software feature will be completed in its planned iteration can help with release planning decisions. However, existing research has focused on predictions of only low-level software tasks, like bug fixes. In this paper, we describe a mixed-method empirical study on three large IBM projects. We investigated the types of iteration changes that occur. We show that up to 54},\n\tnumber = {3},\n\tjournal = {Empirical Software Engineering},\n\tauthor = {Blincoe, K. and Dehghan, A. and Salaou, A.-D. and Neal, A. and Linaker, J. and Damian, D.},\n\tyear = {2019},\n\tnote = {tex.author\\_keywords: Completion prediction; Machine learning; Mining software repositories; Release planning; Software requirements\ntex.document\\_type: Article\ntex.source: Scopus},\n\tkeywords = {\\#nosource},\n\tpages = {1610--1648},\n}\n\n\n\n","author_short":["Blincoe, K.","Dehghan, A.","Salaou, A.","Neal, A.","Linaker, J.","Damian, D."],"key":"Blincoe20191610","id":"Blincoe20191610","bibbaseid":"blincoe-dehghan-salaou-neal-linaker-damian-highlevelsoftwarerequirementsanditerationchangesapredictivemodel-2019","role":"author","urls":{"Paper":"https://www.scopus.com/inward/record.uri?eid=2-s2.0-85055479920&doi=10.1007%2fs10664-018-9656-z&partnerID=40&md5=ee7395b9fb0e8aea21dad136c911f1a3"},"keyword":["#nosource"],"metadata":{"authorlinks":{}},"html":""},"bibtype":"article","biburl":"https://bibbase.org/zotero/maraee75","dataSources":["QsdoGJFsT9yBRZrcG","PjpadRRabZA7FRKpn"],"keywords":["#nosource"],"search_terms":["high","level","software","requirements","iteration","changes","predictive","model","blincoe","dehghan","salaou","neal","linaker","damian"],"title":"High-level software requirements and iteration changes: a predictive model","year":2019}