MétaCan
Menu
Back to cohort

9.4.1 Lessons Learned From Industrial Validation of COSYSMO

2007· article· en· W1556570903 on OpenAlexaff
Ricardo Valerdi, Garry Roedler, John Rieff, Marilee J. Wheaton, Wang Gan

Bibliographic record

VenueINCOSE International Symposium · 2007
Typearticle
Languageen
FieldEngineering
TopicSystems Engineering Methodologies and Applications
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsCapability Maturity Model IntegrationProcess (computing)ReuseEngineeringEngineering managementGovernment (linguistics)Domain (mathematical analysis)Software engineeringComputer scienceSystems engineeringSoftware developmentSoftware development processProcess managementSoftware

Abstract

fetched live from OpenAlex

Abstract The development of COSYSMO has been an ongoing collaboration between industry, government, and academia since 2001. INCOSE provided expertise as well as a forum for collaboration between stakeholders that led to the eventual development of the model. In 2004, we provided eleven lessons learned from experiences collecting systems engineering data from six companies in collaboration with the INCOSE Measurement Working Group and the Practical Software and Systems Measurement (PSM). These lessons were focused on the development of COSYSMO that was motivated by a similar model from the software domain, COCOMO II, but was a first of its kind for systems engineering. Now that the development phase of the model is completed we take a retrospective view of lessons learned during the ongoing validation phase of the model and present new lessons learned that should help cost model developers, academic researchers, and practitioners develop and validate similar approaches. These lessons include the need for more specific counting rules, an approach to account for reuse in systems engineering, and strategies for model adoption in organizations.

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.084
metaresearch head score (Gemma)0.203
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: Empirical
Teacher disagreement score0.084
Threshold uncertainty score0.442

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0840.203
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.002
Science and technology studies0.0030.004
Scholarly communication0.0080.015
Open science0.0060.005
Research integrity0.0030.007
Insufficient payload (model declined to judge)0.0040.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.116
GPT teacher head0.328
Teacher spread0.212 · 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

Citations18
Published2007
Admission routes1
Has abstractyes

Explore more

Same venueINCOSE International SymposiumSame topicSystems Engineering Methodologies and ApplicationsFrench-language works237,207