A hybrid approach to workflow modelling

Abstract

Purpose The increase in business process management projects in the past decade has seen an increase in demand for business process modelling (BPM) techniques. A rapidly growing aspect of BPM is the use of workflow management systems to automate routine and sequential processes. Workflows tend to move away from traditional definitions of business processes that can often be forced to fit a model that does not suit its nature. Existing process modelling tools tend to be biased to either the informational, behavioural or object‐oriented aspect of the workflow. Because of this, models can often miss important aspects of a workflow. As well as managing the relationship between the types of model it is important to consider who will be using it, as process models are useful in various ways. The paper aims to address these issues. Design/methodology/approach This paper reports on a case study in a manufacturing company, where users were surveyed to see which are the notations that are most common in modelling based on two main categories (i.e. behavioural and informational). Findings The research outcomes showed that there is no prevailing set of standards used for either of these categories, while most users feel the need to use more than one approach to model their system at any given time. Many companies face problems when trying to model the behaviour of human workers in the business processes. Existing techniques are mostly designed at modelling information systems or business processes, and rarely attempt to integrate the two. Originality/value This paper proposes the use of a new hybrid modelling methodology, which is an original idea, on existing tools and methodologies. Key authors in the literature recommend against the trend of developing a brand new methodology, so existing tools from each end of the scale were combined to provide a solution which is capable of modelling IS and BP.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 102 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.