MétaCan
Menu
Back to cohort
Record W1981893749 · doi:10.1109/relaw.2013.6671344

Transforming regulations into performance models in the context of reasoning for outcome-based compliance

2013· article· en· W1981893749 on OpenAlexaff
Rouzbahan Rashidi-Tabrizi, Gunter Mussbacher, Daniel Amyot

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsComputer scienceContext (archaeology)Outcome (game theory)Model transformationGoal modelingNotationDomain (mathematical analysis)Context modelModeling languageTransformation (genetics)Artificial intelligenceRisk analysis (engineering)Process managementRequirements engineeringEngineeringProgramming languageBusiness

Abstract

fetched live from OpenAlex

Recently, interest in performance modeling of out-come-based regulations has grown in the regulatory community. In this context, performance modeling refers to the measuring of important business aspects in a coordinated manner and the use of these measurements for improved decision making. Goal modeling techniques have shown to be beneficial when expressing and analyzing performance models. Since most regulations are still written in natural language, support for the transformation of regulatory text into performance models is needed. This allows regulators and regulated parties to keep working with familiar natural language regulations and to use goal models indirectly while avoiding a potentially significant learning curve for goal-modeling techniques. In this paper, we present such a tool-supported transformation to goal models expressed with the User Requirements Notation that enables reasoning about outcome-based regulations via widely available evaluation mechanism for goal models. The transformation is implemented in the jUCM-Nav goal modeling tool and illustrated with an example from the banking domain.

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.021
metaresearch head score (Gemma)0.050
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: Methods · Consensus signal: Methods
Teacher disagreement score0.021
Threshold uncertainty score0.111

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0210.050
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0030.002
Science and technology studies0.0010.004
Scholarly communication0.0080.009
Open science0.0030.005
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0060.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.123
GPT teacher head0.332
Teacher spread0.209 · 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

Citations12
Published2013
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207