1 January 2002 in New Review of Hypermedia and Multimedia
Research into Web cost estimation is relatively new, where few studies have compared cost estimation modelling techniques for Web development, with an emphasis placed on techniques such as Case-based Reasoning (CBR), linear and stepwise regression. Although in a large subset of these studies CBR has given the best predictions, results were based on a simple type of CBR, where no adaptation rules were used to adjust the estimated effort obtained. In addition, when comparing the prediction accuracy of estimation models, analysis has been limited to a maximum of three training/validation sets, which according to recent studies, may lead to untrustworthy results. Since CBR is potentially easier to understand and apply (two important factors to the successful adoption of estimation methods within Web development companies), it should be examined further. This paper has therefore two objectives: i) to further investigate the use of CBR for Web development effort prediction by comparing effort prediction accuracy of several CBR techniques; ii) to compare the effort prediction accuracy of the best CBR technique against stepwise and multiple linear regression, using twenty combinations of training/validation sets. Various measures of effort prediction accuracy were applied. One dataset was used in the estimation process. Stepwise and multiple linear regression showed the best prediction accuracy for the dataset employed.
13 July 2016 in PeerJ Preprints
Building an effective team of developers is a complex task faced by both software companies and open source communities. The problem of forming a “dream” team involves many variables, including consideration of human factors, and it is not a dilemma solvable in a mathematical way. Empirical studies might provide interesting insights to explain which factors need to be taken into account in building a team of developers and which levers act to optimise collaboration and productivity among developers. In this paper, we present the results of an empirical study aimed at investigating the link between team diver- sity (i.e., gender, nationality) and productivity (issue fixing time). We consider issues solved from the GHTorrent dataset inferring gender and nationality of each team’s members. We also evaluate the politeness of all comments involved in issue resolution. Results show that higher gender diversity is linked with a lower team average issue fixing time and that nationality diversity is linked with lower team politeness.
13 July 2016 in PeerJ Preprints
Building an effective team of developers is a complex task faced by both software companies and open source communities. The problem of forming a “dream” team involves many variables, including consideration of human factors, and it is not a dilemma solvable in a mathematical way. Empirical studies might provide interesting insights to explain which factors need to be taken into account in building a team of developers and which levers act to optimise collaboration and productivity among developers. In this paper, we present the results of an empirical study aimed at investigating the link between team diver- sity (i.e., gender, nationality) and productivity (issue fixing time). We consider issues solved from the GHTorrent dataset inferring gender and nationality of each team’s members. We also evaluate the politeness of all comments involved in issue resolution. Results show that higher gender diversity is linked with a lower team average issue fixing time and that nationality diversity is linked with lower team politeness.