Home / Support for EA Modelling With eaDocX / Insights / Process Modelling with Style

Process Modelling with Style

There may be more ways to model process than you think

I’ve been creating models and teaching modelling for quite a few years now. Domain models, use case models, state models and architecture models.
But I usually sigh when a client asks me to teach process modelling. Not because it’s especially hard to teach, though BPMN has made everything a little more complicated. It’s because, unlike all the other types of models, process models don’t seem to last very long.

This may be because we don’t model things in a way which allows the process to evolve over time, which is what we know our organization will certainly do. But we may be able to help this by thinking about the style and scope of the processes we create. Perhaps then we can make them more long-lasting.

 

Three styles

So here are three styles. The first – hierarchy – which seems to be everyone’s default. The second – Calling – where smart modellers go when models start to get big, and finally ‘Event Linked‘ which I only see very occasionally, but really should get used MUCH more.

So you go to talk to your customer, and they draw out this.

Really simple. Something happens, then a couple of things get done, then we’re finished. And let’s assume that there is lots more to say in detail that is shown here.

So what’s the best style to use for modelling this?

Style 1 - Hierarchy

This is maybe your first thought, assuming that you don’t just keep things as above.

You decide that one process contains the other, in a hierarchy.The top-level process has activities which decompose into lower and lower level processes – they are shown here on the same diagram, but of course each process would have its own diagram.
This shows only two levels of nesting, but 5 or even 10 levels are not uncommon.
Essentially what we have designed here is, in programming terms, a ‘main’ process which has lots and lots of sub-routine calls.

 

Processes built like this work fine, until they start to grow, and when we discover that processes in one hierarchy want to use ones from elsewhere. Then it looks less neat. And turf wars start to decide who ‘owns’ the common processes.

This so popular that the different levels in the process hierarchy get given names: you’ll hear consultants talk about “Level 1 Processes”, or even Level 0 (which are usually something crazy like ‘Run the Business’), so this idea of hierarchy has lots of friends.

But it’s an illusion.

There is no ‘run the business’ process: it has none of the characteristics of the process (start, end, owner, metrics)  – it’s just there to make the PowerPoints look neat.

(end of rant)

Style 2 - Callable (re-usable) processes

A process model which uses only processes with sub-processes will clearly not create any re-usable processes. Which is probably not how many businesses work.
What we need to add to the simple hierarchy is the idea of one process calling another one.
This is implemented in BPMN, even if it’s rather hard to understand. There a little magic involved in saying one process ‘calls’ another, and in setting-up the governance required to manage these re-usable processes. But at least we can easily see where the re-usable stuff is.

But if used together, the combination of Hierarchical and Callable process styles seem to suffer from explosive complexity.
Put simply, they do not grow well.
As they get larger, maintaining all the links between all the process – deciding who is a child of whom, and who calls whom – start to overwhelm many process modellers. At which point, they seem to revert to ‘modelling tool = Visio‘ mode, where the integrity of the model is lost, and instead they get a series of pictures. The pictures may look nice, but they aren’t a model, and require the ‘wetware’ of the modeller if they are to add value to the business.

What’s needed is a way of allowing models to grow elegantly:

  • Allow modellers to create well-modelled processes, with the smallest scope possible which is consistent with achieving the business objectives…
  • ..whilst still showing the interconnections between different parts of the business.
  • Challenge a false, hidden assumption which we may have missed: If I’m a Business Process Modeller, and I’m looking at stuff happening, then that stuff must be happening because it’s a process. But there might not be an end-to-end process

Style 3 - Event-linked processes

Not everything which happens in a business does so because it’s part of a business process.
This is the Business Process Illusion.

Sometimes, stuff just happens. And that stuff makes other stuff happen, and it’s hard to tell where it’s all leading to, but the stuff still keeps happening anyway.
So maybe if we recognise that this is what’s really happening – some well-structured processes in a soup of ‘stuff happening’ – then we’ll spend less time trying to create processes where none exist. And we’ll also create models which better reflect how our business really work, and which are maintainable and readable.
So our business maybe looks like this:

  • Events happen in the outside world, over which we have no control
  • These trigger processes, which end with other (internal) business events.
  • These events in turn trigger other processes
  • ..but there is no end-to-end process: just processes creating events, which trigger processes, which create….

So our example process can look like this.

This approach has lots of advantages for the modeller:

  1. Each process can be written in a self-contained way, with well-formed start-, end- and intermediate events (in BPMN-speak)
  2. The events which come out of processes can be understood as proper Business Events, which might have already been modelled elsewhere, such as in Archimate .
  3. Processes can be given a scope which reflects how a business works, rather than trying to pretend there is an end-to-end process where the business doesn’t really have one.

