MétaCan
Menu
Back to cohort
Record W2040225071 · doi:10.1002/spip.146

Findings from Phase 2 of the SPICE trials

2001· article· en· W2040225071 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 · 2001
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsNational Research Council Canada
Fundersnot available
KeywordsSpiceUsabilityComputer scienceEmpirical researchSoftware engineeringDimension (graph theory)Process (computing)Reliability engineeringSystems engineeringProcess managementEngineeringMathematics

Abstract

fetched live from OpenAlex

Abstract The international SPICE (Software Process Improvement and Capability dEtermination) project was set up to support the development of the ISO/IEC 15504 standard for software process assessment (SPA). The project mounted a set of trials to validate the emerging standard against the goals and requirements defined at the start of the SPICE project and to verify the consistency and usability of its component parts. A considerable number of empirical evaluation studies have been conducted during the Phase 2 SPICE Trials based on ISO/IEC PDTR 15504 (between September 1996 and June 1998). Such an exercise is unprecedented in the software engineering standards community and it provides a unique opportunity for empirical validation. The purpose of this paper is to present major parts of the findings of the empirical studies conducted as part of the SPICE Project during Phase 2 of the SPICE Trials. The topics covered in this paper include (i) investigation into reasons for performing SPAs, (ii) evaluation of the internal consistency of the capability dimension, (iii) use of interrater agreement as a measure of the reliability of assessments, (iv) evaluation of the predictive validity of process capability, (v) evaluation of an exemplar model (Part 5), (vi) identification of factors influencing assessor effort, and (vii) empirical comparison between ISO/IEC PDTR 15504 and ISO 9001. Major lessons learned as well as future research directions are summarized on the strengths and weaknesses of ISO/IEC 15505. Copyright © 2001 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.002
metaresearch head score (Gemma)0.030
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.936
Threshold uncertainty score0.978

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.030
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.059
GPT teacher head0.378
Teacher spread0.319 · 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