MétaCan
Menu
Back to cohort
Record W2000107973 · doi:10.1145/2601248.2613084

On collecting and validating UML consistency rules

2014· article· en· W2000107973 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsCarleton University
FundersNatural Sciences and Engineering Research Council of CanadaMinisterio de Economía y Competitividad
KeywordsComputer scienceUnified Modeling LanguageConsistency (knowledge bases)Programming languageApplications of UMLUML toolSoftware engineeringArtificial intelligenceSoftware

Abstract

fetched live from OpenAlex

The main aim of my doctoral research is to create a comprehensive set of well-accepted consistency rules for UML diagrams that can be found in the literature, in reference textbooks or in the UML standard. Moreover, an important part of that aim will be the validation of the gathered UML consistency rules. This research will provide to the academic community and industrial organizations an extensive and detailed new base of knowledge about UML consistency rules which is a paramount topic in UML context. Therefore it will represent a sound starting point for all the researchers and designers involved in UML consistency.

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.000
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.951
Threshold uncertainty score0.320

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.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.016
GPT teacher head0.238
Teacher spread0.222 · 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