MétaCan
Menu
Back to cohort
Record W2130808901 · doi:10.1109/ccece.2006.277301

Repositories for Cots Selection

2006· article· en· W2130808901 on OpenAlexaff
Tom Wanyama, Behrouz H. Far

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsProcess (computing)Computer scienceCommercial off-the-shelfSelection (genetic algorithm)SoftwareDatabaseSoftware engineeringSystems engineeringEngineeringOperating system

Abstract

fetched live from OpenAlex

Selecting commercial-off-the-shelf (COTS) products is a challenging process that utilizes and generates a lot of information. Repositories play a crucial role in the management of the COTS selection information. In fact, it is generally believed in literature that repositories are of great importance to the COTS selection process and indeed to the entire process of developing software using COTS products. However, the process of developing, managing, and accessing these repositories has attracted very little attention. This paper presents a framework for establishing and maintaining the following five different repositories for the COTS selection process: COTS repository, user repository, discussions repository, lessons-learned repository, and historical information repository. The framework supports distributed contribution and access to the repositories, as well as systematic and hierarchical evaluation and integration of the contributions. Moreover, this paper presents a description of a database that was implemented as part of a decision support system (DSS) for the selection of COTS products. The database accommodates the different repositories for the COTS selection process

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.017
metaresearch head score (Gemma)0.043
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.017
Threshold uncertainty score0.090

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0170.043
Meta-epidemiology (narrow)0.0010.002
Meta-epidemiology (broad)0.0020.002
Bibliometrics0.0110.013
Science and technology studies0.0030.001
Scholarly communication0.0130.015
Open science0.0060.008
Research integrity0.0030.003
Insufficient payload (model declined to judge)0.0080.004

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.019
GPT teacher head0.275
Teacher spread0.255 · 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 designNot applicable
Domainnot available
GenreOther

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

Citations10
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207