MétaCan
Menu
Back to cohort
Record W247356838 · doi:10.17705/1jais.00396

Conceptualizing Routing Decisions in Business Processes: Theoretical Analysis and Empirical Testing

2015· article· en· W247356838 on OpenAlexaff
Pnina Soffer, Yair Wand, Maya Kaner

Bibliographic record

VenueJournal of the Association for Information Systems · 2015
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsComputer scienceScope (computer science)Merge (version control)Process (computing)Business processBusiness process discoveryRouting (electronic design automation)Business ruleArtifact-centric business process modelBusiness process managementBusiness process modelingData scienceManagement scienceProcess managementWork in processInformation retrievalOperations managementEngineeringProgramming language

Abstract

fetched live from OpenAlex

Business process models are widely used for purposes such as analyzing information systems, improving operational efficiency, modeling supply chains, and re-engineering business processes. A critical aspect of process representation involves a choice among alternative or parallel routes. Such choices are usually represented in process models by routing structures that appear as “split” and “merge” nodes. However, evidence indicates that modelers face difficulties representing routing options correctly. Clearly, errors in representing routing options might negatively affect the effective use of business process models. We suggest that this difficulty can be mitigated by providing process modelers with a catalog of routing possibilities described in terms that are meaningful to analysts. Based on theoretical considerations, we develop such a catalog and demonstrate that its entries have business meaning and that it is complete with respect to a defined scope of process behaviors that do not depend on resources or on software features. The catalog includes some routing cases not previously recognized. We tested experimentally the catalog in helping subjects understand process behavior. The findings demonstrate that the catalog helps modelers understand and conceptualize process behavior and that the likely reasons are its completeness and the practical terms used to describe its entries.

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.053
metaresearch head score (Gemma)0.290
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.053
Threshold uncertainty score0.282

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0530.290
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0060.008
Science and technology studies0.0020.010
Scholarly communication0.0080.029
Open science0.0040.004
Research integrity0.0030.005
Insufficient payload (model declined to judge)0.0090.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.057
GPT teacher head0.287
Teacher spread0.231 · 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 designObservational
Domainnot available
GenreEmpirical

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

Citations18
Published2015
Admission routes1
Has abstractyes

Explore more

Same venueJournal of the Association for Information SystemsSame topicBusiness Process Modeling and AnalysisFrench-language works237,207