MétaCan
Menu
Back to cohort
Record W1537659679 · doi:10.24297/ijct.v13i5.2535

An Analysis of the PROMISE and ISBSG Software Engineering Data Repositories

2014· article· en· W1537659679 on OpenAlexaff
Laila Cheikhi, Alain Abran

Bibliographic record

VenueINTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY · 2014
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsÉcole de Technologie SupérieureUniversité du Québec à Montréal
Fundersnot available
KeywordsBenchmarkingComputer scienceReusabilitySoftware engineeringData scienceSoftwareSocial software engineeringSoftware developmentSoftware construction

Abstract

fetched live from OpenAlex

There exist two ongoing large repositories of software projects in the software engineering community: the repository of the International Software Benchmarking Standards Group (ISBSG) and the Repository referred to as PROMISE (PRedictOr Models In Software Engineering). Researchers interested in using the datasets have to conduct their own analysis of the datasets within these repositories that figure out what contents are suitable for their purposes. Repositories designed without users (researchers and Industrial) needs in mind greatly are more challenging to use. This paper present an analysis of both repositories and provide users with additional information on these datasets by identifying the topics addressed, highlighting their descriptiveness, and their availability, and by indicating whether or not further details are available in order to enhance their reusability in further empirical studies. Recommendations to both PROMISE managers and datasets owners are also suggested to improve the usefulness of the data provided.

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.043
metaresearch head score (Gemma)0.158
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.043
Threshold uncertainty score0.226

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0430.158
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0200.030
Science and technology studies0.0020.002
Scholarly communication0.0050.011
Open science0.0030.005
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0020.002

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.009
GPT teacher head0.267
Teacher spread0.258 · 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

Citations2
Published2014
Admission routes1
Has abstractyes

Explore more

Same venueINTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGYSame topicSoftware Engineering ResearchFrench-language works237,207