MétaCan
Menu
Back to cohort
Record W2164658662

Context-Sensitive Ranking of Dependencies for Software Navigation

2009· article· en· W2164658662 on OpenAlexaff
Martin P. Robillard, Tristan Ratchford

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsMcGill University
Fundersnot available
KeywordsRanking (information retrieval)Computer scienceDependency graphDependency (UML)Task (project management)Information retrievalGraphData miningContext (archaeology)SoftwareTheoretical computer scienceArtificial intelligenceEngineeringProgramming language
DOInot available

Abstract

fetched live from OpenAlex

Software navigation during change tasks requires developers to perform numerous search cycles to discover new elements related to their task. In a typical search cycle a developer selects an element of interest, triggers a search for its dependencies, inspects the list of results, and selects a result that appears to be relevant. We are interested in improving the efficiency of developers engaged in program navigation by automatically searching for all dependencies to or from elements already discovered, and continually providing the list of dependencies, ranked in decreasing order of likelihood to be related to the task. In this paper, we present a framework for the systematic evaluation of ranking algorithms based on multi-element contexts, and report on a preliminary experiment to assess the value of three ranking strategies for dependencies: using the topology of the dependency graph, textual similarity, or combination of both. Our results show that all three strategies significantly improve the probability of recommending relevant elements in many situations, but that no ranking strategy appears to be universally optimal.

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.005
metaresearch head score (Gemma)0.044
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.007
Threshold uncertainty score0.028

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.044
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0060.003
Science and technology studies0.0010.001
Scholarly communication0.0020.004
Open science0.0020.001
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0020.001

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.020
GPT teacher head0.276
Teacher spread0.256 · 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 designTheoretical or conceptual
Domainnot available
GenreMethods

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

Citations2
Published2009
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207