{"title":"通过使用静态度量来预测代码变更","authors":"Andreas Mauczka, T. Grechenig, Mario Bernhart","doi":"10.1109/SERA.2009.30","DOIUrl":null,"url":null,"abstract":"Maintenance of software is risky, potentially expensive – and inevitable. The main objective of this study is to examine the relationship of code change, referred to as maintenance effort, with source-level software metrics. This approach varies from the typical approach of evaluating software metrics against failure data and provides a different angle on the validation of software metrics. The goal of this study is to show through exhaustive data mining that a relation between software metrics and code change exists. Once this connection is established, a set of software metrics is identified, which will be used in further studies to predict code change in problematic modules identified by the software metrics at an early development stage.","PeriodicalId":333607,"journal":{"name":"2009 Seventh ACIS International Conference on Software Engineering Research, Management and Applications","volume":"172 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2009-12-02","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"Predicting Code Change by Using Static Metrics\",\"authors\":\"Andreas Mauczka, T. Grechenig, Mario Bernhart\",\"doi\":\"10.1109/SERA.2009.30\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Maintenance of software is risky, potentially expensive – and inevitable. The main objective of this study is to examine the relationship of code change, referred to as maintenance effort, with source-level software metrics. This approach varies from the typical approach of evaluating software metrics against failure data and provides a different angle on the validation of software metrics. The goal of this study is to show through exhaustive data mining that a relation between software metrics and code change exists. Once this connection is established, a set of software metrics is identified, which will be used in further studies to predict code change in problematic modules identified by the software metrics at an early development stage.\",\"PeriodicalId\":333607,\"journal\":{\"name\":\"2009 Seventh ACIS International Conference on Software Engineering Research, Management and Applications\",\"volume\":\"172 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2009-12-02\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2009 Seventh ACIS International Conference on Software Engineering Research, Management and Applications\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SERA.2009.30\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2009 Seventh ACIS International Conference on Software Engineering Research, Management and Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SERA.2009.30","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Maintenance of software is risky, potentially expensive – and inevitable. The main objective of this study is to examine the relationship of code change, referred to as maintenance effort, with source-level software metrics. This approach varies from the typical approach of evaluating software metrics against failure data and provides a different angle on the validation of software metrics. The goal of this study is to show through exhaustive data mining that a relation between software metrics and code change exists. Once this connection is established, a set of software metrics is identified, which will be used in further studies to predict code change in problematic modules identified by the software metrics at an early development stage.