MétaCan
Menu
Back to cohort
Record W2131689139 · doi:10.5381/jot.2009.8.2.a2

Generating Maude Specifications From UML Use Case Diagrams.

2009· article· en· W2131689139 on OpenAlexaff
Farid Mokhati, Mourad Badri

Bibliographic record

VenueThe Journal of Object Technology · 2009
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsUniversité du Québec à Trois-Rivières
Fundersnot available
KeywordsProgramming languageComputer scienceUnified Modeling LanguageUse Case DiagramClass diagramSoftware engineeringSoftware

Abstract

fetched live from OpenAlex

This paper presents a systematic approach supporting the translation of UML use case diagrams, describing the functional requirements of a system, into a Maude formal specification. The proposed approach also considers the static and dynamic features of object-oriented systems. The formal and object-oriented language Maude, based on rewriting logic, supports formal specification and programming of concurrent systems. The major motivations of this work are: (1) translating the functional requirements of an object-oriented system, specified using UML use case diagrams, into a Maude specification, (2) translating its static and dynamic aspects, described using UML class, communication and state-transitions diagrams respectively, into a Maude specification, and (3) integrating the formal verification of the consistency of the models, since the analysis phase. A case study is presented to illustrate our approach.

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.007
metaresearch head score (Gemma)0.033
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: Empirical · Consensus signal: none
Teacher disagreement score0.007
Threshold uncertainty score0.039

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.033
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0050.002
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0030.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0070.004

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.032
GPT teacher head0.250
Teacher spread0.217 · 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
GenreEmpirical

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

Citations14
Published2009
Admission routes1
Has abstractyes

Explore more

Same venueThe Journal of Object TechnologySame topicModel-Driven Software Engineering TechniquesFrench-language works237,207