MétaCan
Menu
Back to cohort
Record W83518946

Supporting Flexible Business Processes with a Progression Model.

2004· article· en· W83518946 on OpenAlexaff
Nicole Ann Stavness, Kevin A. Schneider

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsWorkflowComputer scienceFlexibility (engineering)Transaction processingTransaction processing systemDatabase transactionOnline transaction processingBusiness processArtifact-centric business process modelDatabaseDistributed transactionWorkflow management systemBusiness process modelingSoftware engineeringBusinessWork in process
DOInot available

Abstract

fetched live from OpenAlex

Users require flexibility when interacting with information systems to contend with changing business processes, and to support diverse workflow. Model-based user interface design needs to accommodate flexible business processes by integrating workflow activities with other model approaches. We present a progression model to help in developing systems that support flexible business processes. The progression model tracks a user's interaction when using a transaction-based information system. The steps a user takes to create a transaction and the state of the transaction at each step is made explicit. This provides the user with a mechanism to deal with partial information, interrupted and concurrent transaction entry, and the processing of multiple transactions. The paper describes the progression model along with the potential workflow benefits of recording progressions.

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.003
metaresearch head score (Gemma)0.009
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.007
Threshold uncertainty score0.022

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.009
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0040.009
Open science0.0010.002
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0070.002

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.019
GPT teacher head0.270
Teacher spread0.250 · 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

Citations11
Published2004
Admission routes1
Has abstractyes

Explore more

Same topicBusiness Process Modeling and AnalysisFrench-language works237,207