MétaCan
Menu
Back to cohort
Record W1666161204 · doi:10.48550/arxiv.1012.2469

UCMExporter: Supporting Scenario Transformations from Use Case Maps

2010· preprint· en· W1666161204 on OpenAlexaff
Daniel Amyot, Ali Echihabi, Yong He

Bibliographic record

VenuearXiv (Cornell University) · 2010
Typepreprint
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsSequence diagramComputer scienceNotationUnified Modeling LanguageInteroperabilitySoftware engineeringSequence (biology)Programming languageActivity diagramTransformation (genetics)Model transformationSystems engineeringSoftwareEngineeringArtificial intelligence

Abstract

fetched live from OpenAlex

The Use Case Maps (UCM) scenario notation is applicable to many requirements engineering activities. However, other scenario notations, such as Message Sequence Charts (MSC) and UML Sequence Diagrams (SD), have shown to be better suited for detailed design. In order to use the notation that is best appropriate for each phase in an efficient manner, a mechanism has to be devised to automatically transfer the knowledge acquired during the requirements analysis phase (using UCM) to the design phase (using MSC or SD). This paper introduces UCMEXPORTER, a new tool that implements such a mechanism and reduces the gap between high-level requirements and detailed design. UCMEXPORTER automatically transforms individual UCM scenarios to UML Sequence Diagrams, MSC scenarios, and even TTCN-3 test skeletons. We highlight the current capabilities of the tool as well as architectural solutions addressing the main challenges faced during such transformation, including the handling of concurrent scenario paths, the generation of customized messages, and tool interoperability.

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.005
metaresearch head score (Gemma)0.019
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.015
Threshold uncertainty score0.052

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.019
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0030.001
Science and technology studies0.0010.001
Scholarly communication0.0030.005
Open science0.0030.004
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0150.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.128
GPT teacher head0.226
Teacher spread0.097 · 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 designNot applicable
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

Citations8
Published2010
Admission routes1
Has abstractyes

Explore more

Same venuearXiv (Cornell University)Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207