MétaCan
Menu
Back to cohort
Record W3163016207 · doi:10.1145/1082983.1082958

Decision support for customization of the COTS selection process

2005· article· en· W3163016207 on OpenAlexaff
Abdallah Mohamed, Guenther Ruhe, Armin Eberlein

Bibliographic record

VenueACM SIGSOFT Software Engineering Notes · 2005
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsPersonalizationExploitComputer scienceProcess (computing)Context (archaeology)Domain (mathematical analysis)Selection (genetic algorithm)Software engineeringSoftwareSystems engineeringRisk analysis (engineering)Process managementEngineeringArtificial intelligenceWorld Wide Web

Abstract

fetched live from OpenAlex

Software technologies need to be customized to make them effective and efficient for a specific context. In this position paper, we consider the customization of the COTS selection process. We have developed a methodology which customizes the selection process based on the actual project domain characteristics (PDCs) including attributes such as available effort or project criticality. The customization of the process is done at both the process level and the activity level. We suggest a hybrid approach that integrates formalized knowledge with human expertise. This principle has already been successfully used in the context of the software release planning. The advantage is two-fold: Firstly, we exploit the existing empirical results related to different stages of the COTS selection process. Secondly, we facilitate involvement of human judgment to determine most appropriate decisions among the ones proposed by the formalized and knowledge-based solution techniques.

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.012
metaresearch head score (Gemma)0.035
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: Empirical · Consensus signal: none
Teacher disagreement score0.012
Threshold uncertainty score0.061

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0120.035
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.001
Science and technology studies0.0010.001
Scholarly communication0.0040.003
Open science0.0020.002
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0060.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.022
GPT teacher head0.290
Teacher spread0.268 · 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
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

Citations1
Published2005
Admission routes1
Has abstractyes

Explore more

Same venueACM SIGSOFT Software Engineering NotesSame topicAdvanced Software Engineering MethodologiesFrench-language works237,207