Summary

In reality, a blend of each of these approaches is probably what you need, but recognising that there are (at least) 3 different styles to choose from means we’re not constrained to simple hierarchical processes, with their giant-sized end-to-end scope.

Because we all know that sometimes, stuff just happens.

More Insights

Models matter - nearly as much as deliverables

25 August 2020

Models matter - nearly as much as deliverables

Learn More

Mechanical vs Content Quality

25 August 2020

Mechanical vs Content Quality - they are different

Learn More

Fixing your meta-model

25 August 2020

Fixing your meta-model too early is bad

Learn More

Advice for the new modeller #2 - (not) Melting the Pan

25 August 2020

Advice for the new modeller #2 - (not) Melting the Pan

Learn More

Advice for the new modeller #1 - Modelling The World

25 August 2020

Advice for the new modeller #1 - Modelling The World

Learn More

Knowing when to give up

25 August 2020

Knowing when to give up makes for better Business Analysts

Learn More

Diagram Graphics for Adults

25 August 2020

Diagram Graphics for Adults

Learn More

Decision, decisions

25 August 2020

Documenting your decisions makes models more useful

Learn More

Beck's Abstraction

25 August 2020

Possibly the best model abstraction in the world

Learn More

A time for Packages

25 August 2020

A time for Packages

Learn More

Ideas in diagrams

25 August 2020

How many ideas are there in your diagrams?

Learn More

Model Driven Analysis

25 August 2020

What is it ?

Learn More

"Look at me" Diagrams

25 August 2020

"Look at me" Diagrams - and why they are usually bad

Learn More

Why we model

14 August 2020

A short argument about 'why we model' which you might want to re-use

Learn More

Model Curation techniques for EA - #1: Cleaning

14 August 2020

Cleaning your model before you let other people see it

Learn More

Model Provenence

14 August 2020

When you look at some modelling work, knowing where it came from is vital information. This article explores some ways to capture and use this

Learn More

Getting to the Point

29 July 2020

How to help your stakeholders with documents that communicate efficiently and effectively.

Learn More

The Well Dressed Model

28 July 2020

Seven ways to organise your EA models so that other people can understand them

Learn More

Choosing Your Subset

27 July 2020

One of my occasional pleasures in helping people to do better modelling is to tell them the things they DON’T need to do. And ...

Learn More

Webinar - Working with Interactive Documents

17 July 2020

This webinar from the EA Global Summit 2020 describes how to generate interactive Word documents, and use them to automate your EA model updates.

Learn More

Webinar - How to successfully scale up your EA modelling team

30 June 2020

The key issues and decisions to consider when scaling up your modelling team, and how to avoid the common pitfalls.

Learn More

Model Curation techniques for EA – 2: Navigating

16 April 2020

This is the second article in the series which describes simple techniques to improve the effectiveness of EA model sharing.

Learn More

Model Curation techniques for EA – 3: Validating

16 April 2020

So now users can find their way around successfully. The question is, what will they find when they get there?

Learn More

Explaining the General with a Specific

16 April 2020

Explaining ideas using Object diagrams

Learn More

Different documents for Different People

16 November 2018

How to tailor information to each user - making it as easy as possible for everyone to engage with your work, project or deliverables.

Learn More

Document or Model View?

21 May 2018

Use your documents as an alternative to Model Views.

Learn More

Color your Knowledge

25 April 2018

A while ago a client asked me to look at some process diagrams which had been created for them by a well-known consultancy.

Learn More

Model Curation

6 March 2018

How cleaning, navigating and validating your EA model makes sharing and collaborating much more effective.

Learn More

Context - Where are we?

20 October 2017

I’m occasionally asked “What’s the most re-usable bit of a model – where should I start?“.

Learn More

Glossary

12 October 2017

In a recent talk, I asked the audience of about 100 BAs which of them maintained a glossary as part of their work.

Learn More

Hard and Soft

11 October 2017

No, not about Brexit… More about styles of Business Analyst.

Learn More

Printing connectors

18 October 2016

Creating documents that start with the connections between the things in your model

Learn More

Using Multi-hop relationships to display Branch/Merge with EA13

11 August 2016

One of the most common requests we see from new EA users is: "Why can’t I do branch/merge with EA?

Learn More

Compare pricing and features

Choose the eaDocX edition that’s right for you and your team

Compare Pricing

Download a free trial

Take a free, no obligation, 30-day trial of eaDocX. Discover for yourself why it’s the world’s best-selling Enterprise Architect extension.

Download