MétaCan
Menu
Back to cohort
Record W4252165735 · doi:10.24124/2006/bpgub1329

Distribution of defects in a large software system

2006· dissertation· en· W4252165735 on OpenAlexaboutno aff
Stephen M. Wickham

Bibliographic record

Venuenot available
Typedissertation
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsnot available
Fundersnot available
KeywordsComputer scienceMemory leakSource lines of codeProgrammerLeakSoftwareOperating systemEmbedded systemMemory managementEngineeringSemiconductor memory

Abstract

fetched live from OpenAlex

This report summarizes the findings of a retrospective analysis of coding errors in a major software system produced by a large Canadian software engineering firm. The code-base of the system is approximately 1.7 million lines of C++ integrated with third party RDBMS and GIS products. The safety related nature of the system and the size of its code base make it an ideal candidate for an investigation of software related defects referred to as ' memory leaks.' A ' memory leak' results from the failure to return previously allocated heap memory. The distribution of memory leaks is analyzed and a two-part memory leak classification scheme is described. A secondary focus of the investigation is the influence of decision complexity on system safety. This investigation yielded two statistically significant findings. The first is a relationship between programmer experience and memory leak creation. The second is a correlation between subsystem complexity and memory leak density. The impact of software process improvement measures are also discussed.--Page iii.

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.001
metaresearch head score (Gemma)0.017
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.021
Threshold uncertainty score0.041

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.017
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0070.003
Science and technology studies0.0010.001
Scholarly communication0.0010.001
Open science0.0000.001
Research integrity0.0000.000
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.007
GPT teacher head0.251
Teacher spread0.244 · 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 designObservational
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

Citations0
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207