MétaCan
Menu
Back to cohort
Record W2112902067 · doi:10.1109/sess.1995.525963

Trillium: a model for the assessment of telecom software system development and maintenance capability

2002· article· en· W2112902067 on OpenAlexaffabout
Alain April, François Coallier

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsBell (Canada)
Fundersnot available
KeywordsBenchmarkingBenchmark (surveying)Computer scienceProcess (computing)Software developmentCapability Maturity ModelSoftware engineeringSoftwareSoftware development processEngineering managementSoftware qualityQuality (philosophy)Best practiceSystems engineeringProcess managementEngineeringBusinessOperating system

Abstract

fetched live from OpenAlex

Since 1982 Bell Canada has been developing a model to assess the software development process of existing and prospective suppliers as a means to minimize the risks involved and ensure both the performance and timely delivery of software systems purchased. This paper presents the revised Trillium model (version 3.0). The basis of the process assessment models for software relies on benchmarking, e.g. comparing your practices with the best and successful organizations. It is also a basic tool that you will find in the TQM literature. For software assessment we have used initially two levels of benchmarks to develop the model: professional, national and international standards; and comparisons with other organizations in the same market segment. The software assessment model should therefore map to existing engineering standards as well as quality standards. It should also provide an output that can be used easily to benchmark against "best-in-class" 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.004
metaresearch head score (Gemma)0.014
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.024
Threshold uncertainty score0.047

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.014
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0060.004
Science and technology studies0.0010.002
Scholarly communication0.0050.007
Open science0.0040.002
Research integrity0.0030.002
Insufficient payload (model declined to judge)0.0110.006

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.037
GPT teacher head0.266
Teacher spread0.229 · 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 designSimulation or modeling
Domainnot available
GenreMethods

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

Citations12
Published2002
Admission routes2
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207