MétaCan
Menu
Back to cohort
Record W1996489781 · doi:10.1145/1923947.1923974

Towards workflow verification

2010· article· en· W1996489781 on OpenAlexaff
Nazia Leyla, Ahmed Shah Mashiyat, Hao Wang, Wendy MacCaull

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsSt. Francis Xavier University
Fundersnot available
KeywordsWorkflowComputer scienceWorkflow management systemWorkflow technologyWorkflow engineSoftware engineeringModel checkingXPDLWindows Workflow FoundationSoftware deploymentDomain (mathematical analysis)Distributed computingProgramming languageDatabase

Abstract

fetched live from OpenAlex

Workflow Management Systems (WfMS) that help the design and deployment of automated business processes as well as aid their execution and monitoring continue to evolve. Many WfMS use Workflow Patterns as their basic modeling constructs; however, the absence of verification facilities in most WfMS causes the resulting implementation to be at risk of undesirable runtime executions. Model Checking can facilitate the verification of workflow models, provided that we can conveniently implement the workflow model and provide the resources to handle the space requirement of the model. DiVinE is a distributed and parallel Model Checker that can effectively handle the well-known state explosion problem of this domain. In this paper, we present a translation of a collection of established Workflow Patterns into DVE, the input specification language of DiVinE. Thus, by assembling the corresponding DVE translated patterns into a whole model, we can verify properties of workflow models. We discuss the difficulties we have experienced with this approach and explain how that led to the development of an automatic translator tool from YAWL to DVE. We present two case studies and some ongoing work in our research group.

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.019
metaresearch head score (Gemma)0.049
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.019
Threshold uncertainty score0.099

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0190.049
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.004
Bibliometrics0.0030.002
Science and technology studies0.0020.007
Scholarly communication0.0090.012
Open science0.0040.009
Research integrity0.0040.009
Insufficient payload (model declined to judge)0.0080.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.015
GPT teacher head0.224
Teacher spread0.208 · 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 designTheoretical or conceptual
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

Citations7
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicBusiness Process Modeling and AnalysisFrench-language works237,207