Formal Grammars in Business Process Management: A Systematic Literature Review
This paper presents a systematic literature review of 34 studies that identifies seven distinct research streams at the intersection of formal grammars and Business Process Management, highlighting their comprehensive influence across the BPM lifecycle while noting the lack of cross-stream synthesis and proposing future directions for a unified exploitation of grammatical theory.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to describe how a complex business works—like a bakery, a hospital, or a bank. You have people doing tasks, passing information, making decisions, and following rules. Now, imagine trying to write a set of instructions so precise that a computer can run the whole thing without getting confused.
This paper is a "systematic literature review," which is a fancy way of saying the author, Milliam Maxime Zekeng Ndadji, went on a massive treasure hunt. He looked at hundreds of research papers to find all the ways scientists have used Formal Grammars to solve business problems.
Here is the simple breakdown of what he found, using everyday analogies.
What is a "Formal Grammar"?
Think of a formal grammar not as a school lesson on English, but as a recipe book for generating stories.
- In a normal recipe, you have ingredients (flour, eggs) and steps (mix, bake).
- In a grammar, you have "rules" that tell you how to combine basic building blocks to create infinite valid sentences or, in this case, infinite valid business processes.
- Just as a grammar can generate every possible sentence in a language, a "process grammar" can generate every possible way a business task could be performed.
The Big Discovery: Seven Different "Schools of Thought"
The author found 34 important studies and grouped them into seven distinct research streams. Imagine these as seven different teams of architects, all trying to design the same building (a business process), but using different blueprints and tools.
1. The "Organizational Poets" (Stream I)
- The Idea: These researchers treat business routines like a language. They believe that just as people speak in sentences, organizations "speak" in patterns of action.
- The Analogy: Imagine a dance troupe. Instead of writing down every single step, they define a few basic moves and rules for how to combine them. This allows them to describe infinite dance routines without writing a script for every single one.
- What they do: They use these rules to design new ways of working or to figure out how a company actually works by observing their "dance."
2. The "Grammar Police" (Stream II)
- The Idea: This team looks at the standard languages businesses use (like BPMN, which is a drawing language for processes) and checks if they are "grammatically correct" according to deep philosophical rules about reality.
- The Analogy: Imagine a language teacher checking a student's essay. They aren't just checking for spelling; they are checking if the student used the right words to describe real-world objects. They found that some popular business drawing tools are missing words or use the same word for two different things, which causes confusion.
3. The "Structural Architects" (Stream III)
- The Idea: These researchers focus on the skeleton of the process. They want to make sure the structure is valid before worrying about what happens inside.
- The Analogy: Think of building a house. Before you worry about the paint or the furniture, you need to make sure the walls are standing up and the roof isn't upside down. They use strict rules to ensure you can't build a "process house" that collapses. They also help manage "variants"—like building a house with a garage for one family and a pool for another, using the same basic blueprint.
4. The "Data & Role Integrators" (Stream IV)
- The Idea: Traditional process maps show what happens, but they often forget who is doing it and what data they are using. This team adds "attributes" (tags) to the rules.
- The Analogy: Imagine a game of chess. The rules tell you how pieces move (the structure). But these researchers add a layer that says, "Only the Queen can move here, and she can only move if she has 50 points of energy." They combine the movement rules with the player's identity and the data they are carrying, allowing for complex, decentralized teamwork.
5. The "Shape Shifters" (Stream V)
- The Idea: Business processes are often drawn as pictures (graphs). This team uses "Graph Grammars" to turn one picture into another automatically.
- The Analogy: Imagine you have a sketch of a house drawn in crayon. You want to turn it into a 3D model for a video game. These researchers have a magical machine (a graph grammar) that takes the crayon drawing and instantly rebuilds it as a 3D model, ensuring all the windows and doors line up perfectly. They also use this to create fake "test houses" to see if their software works.
6. The "Detectives" (Stream VI)
- The Idea: Instead of writing rules first, these researchers look at the "crime scene" (the data logs of what actually happened) and try to reverse-engineer the rules.
- The Analogy: Imagine a detective finding a pile of receipts and trying to figure out the recipe for a secret sauce. They look at the patterns in the data to guess the grammar that generated it. This helps businesses discover what they are actually doing, rather than what they think they are doing.
7. The "Logic Philosophers" (Stream VII)
- The Idea: This small group uses advanced math (Process Algebras) to prove that a process will never get stuck or make a mistake.
- The Analogy: Imagine a traffic light system. These researchers don't just build the lights; they use complex math to prove, with 100% certainty, that two cars will never crash at the intersection, no matter how the traffic flows. They treat the business process like a mathematical equation that must balance perfectly.
The Main Problem: Everyone is Working Alone
The most important finding of this paper is that these seven teams are not talking to each other.
- The "Poets" (Stream I) don't talk to the "Detectives" (Stream VI).
- The "Shape Shifters" (Stream V) don't talk to the "Logic Philosophers" (Stream VII).
They are all using different tools to solve parts of the same problem, but they haven't built a single, unified system that does it all.
The Future Challenge
The author argues that the future of Business Process Management lies in connecting these seven streams.
Imagine a super-tool where:
- You design a process using the "Poet's" creative rules.
- The "Architect" checks the structure.
- The "Integrator" adds the data and people.
- The "Shape Shifter" turns it into a computer program.
- The "Philosopher" proves it won't crash.
- The "Detective" watches it run and updates the rules automatically if things change.
The paper concludes that while we have all the individual pieces, we haven't yet built the machine that puts them all together. The goal is to create a unified "grammar theory" that can handle the design, execution, and improvement of business processes all in one go.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.