MétaCan
Menu
Back to cohort
Record W2004901564 · doi:10.1145/1243987.1243989

Metamodel-based model conformance and multiview consistency checking

2007· article· en· W2004901564 on OpenAlexaff
Richard F. Paige, Phillip J. Brooke, Jonathan S. Ostroff

Bibliographic record

VenueACM Transactions on Software Engineering and Methodology · 2007
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsYork University
FundersEngineering and Physical Sciences Research CouncilEuropean Commission
KeywordsMetamodelingComputer scienceSequence diagramUnified Modeling LanguageConformance checkingConsistency (knowledge bases)Model checkingProgramming languageSoftware engineeringCompleteness (order theory)Applications of UMLConsistency modelAutomationArtificial intelligenceWork in process

Abstract

fetched live from OpenAlex

Model-driven development, using languages such as UML and BON, often makes use of multiple diagrams (e.g., class and sequence diagrams) when modeling systems. These diagrams, presenting different views of a system of interest, may be inconsistent. A metamodel provides a unifying framework in which to ensure and check consistency, while at the same time providing the means to distinguish between valid and invalid models, that is, conformance. Two formal specifications of the metamodel for an object-oriented modeling language are presented, and it is shown how to use these specifications for model conformance and multiview consistency checking. Comparisons are made in terms of completeness and the level of automation each provide for checking multiview consistency and model conformance. The lessons learned from applying formal techniques to the problems of metamodeling, model conformance, and multiview consistency checking are summarized.

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.018
metaresearch head score (Gemma)0.055
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.018
Threshold uncertainty score0.095

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0180.055
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0020.004
Bibliometrics0.0030.002
Science and technology studies0.0010.005
Scholarly communication0.0040.007
Open science0.0050.006
Research integrity0.0020.004
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.091
GPT teacher head0.317
Teacher spread0.226 · 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

Citations125
Published2007
Admission routes1
Has abstractyes

Explore more

Same venueACM Transactions on Software Engineering and MethodologySame topicModel-Driven Software Engineering TechniquesFrench-language works237,207