MétaCan
Menu
Back to cohort

Towards Checking Consistency-Breaking Updates between Models and Generated Artifacts

2021· article· en· W4200047428 on OpenAlexaff
MohammadAmin Zaheri, Michalis Famelis, Eugene Syriani

Bibliographic record

Venue2021 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C) · 2021
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsUniversité de Montréal
Fundersnot available
KeywordsComputer scienceConsistency (knowledge bases)MetadataConsistency modelSet (abstract data type)SoftwareCode (set theory)Data modelingSoftware engineeringModel-driven architectureSoftware developmentData consistencyProgramming languageData miningDatabaseArtificial intelligenceWorld Wide Web

Abstract

fetched live from OpenAlex

Model-based Low-Code systems rely on high-level specifications (models) to generate all artifacts of the resulting software. Such artifacts can be code, schemas, as well as data, and metadata. Maintaining consistency between models and artifacts generated from them is at the core of generative approaches in software engineering. Existing approaches have focused on the consistency problem between specific pairs of artifacts, such as models and their metamodels, class diagrams and generated code, and database schemas and data. Instead, we envision a holistic approach for maintaining the consistency that encompasses all generated artifacts. In this paper, we motivate our approach with a case study from a real model-driven software system. We identify scenarios where updates to either models or generated artifacts break consistency and outline a set of challenges and future research directions.

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.057
metaresearch head score (Gemma)0.333
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: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.057
Threshold uncertainty score0.302

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0570.333
Meta-epidemiology (narrow)0.0020.005
Meta-epidemiology (broad)0.0030.004
Bibliometrics0.0050.004
Science and technology studies0.0030.009
Scholarly communication0.0100.022
Open science0.0090.014
Research integrity0.0070.010
Insufficient payload (model declined to judge)0.0020.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.307
Teacher spread0.216 · 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

Citations7
Published2021
Admission routes1
Has abstractyes

Explore more

Same venue2021 ACM/IEEE International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C)Same topicModel-Driven Software Engineering TechniquesFrench-language works237,207