MétaCan
Menu
Back to cohort
Record W4376869467 · doi:10.18280/isi.280201

A Novel Method for Refactoring UML Metamodel

2023· article· en· W4376869467 on OpenAlex
Berraouna Abdelkader

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueIngénierie des systèmes d information · 2023
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsnot available
Fundersnot available
KeywordsMetamodelingCode refactoringUnified Modeling LanguageComputer scienceProgramming languageApplications of UMLSoftware engineeringUML toolSoftware

Abstract

fetched live from OpenAlex

UML metamodel, like other metamodel change through time as a result of changing needs and technical improvements during their life cycle.Adding new update or bug fixing can change UML metamodel, so potential inconsistencies with existing models that correspond to the previous version of the UML metamodel and may become non-compliant with the new version.In this approach, the refactoring facilitates a UML metamodel refactoring in well-defined steps from the basic features.The use of this refactoring allows extending the functionality of the existing UML metamodel.This research focuses on the methods and processes involved in adapting the UML metamodel to changing needs and technical improvements over time.The study highlights the potential for inconsistencies to arise from updates and bug fixing in the UML metamodel.The research methodology used is the refactoring of the UML metamodel through a well-defined process in well-defined steps.The study found that the refactoring process allows for the extension of the basic features of the UML metamodel and the introduction of new functionalities.The research concludes that the use of well-defined refactoring processes is essential in maintaining the evolution of the UML metamodel and ensuring its compliance with changing needs and technical improvements.

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

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.004
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.036
GPT teacher head0.286
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