MétaCan
Menu
Back to cohort
Record W2018530348 · doi:10.1109/qsic.2003.1319092

Generating scenarios from use case map specifications

2003· article· en· W2018530348 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsComputer science

Abstract

fetched live from OpenAlex

The use case map (UCM) notation is being standardized as part of the user requirements notation (URN), the most recent addition to ITU-T's family of languages. UCM models describe functional requirements and high-level designs with causal paths superimposed on a structure of components. The generation of individual scenarios from UCM specifications enables the validation of requirements and facilitates the transition from requirements to design. In this paper, we address the challenges faced during the automated generation of such scenarios. Scenario definitions and traversal algorithms are first used to extract individual scenarios from UCMs and to store them as XML files. Transformations to other scenario languages (for instance, message sequence charts) are then achieved using XSLT. Possible applications of this two-step generation process include early validation and synthesis of design models. Illustrative examples are given based on our current tools and recent experiments.

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

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.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.153
GPT teacher head0.297
Teacher spread0.145 · 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