A study of differences by industry using factor models influencing software development estimates
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Recently, IoT and AI/machine learning have attracted attention, and software development has been a critical activity for the companies that use IT. The investment in IT has been increasing, and it varies with the industry. In addition, software development has become complex with the growing sophistication in the target applications; therefore, it is a challenging task for the software vendors to prepare an accurate estimate. Consequently, the estimates grossly deviate from the true value. In this paper, we propose a method based on the previous research that uses the factors related to productivity of software development to find factors that affect the estimation of man-hours. We analyzed the parameters among populations using two factors and simultaneous analysis of multiple populations from nine industries. We used two-factor models extracted from “the study of software estimation factors extracted using covariance structure analysis” and verified the method by applying five constraints, including factor load amount and error variance, simultaneously for the nine industries. As a result, it was possible to separate industries with large factor variance and those with small factor variance. Moreover, it was possible to separate industries with large correlation coefficient between factors and industries with small factor correlation coefficient. For industries with small variance of factors, the factors are consistent within the industry, and in industries with large correlation between factors; the relationship between the two factors is more relevant. In other words, we could find out the relationship of factors influencing software estimation for each industry type. In addition, the variance of these two factors and the correlation coefficient between the factors were grouped, and a cluster analysis was performed. It was found that there was a difference in the estimate for each group of Business-to-Business and Business-to-Customer industry groups. Based on these results, while preparing software estimates, IT vendors would capture the characteristics of the factors for each type of industry and clarify the influential factors of fluctuation by being conscious of the productivity fluctuation factors related to the two factors.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it