Pub Date : 2004-09-11DOI: 10.1109/METRIC.2004.1357902
A. Rainer, T. Hall
We present data on the progress of two projects at IBM Hursley Park. Each project lasted approximately 12 months in duration. We use the data to identify the areas in the projects where poor progress was occurring and to investigate the causes of this poor progress. We find some similarities between the two projects in terms of where some poor progress is occurring i.e. with the design, code and test processes. But we also identify differences between the two projects that can be partially explained by the dependency of these two projects on other parts of IBM. We also find that limited quantitative data is reported in the projects, and that there is little explicit comparison of actual progress with planned progress. Indeed, the reporting of progress seems to be affected by factors like the 'deadline effect' and preferences for reporting certain types of progress. We conclude that these factors may threaten the valid reporting and management of the projects.
{"title":"Identifying the causes of poor progress in software projects","authors":"A. Rainer, T. Hall","doi":"10.1109/METRIC.2004.1357902","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357902","url":null,"abstract":"We present data on the progress of two projects at IBM Hursley Park. Each project lasted approximately 12 months in duration. We use the data to identify the areas in the projects where poor progress was occurring and to investigate the causes of this poor progress. We find some similarities between the two projects in terms of where some poor progress is occurring i.e. with the design, code and test processes. But we also identify differences between the two projects that can be partially explained by the dependency of these two projects on other parts of IBM. We also find that limited quantitative data is reported in the projects, and that there is little explicit comparison of actual progress with planned progress. Indeed, the reporting of progress seems to be affected by factors like the 'deadline effect' and preferences for reporting certain types of progress. We conclude that these factors may threaten the valid reporting and management of the projects.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123138610","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357899
Matthias M. Müller, F. Padberg
Why are programmer pairs more productive than single developers? Using empirical data from two controlled experiments, we find that pair performance is uncorrelated with programming experience, but shows a significant correlation with how comfortably the developers feel with pair programming during the session (the 'feelgood" factor).
{"title":"An empirical study about the feelgood factor in pair programming","authors":"Matthias M. Müller, F. Padberg","doi":"10.1109/METRIC.2004.1357899","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357899","url":null,"abstract":"Why are programmer pairs more productive than single developers? Using empirical data from two controlled experiments, we find that pair performance is uncorrelated with programming experience, but shows a significant correlation with how comfortably the developers feel with pair programming during the session (the 'feelgood\" factor).","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121045660","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357906
J. Hietala, J. Kontio, J. Jokinen, Jarkko Pyysiäinen
We report findings from a survey that has been conducted in Finland to study how the software product companies have matured and evolved over the years. In addition to introducing some key terms for characterizing the software product business, we provide some overall data on the sector, and discuss some specific issues related to the software R&D process and subcontracting. The survey is one of the largest such surveys covering the software product companies and has revealed several interesting findings on software product companies. Most notably, the software companies have shown to be dynamic and resilient in challenging business environment; and their biggest challenges in growth are not technical but management and marketing related. Furthermore, we also discovered that the most important improvement areas are improving the degree of productization and level of competence of personnel and that the ability to network with other companies is critical for younger companies. This survey also revealed that programming and planning are the two most common types of subcontracting, and difficulties in modularity and specifications are the biggest hurdles that prevent wider use of subcontracting.
{"title":"Challenges of software product companies: results of a national survey in Finland","authors":"J. Hietala, J. Kontio, J. Jokinen, Jarkko Pyysiäinen","doi":"10.1109/METRIC.2004.1357906","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357906","url":null,"abstract":"We report findings from a survey that has been conducted in Finland to study how the software product companies have matured and evolved over the years. In addition to introducing some key terms for characterizing the software product business, we provide some overall data on the sector, and discuss some specific issues related to the software R&D process and subcontracting. The survey is one of the largest such surveys covering the software product companies and has revealed several interesting findings on software product companies. Most notably, the software companies have shown to be dynamic and resilient in challenging business environment; and their biggest challenges in growth are not technical but management and marketing related. Furthermore, we also discovered that the most important improvement areas are improving the degree of productization and level of competence of personnel and that the ability to network with other companies is critical for younger companies. This survey also revealed that programming and planning are the two most common types of subcontracting, and difficulties in modularity and specifications are the biggest hurdles that prevent wider use of subcontracting.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"79 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126247894","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}
Measuring similarity between trees, such as XML structured information, has an important role in many applications, and in particular in the evaluation of the effectiveness of information extraction systems (IES). In this paper we present an experience in evaluating the effectiveness of IES in terms of extraction and adaptation effectiveness. In the first part of the paper a similarity measure between XML trees based on a common subtree detection algorithm is introduced; then, a case study aimed at the evaluation of the effectiveness of a group of IES is presented as an example of application.
{"title":"Measuring XML document similarity: a case study for evaluating information extraction systems","authors":"G. Canfora, L. Cerulo, R. Scognamiglio","doi":"10.1109/METRICS.2004.29","DOIUrl":"https://doi.org/10.1109/METRICS.2004.29","url":null,"abstract":"Measuring similarity between trees, such as XML structured information, has an important role in many applications, and in particular in the evaluation of the effectiveness of information extraction systems (IES). In this paper we present an experience in evaluating the effectiveness of IES in terms of extraction and adaptation effectiveness. In the first part of the paper a similarity measure between XML trees based on a common subtree detection algorithm is introduced; then, a case study aimed at the evaluation of the effectiveness of a group of IES is presented as an example of application.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121785630","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357909
F. Lanubile, Teresa Mallardo, Fabio Calefato, C. Denger, M. Ciolkowski
Scenario-based reading (SBR) techniques have been proposed as an alternative to checklists to support the inspectors throughout the reading process in the form of operational scenarios. Many studies have been performed to compare these techniques regarding their impact on the inspector performance. However, most of the existing studies have compared generic checklists to a set of specific reading scenarios, thus confounding the effects of two SBR key factors: separation of concerns and active guidance. In a previous work we have preliminarily conducted a repeated case study at the University of Kaiserslautern to evaluate the impact of active guidance on inspection performance. Specifically, we compared reading scenarios and focused checklists, which were both characterized as being perspective-based. The only difference between the reading techniques was the active guidance provided by the reading scenarios. We now have replicated the initial study with a controlled experiment using as subjects 43 graduate students in computer science at University of Bari. We did not find evidence that active guidance in reading techniques affects the effectiveness or the efficiency of defect detection. However, inspectors showed a better acceptance of focused checklists than reading scenarios.
{"title":"Assessing the impact of active guidance for defect detection: a replicated experiment","authors":"F. Lanubile, Teresa Mallardo, Fabio Calefato, C. Denger, M. Ciolkowski","doi":"10.1109/METRIC.2004.1357909","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357909","url":null,"abstract":"Scenario-based reading (SBR) techniques have been proposed as an alternative to checklists to support the inspectors throughout the reading process in the form of operational scenarios. Many studies have been performed to compare these techniques regarding their impact on the inspector performance. However, most of the existing studies have compared generic checklists to a set of specific reading scenarios, thus confounding the effects of two SBR key factors: separation of concerns and active guidance. In a previous work we have preliminarily conducted a repeated case study at the University of Kaiserslautern to evaluate the impact of active guidance on inspection performance. Specifically, we compared reading scenarios and focused checklists, which were both characterized as being perspective-based. The only difference between the reading techniques was the active guidance provided by the reading scenarios. We now have replicated the initial study with a controlled experiment using as subjects 43 graduate students in computer science at University of Bari. We did not find evidence that active guidance in reading techniques affects the effectiveness or the efficiency of defect detection. However, inspectors showed a better acceptance of focused checklists than reading scenarios.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132987853","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}
This paper extends a previous study, using data on 67 Web projects from the Tukutuku database, investigating to what extent a cross-company cost model can be successfully employed to estimate effort for projects that belong to a single company, where no projects from this company were used to build the cross-company model. Our within-company model employed data on 14 Web projects from a single Web company. Our results were similar to those from the previous study, showing that predictions based on the within-company model were significantly more accurate than those based on the cross-company model. We also found that predictions were very poor when the within-company cost model was used to estimate effort for 53 Web projects from different companies. We analysed the data using two techniques, forward stepwise regression and case-based reasoning. We found estimates produced using stepwise regression models were better for the within company model while case-based reasoning predictions were better for the cross-company model.
{"title":"Further comparison of cross-company and within-company effort estimation models for Web applications","authors":"E. Mendes, B. Kitchenham","doi":"10.1109/METRICS.2004.24","DOIUrl":"https://doi.org/10.1109/METRICS.2004.24","url":null,"abstract":"This paper extends a previous study, using data on 67 Web projects from the Tukutuku database, investigating to what extent a cross-company cost model can be successfully employed to estimate effort for projects that belong to a single company, where no projects from this company were used to build the cross-company model. Our within-company model employed data on 14 Web projects from a single Web company. Our results were similar to those from the previous study, showing that predictions based on the within-company model were significantly more accurate than those based on the cross-company model. We also found that predictions were very poor when the within-company cost model was used to estimate effort for 53 Web projects from different companies. We analysed the data using two techniques, forward stepwise regression and case-based reasoning. We found estimates produced using stepwise regression models were better for the within company model while case-based reasoning predictions were better for the cross-company model.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"57 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128876485","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357912
G. Cantone, D. Pace, G. Calavaro
We consider convertibility of the elements of the unified modeling language into entities of the function point analysis, introduces a model for establishing the link, and presents a pilot study for comparing the function point counts provided by the model with those provided by a function point certified expert. In order to map the unified modeling language elements to function point analysis entities, the paper develops guidelines, rules, heuristics, and flexibility specifications, which also constitute the requirements of an analyzer and semiautomatic converter, implemented as a wizard inside IBM-Rational Rose. The paper presents and discusses the design, conduction and results of the pilot study.
{"title":"Applying function point to unified modeling language: conversion model and pilot study","authors":"G. Cantone, D. Pace, G. Calavaro","doi":"10.1109/METRIC.2004.1357912","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357912","url":null,"abstract":"We consider convertibility of the elements of the unified modeling language into entities of the function point analysis, introduces a model for establishing the link, and presents a pilot study for comparing the function point counts provided by the model with those provided by a function point certified expert. In order to map the unified modeling language elements to function point analysis entities, the paper develops guidelines, rules, heuristics, and flexibility specifications, which also constitute the requirements of an analyzer and semiautomatic converter, implemented as a wizard inside IBM-Rational Rose. The paper presents and discusses the design, conduction and results of the pilot study.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"118 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116901007","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357925
A. Geras, Michael R. Smith, James Miller
Test driven development (TDD) is a relatively new software development process. On the strength of anecdotal evidence and a number of empirical evaluations, TDD is starting to gain momentum as the primary means of developing software in organizations worldwide. In traditional development, tests are for verification and validation purposes and are built after the target product feature exists. In test-driven development, tests are used for specification purposes in addition to verification and validation. An experiment was devised to investigate the distinction between test-driven development and traditional, test-last development from the perspective of developer productivity and software quality. The results of the experiment indicate that while there is little or no difference in developer productivity in the two processes, there are differences in the frequency of unplanned test failures. This may lead to less debugging and more time spent on forward progress within a development project. As with many new software development technologies however, this requires further study, in particular to determine if the positive results translate into lower total costs of ownership.
{"title":"A prototype empirical evaluation of test driven development","authors":"A. Geras, Michael R. Smith, James Miller","doi":"10.1109/METRIC.2004.1357925","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357925","url":null,"abstract":"Test driven development (TDD) is a relatively new software development process. On the strength of anecdotal evidence and a number of empirical evaluations, TDD is starting to gain momentum as the primary means of developing software in organizations worldwide. In traditional development, tests are for verification and validation purposes and are built after the target product feature exists. In test-driven development, tests are used for specification purposes in addition to verification and validation. An experiment was devised to investigate the distinction between test-driven development and traditional, test-last development from the perspective of developer productivity and software quality. The results of the experiment indicate that while there is little or no difference in developer productivity in the two processes, there are differences in the frequency of unplanned test failures. This may lead to less debugging and more time spent on forward progress within a development project. As with many new software development technologies however, this requires further study, in particular to determine if the positive results translate into lower total costs of ownership.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130616142","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357903
J. Kontio, J. Jokinen, E. Rosendahl
An essential element of software engineering risk management is the conceptualization of potential risks to a project. It is the basis of risk analysis and, even more importantly, it strongly influences how risks are communicated and understood by participants in a project. We report the results of a study where different risk visualization and documentation methods were compared in a controlled experiment with students. The study indicated that a defined and sufficiently expressive visualization approach can help capture more of the risk information than less formal methods. At the same time, participants felt that the more formal approaches were not more difficult to either learn or use than less formal ones. The SEI risks statements turned out to be inferior to other methods in most comparisons.
{"title":"Visualizing and formalizing risk information: an experiment","authors":"J. Kontio, J. Jokinen, E. Rosendahl","doi":"10.1109/METRIC.2004.1357903","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357903","url":null,"abstract":"An essential element of software engineering risk management is the conceptualization of potential risks to a project. It is the basis of risk analysis and, even more importantly, it strongly influences how risks are communicated and understood by participants in a project. We report the results of a study where different risk visualization and documentation methods were compared in a controlled experiment with students. The study indicated that a defined and sufficiently expressive visualization approach can help capture more of the risk information than less formal methods. At the same time, participants felt that the more formal approaches were not more difficult to either learn or use than less formal ones. The SEI risks statements turned out to be inferior to other methods in most comparisons.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"38 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132071778","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 : 2004-09-11DOI: 10.1109/METRIC.2004.1357890
S. Morasca
It is not uncommon in software engineering measurement to deal with attributes measured with nominal or ordinal scales. Also, it has long been debated whether it is possible to find ordinal scales for the structural complexity of software code. We address two problems: (1) the definition of concentration and dispersion indices for nominal scales; (2) the conditions under which the comparisons of arithmetic means or geometric means are meaningful for scales that are ordinal or not even ordinal.
{"title":"On the definition and use of aggregate indices for nominal, ordinal, and other scales","authors":"S. Morasca","doi":"10.1109/METRIC.2004.1357890","DOIUrl":"https://doi.org/10.1109/METRIC.2004.1357890","url":null,"abstract":"It is not uncommon in software engineering measurement to deal with attributes measured with nominal or ordinal scales. Also, it has long been debated whether it is possible to find ordinal scales for the structural complexity of software code. We address two problems: (1) the definition of concentration and dispersion indices for nominal scales; (2) the conditions under which the comparisons of arithmetic means or geometric means are meaningful for scales that are ordinal or not even ordinal.","PeriodicalId":261807,"journal":{"name":"10th International Symposium on Software Metrics, 2004. Proceedings.","volume":"39 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2004-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122794294","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
扫码关注我们
求助内容：
应助结果提醒方式：