@inproceedings{ schulte_active_2014,
  address = {New York, NY, USA},
  series = {{ICSE} {Companion} 2014},
  title = {Active {Files} {As} a {Measure} of {Software} {Maintainability}},
  isbn = {978-1-4503-2768-8},
  url = {http://doi.acm.org/10.1145/2591062.2591176},
  doi = {10.1145/2591062.2591176},
  abstract = {In this paper, we explore the set of source files which are changed unusually often. We define these files as active files. Although discovery of active files relies only on version history and defect classification, the simple concept of active files can deliver key insights into software development activities. Active files can help focus code reviews, implement targeted testing, show areas for potential merge conflicts and identify areas that are central for program comprehension.   In an empirical study of six large software systems within Microsoft ranging from products to services, we found that active files constitute only between 2-8% of the total system size, contribute 20-40% of system file changes, and are responsible for 60-90% of all defects. Not only this, but we establish that the majority, 65-95%, of the active files are architectural hub files which change due to feature addition as opposed to fixing defects.},
  urldate = {2014-07-22TZ},
  booktitle = {Companion {Proceedings} of the 36th {International} {Conference} on {Software} {Engineering}},
  publisher = {ACM},
  author = {Schulte, Lukas and Sajnani, Hitesh and Czerwonka, Jacek},
  year = {2014},
  keywords = {Maintainability, Software metrics, _done, _naming_fault_as_defect_model, active file, risk, source file change, technical debt},
  pages = {34--43}
}

{"_id":"7bAoSWc4izDKZakZ3","bibbaseid":"schulte-sajnani-czerwonka-activefilesasameasureofsoftwaremaintainability-2014","downloads":0,"creationDate":"2015-04-15T11:01:18.871Z","title":"Active Files As a Measure of Software Maintainability","author_short":["Schulte, L.","Sajnani, H.","Czerwonka, J."],"year":2014,"bibtype":"inproceedings","biburl":"http://bibbase.org/zotero/troeger","bibdata":{"abstract":"In this paper, we explore the set of source files which are changed unusually often. We define these files as active files. Although discovery of active files relies only on version history and defect classification, the simple concept of active files can deliver key insights into software development activities. Active files can help focus code reviews, implement targeted testing, show areas for potential merge conflicts and identify areas that are central for program comprehension. In an empirical study of six large software systems within Microsoft ranging from products to services, we found that active files constitute only between 2-8% of the total system size, contribute 20-40% of system file changes, and are responsible for 60-90% of all defects. Not only this, but we establish that the majority, 65-95%, of the active files are architectural hub files which change due to feature addition as opposed to fixing defects.","address":"New York, NY, USA","author":["Schulte, Lukas","Sajnani, Hitesh","Czerwonka, Jacek"],"author_short":["Schulte, L.","Sajnani, H.","Czerwonka, J."],"bibtex":"@inproceedings{ schulte_active_2014,\n address = {New York, NY, USA},\n series = {{ICSE} {Companion} 2014},\n title = {Active {Files} {As} a {Measure} of {Software} {Maintainability}},\n isbn = {978-1-4503-2768-8},\n url = {http://doi.acm.org/10.1145/2591062.2591176},\n doi = {10.1145/2591062.2591176},\n abstract = {In this paper, we explore the set of source files which are changed unusually often. We define these files as active files. Although discovery of active files relies only on version history and defect classification, the simple concept of active files can deliver key insights into software development activities. Active files can help focus code reviews, implement targeted testing, show areas for potential merge conflicts and identify areas that are central for program comprehension. In an empirical study of six large software systems within Microsoft ranging from products to services, we found that active files constitute only between 2-8% of the total system size, contribute 20-40% of system file changes, and are responsible for 60-90% of all defects. Not only this, but we establish that the majority, 65-95%, of the active files are architectural hub files which change due to feature addition as opposed to fixing defects.},\n urldate = {2014-07-22TZ},\n booktitle = {Companion {Proceedings} of the 36th {International} {Conference} on {Software} {Engineering}},\n publisher = {ACM},\n author = {Schulte, Lukas and Sajnani, Hitesh and Czerwonka, Jacek},\n year = {2014},\n keywords = {Maintainability, Software metrics, _done, _naming_fault_as_defect_model, active file, risk, source file change, technical debt},\n pages = {34--43}\n}","bibtype":"inproceedings","booktitle":"Companion Proceedings of the 36th International Conference on Software Engineering","doi":"10.1145/2591062.2591176","id":"schulte_active_2014","isbn":"978-1-4503-2768-8","key":"schulte_active_2014","keywords":"Maintainability, Software metrics, _done, _naming_fault_as_defect_model, active file, risk, source file change, technical debt","pages":"34--43","publisher":"ACM","series":"ICSE Companion 2014","title":"Active Files As a Measure of Software Maintainability","type":"inproceedings","url":"http://doi.acm.org/10.1145/2591062.2591176","urldate":"2014-07-22TZ","year":"2014","bibbaseid":"schulte-sajnani-czerwonka-activefilesasameasureofsoftwaremaintainability-2014","role":"author","urls":{"Paper":"http://doi.acm.org/10.1145/2591062.2591176"},"keyword":["Maintainability","Software metrics","_done","_naming_fault_as_defect_model","active file","risk","source file change","technical debt"],"downloads":0},"search_terms":["active","files","measure","software","maintainability","schulte","sajnani","czerwonka"],"keywords":["maintainability","software metrics","_done","_naming_fault_as_defect_model","active file","risk","source file change","technical debt"],"authorIDs":[],"dataSources":["zHc5HdgBCDgkarEqH"]}