MétaCan
Menu
Back to cohort
Record W2945596753 · doi:10.1109/icsa-c.2019.00023

Component Comparison, Evaluation, and Selection: A Continuous Approach

2019· article· en· W2945596753 on OpenAlexaff
Neil Ernst, Rick Kazman, Philip Bianco

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Victoria
FundersCarnegie Mellon UniversityU.S. Department of Defense
KeywordsComponent (thermodynamics)Computer scienceBalanced scorecardSelection (genetic algorithm)Context (archaeology)SoftwareAgile software developmentSoftware qualitySoftware engineeringData miningSoftware developmentArtificial intelligenceProcess managementEngineering

Abstract

fetched live from OpenAlex

Early visions of component-based software development have been realized, with software projects now composed mostly of other peoples code. However, the challenge of selecting the best components, with speed and confidence in the result, has only become more difficult. Previous work has focused on systematic approaches to component selection, but in continuous- <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">*</sup> and agile settings, the increase in confidence from being systematic is not worth the cost of delay. In this emerging ideas paper, we present early results on work to balance speed with confidence in component selection. Our idea is to define a scorecard for components based on high-level quality attribute indicators, project health measures, and a context-specific aggregation function for producing a single yes/no decision for integrators. We present preliminary results showing how this scorecard approach works on computer vision components.

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 distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.837
Threshold uncertainty score0.274

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.025
GPT teacher head0.289
Teacher spread0.264 · 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 teacher head, 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

Citations8
Published2019
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering ResearchFrench-language works237,207