MétaCan
Menu
Back to cohort
Record W2097146349 · doi:10.1109/case.1992.200156

ROOM: an object-oriented methodology for developing real-time systems

2003· article· en· W2097146349 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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsBell (Canada)
Fundersnot available
KeywordsComputer scienceSoftware engineeringObject-oriented programmingProcess (computing)Iterative and incremental developmentSet (abstract data type)Domain (mathematical analysis)Object (grammar)Software developmentSoftwareSystems engineeringProgramming languageArtificial intelligenceEngineering

Abstract

fetched live from OpenAlex

Real-time object-oriented modeling (ROOM), an object-oriented methodology for the development of real-time systems supported by a commercial computer-aided software engineering (CASE) toolset, is presented. This methodology has been driven by industrial experience, and is founded on a set of principles which fulfil the need to produce high-quality software more rapidly and more efficiently than by traditional methods. The principles include the definition and use of powerful domain-specific modeling abstractions, the elimination of error-prone discontinuities during development, and a highly iterative development process based on advanced tool support. An overview of the conceptual framework and the development process model of ROOM is given.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.978
Threshold uncertainty score0.645

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.064
GPT teacher head0.315
Teacher spread0.250 · 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