MétaCan
Menu
Back to cohort
Record W4230500706 · doi:10.1002/spip.374

Optimized mismatch resolution for COTS selection

2008· article· en· W4230500706 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSoftware Process Improvement and Practice · 2008
Typearticle
Languageen
FieldComputer Science
TopicEmbedded Systems Design Techniques
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsProcess (computing)Selection (genetic algorithm)Reliability engineeringSoftwareSystems engineeringComputer scienceResource (disambiguation)Domain (mathematical analysis)Product (mathematics)Risk analysis (engineering)EngineeringSoftware engineeringArtificial intelligenceOperating system

Abstract

fetched live from OpenAlex

Abstract The use of Commercial Off‐The‐Shelf (COTS) products in the software development process requires the evaluation of existing COTS products, and then selecting the one that best fits system requirements. In this process, it is inevitable to encounter mismatches between COTS features and system requirements. Mismatches occur as a result of an excess or shortage of COTS capabilities. Many of these mismatches are resolved after selecting a COTS product. Existing COTS‐selection approaches fail to properly consider these mismatches. This article presents MiHOS (Mismatch Handling for COTS Selection), an approach that aims at addressing mismatches while considering limited resources. MiHOS can be integrated with existing COTS‐selection methods at two points: (i)When evaluating COTS candidates in order to estimate the anticipated fitness of the candidates if their mismatches are resolved. This helps to base our COTS‐selection decisions on the fitness that the COTS candidates will eventually have if selected. (ii) After selecting a COTS product in order to plan the resolution of the most appropriate mismatches using suitable actions, such that the most important risk, technical, and resource constraints are met. A case study from the e‐services domain is used to illustrate the method and to discuss its added value. Copyright © 2008 John Wiley & Sons, Ltd.

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.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.729
Threshold uncertainty score0.668

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.002
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.034
GPT teacher head0.313
Teacher spread0.279 · 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