MétaCan
Menu
Back to cohort
Record W2902192294 · doi:10.1002/smr.2149

Empirical evaluation of an entropy‐based approach to estimation variation of software development effort

2018· article· en· W2902192294 on OpenAlexaff
Salma El Koutbi, Ali Idri, Alain Abran

Bibliographic record

VenueJournal of Software Evolution and Process · 2018
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsJackknife resamplingGaussianMathematicsEntropy (arrow of time)Entropy estimationComputer scienceAlgorithmVariation (astronomy)StatisticsApplied mathematicsEstimator

Abstract

fetched live from OpenAlex

Abstract As effort estimation has gained increasing attention, most of the techniques proposed have focused on the accuracy of effort estimates. Yet no clear conclusions have been drawn on which techniques perform best in all contexts. We propose an entropy‐based approach to effort estimate variation caused by measurement and model error sources whatever the effort estimation technique used. The proposed approach was empirically evaluated by exploring three entropy formulae, four interpolation methods, and two analogy‐based effort estimation approaches (crisp and fuzzy analogy) over seven datasets using the Jackknife evaluation method. The obtained results show that the three entropy formulae have in general the same positive influence on the performance of the entropy‐based approach measured in terms of absolute error of effort deviation. In addition, the spline interpolation outperformed all other interpolation methods, using any of the entropy formulae. Moreover, achievement percentages of the best variants of our approach closely approximated those of the Gaussian distribution confirming that the Gaussian distribution is useful for characterizing effort estimate variation.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.013
metaresearch head score (Gemma)0.054
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.013
Threshold uncertainty score0.068

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0130.054
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0050.002
Science and technology studies0.0000.001
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0010.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.

Opus teacher head0.041
GPT teacher head0.339
Teacher spread0.298 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Software Evolution and ProcessSame topicSoftware Engineering ResearchFrench-language works237,207