11th IEEE International Software Metrics Symposium (METRICS'05)最新文献

筛选
英文 中文
Measurement-driven dashboards enable leading indicators for requirements and design of large-scale systems 测量驱动的仪表板为大型系统的需求和设计提供了领先的指标
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.31
R. Selby
{"title":"Measurement-driven dashboards enable leading indicators for requirements and design of large-scale systems","authors":"R. Selby","doi":"10.1109/METRICS.2005.31","DOIUrl":"https://doi.org/10.1109/METRICS.2005.31","url":null,"abstract":"Measurement-driven dashboards provide a unifying mechanism for understanding, evaluating, and predicting the development, management, and economics of large-scale systems and processes. Dashboards enable interactive graphical displays of complex information and support flexible analytic capabilities for user customizability and extensibility. Dashboards commonly include software requirements and design metrics because they provide leading indicators for project size, growth, and stability. This paper focuses on dashboards that have been used on actual large-scale projects as well as example empirical relationships revealed by the dashboards. The empirical results focus on leading indicators for requirements and design of large-scale systems. In the first set of 14 projects focusing on requirements metrics, the ratio of software requirements to source-lines-of code averaged 1:46. Projects that far exceeded the 1:46 requirements-to-code ratio tended to be more effort-intensive and fault-prone during verification. In the second set of 16 projects focusing on design metrics, the components in the top quartile of the number of component internal states had 6.2 times more faults on average than did the components in the bottom quartile, after normalization by size. The components in the top quartile of the number of component interactions had 4.3 times more faults on average than did the components in the bottom quartile, after normalization by size. When the number of component internal states was in the bottom quartile, the component fault-proneness was low even when the number of component interactions was in the upper quartiles, regardless of size normalization. Measurement-driven dashboards reveal insights that increase visibility into large-scale systems and provide feedback to organizations and projects","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132743796","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}
引用次数: 14
What should you optimize when building an estimation model? 在构建评估模型时应该优化什么?
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.55
C. Lokan
{"title":"What should you optimize when building an estimation model?","authors":"C. Lokan","doi":"10.1109/METRICS.2005.55","DOIUrl":"https://doi.org/10.1109/METRICS.2005.55","url":null,"abstract":"When estimation models are derived from existing data, they are commonly evaluated using statistics such as mean magnitude of relative error. But when the models are derived in the first place, it is usually by optimizing something else - typically, as in statistical regression, by minimizing the sum of squared deviations. How do estimation models for typical software engineering data fare, on various common accuracy statistics, if they are derived using other \"fitness functions\"? In this study, estimation models are built using a variety of fitness functions, and evaluated using a wide range of accuracy statistics. We find that models based on minimizing actual errors generally out-perform models based on minimizing relative errors. Given the nature of software engineering data sets, minimizing the sum of absolute deviations seems an effective compromise","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114905133","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}
引用次数: 35
An empirical analysis of software productivity over time 软件生产力随时间变化的实证分析
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.8
Rahul Premraj, M. Shepperd, B. Kitchenham, Pekka Forselius
{"title":"An empirical analysis of software productivity over time","authors":"Rahul Premraj, M. Shepperd, B. Kitchenham, Pekka Forselius","doi":"10.1109/METRICS.2005.8","DOIUrl":"https://doi.org/10.1109/METRICS.2005.8","url":null,"abstract":"The paper aims to investigate how software project productivity has changed over time. Within this overall goal we also compare productivity between different business sectors and seek to identify major drivers. We analysed a data set of more than 600 projects that have been collected from a number of Finnish companies since 1978. Overall, we observed a quite pronounced improvement in productivity over the entire time period, though, this improvement is less marked since the 1990s. However, the trend is not smooth. We also observed productivity variability between company and business sector. Whilst this data set is not a random sample so generalisation is somewhat problematic, we hope that it contributes to an overall body of knowledge about software productivity and thereby facilitates the construction of a bigger picture","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128735845","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}
引用次数: 87
Can We Teach Empirical Software Engineering? 我们能教实证软件工程吗?
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.16
M. L. Jaccheri, Thomas Østerlie
{"title":"Can We Teach Empirical Software Engineering?","authors":"M. L. Jaccheri, Thomas Østerlie","doi":"10.1109/METRICS.2005.16","DOIUrl":"https://doi.org/10.1109/METRICS.2005.16","url":null,"abstract":"We report about an empirical software engineering course for PhD students. We introduce its syllabus and two different pedagogical strategies. The first strategy is based on individual learning and presentations. The second relies also on social activities to support learning and knowledge sharing. The syllabus, which has been used for three iterations of the course, is available at our web site together with student essays, evaluation data, and other documentation produced during course runs.","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"197 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115669936","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}
引用次数: 9
Product Metrics for Automatic Identification of "Bad Smell" Design Problems in Java Source-Code 在Java源代码中自动识别“臭味”设计问题的产品度量
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.38
M. Munro
{"title":"Product Metrics for Automatic Identification of \"Bad Smell\" Design Problems in Java Source-Code","authors":"M. Munro","doi":"10.1109/METRICS.2005.38","DOIUrl":"https://doi.org/10.1109/METRICS.2005.38","url":null,"abstract":"Refactoring can have a direct influence on reducing the cost of software maintenance through changing the internal structure of the source-code to improve the overall design that helps the present and future programmers evolve and understand a system. Bad smells are a set of design problems with refactoring identified as a solution. Locating these bad smells has been described as more a human intuition than an exact science. This paper addresses the issue of identifying the characteristics of a bad smell through the use of a set of software metrics. Then by using a pre-defined set of interpretation rules to interpret the software metric results applied to Java source-code, the software engineer can be provided with significant guidance as to the location of bad smells. These issues are addressed in a number of ways. Firstly, a precise definition of bad smells is given from the informal descriptions given by the originators Fowler and Beck. The characteristics of the bad smells have been used to define a set of measurements and interpretation rules for a subset of the bad smells. A prototype tool has been implemented to enable the evaluation of the interpretation rules in two case studies.","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123230010","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}
引用次数: 237
An empirical assessment of function point-like object-oriented metrics 功能点类面向对象度量的经验评估
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.9
V. D. Bianco, L. Lavazza
{"title":"An empirical assessment of function point-like object-oriented metrics","authors":"V. D. Bianco, L. Lavazza","doi":"10.1109/METRICS.2005.9","DOIUrl":"https://doi.org/10.1109/METRICS.2005.9","url":null,"abstract":"Since object-oriented programming became a popular development practice, researchers and practitioners have defined several techniques aimed at measuring object-oriented software. Among these, several function point-like approaches have been proposed. However, mapping the concepts at the basis of function point analysis onto object-oriented concepts is not straightforward; therefore, there is the need to test the validity of FP-based object-oriented metrics. This paper presents an analysis of a set of programs developed by masteral students of a software engineering course employing object-oriented techniques (UML and Java). Different kinds of FP-based object-oriented metrics were applied, and the results analysed. The work done addresses questions like the following: is there a correlation between object-oriented FPs and LOCs? How do object-oriented FPs compare with the function points defined by Albrecht? How do object-oriented FPs compare with non FP-like OO metrics? How do object-oriented FPs compare with each other?","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121131712","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
The clients' impact on effort estimation accuracy in software development projects 客户对软件开发项目中工作量估算准确性的影响
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.47
Stein Grimstad, M. Jørgensen, Kjetil Moløkken-Østvold
{"title":"The clients' impact on effort estimation accuracy in software development projects","authors":"Stein Grimstad, M. Jørgensen, Kjetil Moløkken-Østvold","doi":"10.1109/METRICS.2005.47","DOIUrl":"https://doi.org/10.1109/METRICS.2005.47","url":null,"abstract":"This paper focuses on the clients' impact on estimation accuracy in software development projects. Client related factors contributing to effort overruns as well as factors preventing overruns are investigated. Based on a literature review and a survey of 300 software professionals we find that: 1) software professionals perceive that clients impact estimation accuracy. Changed and new requirements are perceived as the clients' most frequent contribution to overruns, while overruns are prevented by the availability of competent clients and capable decision makers. 2) Survey results should not be used in estimation accuracy improvement initiatives without further analysis. Surveys typically identify directly observable and project specific causes for overruns, while substantial improvement is only possible when the underlying causes are understood","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126337478","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
Finding predictors of field defects for open source software systems in commonly available data sources: a case study of OpenBSD 在通常可用的数据源中为开源软件系统寻找领域缺陷的预测器:OpenBSD的一个案例研究
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.26
P. Li, J. Herbsleb, M. Shaw
{"title":"Finding predictors of field defects for open source software systems in commonly available data sources: a case study of OpenBSD","authors":"P. Li, J. Herbsleb, M. Shaw","doi":"10.1109/METRICS.2005.26","DOIUrl":"https://doi.org/10.1109/METRICS.2005.26","url":null,"abstract":"Open source software systems are important components of many business software applications. Field defect predictions for open source software systems may allow organizations to make informed decisions regarding open source software components. In this paper, we remotely measure and analyze predictors (metrics available before release) mined from established data sources (the code repository and the request tracking system) as well as a novel source of data (mailing list archives) for nine releases of OpenBSD. First, we attempt to predict field defects by extending a software reliability model fitted to development defects. We find this approach to be infeasible, which motivates examining metrics-based field defect prediction. Then, we evaluate 139 predictors using established statistical methods: Kendall's rank correlation, Pearson's rank correlation, and forward AIC model selection. The metrics we collect include product metrics, development metrics, deployment and usage metrics, and software and hardware configurations metrics. We find the number of messages to the technical discussion mailing list during the development period (a deployment and usage metric captured from mailing list archives) to be the best predictor of field defects. Our work identifies predictors of field defects in commonly available data sources for open source software systems and is a step towards metrics-based field defect prediction for quantitatively-based decision making regarding open source software components","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116934466","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}
引用次数: 55
Refactoring for changeability: a way to go? 为可变性而重构:一种可行的方法?
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.40
B. Geppert, A. Mockus, F. Rößler
{"title":"Refactoring for changeability: a way to go?","authors":"B. Geppert, A. Mockus, F. Rößler","doi":"10.1109/METRICS.2005.40","DOIUrl":"https://doi.org/10.1109/METRICS.2005.40","url":null,"abstract":"Legacy systems are difficult and expensive to maintain due to size, complexity, and age of their code base. Business needs require continuously adding new features and maintaining older releases. This and the ever present worry about feature breakage are often the reason why the sweeping changes for reversing design degradation are considered too costly, risky and difficult to implement. We study a refactoring carried out on a part of a large legacy business communication product where protocol logic in the registration domain was restructured. We pose a number of hypotheses about the strategies and effects of the refactoring effort on aspects of changeability and measure the outcomes. The results of this case study show a significant decrease in customer reported defects and in effort needed to make changes","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124444873","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}
引用次数: 50
On refactoring support based on code clone dependency relation 基于代码克隆依赖关系的重构支持
11th IEEE International Software Metrics Symposium (METRICS'05) Pub Date : 2005-09-19 DOI: 10.1109/METRICS.2005.36
Norihiro Yoshida, Yoshiki Higo, Toshihiro Kamiya, S. Kusumoto, Katsuro Inoue
{"title":"On refactoring support based on code clone dependency relation","authors":"Norihiro Yoshida, Yoshiki Higo, Toshihiro Kamiya, S. Kusumoto, Katsuro Inoue","doi":"10.1109/METRICS.2005.36","DOIUrl":"https://doi.org/10.1109/METRICS.2005.36","url":null,"abstract":"Generally, code clones are regarded as one of the factors that make software maintenance more difficult. A code clone is a set of source code fragments identical or similar to each other from the viewpoint of software maintainability, code clones should be removed. However, sometimes there are dependency relations among each of which belong to the different code clone, and it is advisable to refactor all of such code clones at once. In this paper, we focus on the case that such code fragment corresponds to a method body in Java programs. We defined \"chained method\" as a set of methods that have dependency relations. A set of \"chained methods\" whose elements are each other's code clone is called \"chained clone\", and an equivalence class of \"chained clone\" is called a \"chained clone set\". We propose a refactoring support method for \"chained clone set\" by providing an appropriate refactoring pattern to them. Finally, we present the \"chained clone set\" refactoring support tool that we have developed, together with some case studies to show the usefulness of the proposed method","PeriodicalId":402415,"journal":{"name":"11th IEEE International Software Metrics Symposium (METRICS'05)","volume":"58 9","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-09-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114126876","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}
引用次数: 34
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
相关产品
×
本文献相关产品
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信