Home / Support for EA Modelling With eaDocX / Insights / Simplifying ideas in a BPMN Process Diagram

Simplifying ideas in a BPMN Process Diagram

How to find the right number of ideas to include in your model.

A common theme to the examples in the Reading Diagrams posting was that great diagrams have a small numbers of abstractions. Indeed, they are made great often by what bits of the real-world they choose to miss-out.

I’m going to refer to these not as ‘abstractions’ – it makes them sound, well, abstract, but as “Ideas”, because then I get to define what I mean.

Diagram Overloading

Consider a really simple UML Use Case diagram:

It has a small number of ideas:

There are Actors and Use Cases, and Actors can use Use Cases. I make this a single idea, because it includes notions of what an Actor and a Use case are, and what the link between them means.

There’s a second idea, buts its such a small and simple one, that I don’t think this is a 2-idea diagram. The Use Cases are contained inside a box, which represents the software system we’re thinking about. So maybe this is a 1.5 idea model.

But there’s more we want to say in our modelling work.

We’ve decided to store the Issues which exist for our project in the model as well. That way, they can be linked-up to the relevant Use Cases or Actors.
Which is fine, until we add them to the diagram:

The diagram is now definitely > 2 ideas.

But now we’ve got started, we can tell ourselves that we need to create a one-stop diagram, which will really help people to understand these Use Cases in their wider context. So we add some more stuff:

 

We can add information about which stakeholders represent which actors, and which people in the project team ‘own’ which of the issues.

We’re now well over the line in to a 4 or 5-idea model.

Sure, it’s a one-stop diagram, but we’re asking a lot of our readers here.

Perhaps we might keep this as a diagram just for private use, and instead create several smaller diagrams which have a smaller number of ideas:

  • The original diagram: Use Case & Actors and the system boundary
  • One which shows who represents which actors
  • One showing the Issues, and their related model ‘thing’ and who owns them:

With this diagram, our layout is totally different.

We are focused on a single idea: the Issue. Issues are owned by people, and they relate to some aspect of the main model. So this is still a 1-idea model.

Idea-heavy Modelling Languages

The example above is an easy one to fix, because we took the UML-defined idea of a Use case diagram, and added our own bits to it. So we can just as easily remove those bits to get back to a 1-idea diagram.

But what if the language we are using is idea-heavy? A modelling language which fits this description is BPMN.

This is a OMG way of describing business processes, and it’s an accurate way of saying almost all we need to say about processes. But that accuracy comes at a price. Lots of ideas.

Here’s a typical BPMN process.

What we’re trying to says is:

  1. The order processing department (Lane) Process Orders (Activity), when they Receive an order (event).
  2. The QA department (Lane) then check the order (Activity) and if its ok (Decision) then the order is complete (End type Event)
  3. If its not OK, then they send an order rejection (‘send’ type Activity) to the Customer (Black Box Pool) via a Message (Message connector) and throw a Bad Order Created event (‘error’ type End Event)

And this is a really simple diagram. We have not said what types of Activities they are – BPMN has 8 types. Nor have we specified the data objects which are passed between the Activities, and this is a really useful aspect of BPMN.

So the very richness of the language creates its own challenges for the modeller: how to keep the number of ideas as small as possible to help the reader. (there’s an example of simplifying a giant-sized BPMN diagram in fixing a look-at-me diagram/)

Something else which I first saw in the BPMN notation was the idea of adding lots of types to ideas, and making that part of the visual representation. For example, BPMN has 8 types of Activity:

This is the precision of BPMN at work. Each of these different types of Activity means something slightly different. ‘Send’ Activities should have a Message connector going from them, and will only go onto the next Activity once that message has been sent. So they are useful but they contribute to the basic complexity of the language, and therefore to the number of ideas which appear in any given diagram.

As a rule, I tend to avoid using ANY of these types on ANY diagram: I’d much rather use a note linked to a ‘normal’ (BPMN “abstract”) Activity:

I’m making a deliberate decision here to exchange accuracy for readability. The readers of my process diagrams might not know that the little hand in the top-left of an Activity box means ‘Manual Activity’, but the little note makes it obvious.

More Insights

Quick Document - Video guides

22 June 2021

If you are new to eaDocX, the best place to start is by creating a Quick Document. Let eaDocX do the work

Learn More

eaDocX in the Cloud

6 April 2021

Enterprise Architect document creation for EA SAAS environments

Learn More

Producing a RACI report

11 March 2021

Producing a RACI report from data held in EA, mapping stakeholders to any project deliverables is straightforward with eaDocX.

Learn More

Using Excel to create an EA dashboard

16 February 2021

A simple example of an EA dashboard, to show how you can create your own and show the information in your EA model to your project team

Learn More

Where's the best place to start modelling?

19 October 2020

Advice for the new modeller #1 - Where do you start?

Learn More

Process based model styles

25 August 2020

How to use BPMN and UML to make models which last.

Learn More

Models matter - nearly as much as deliverables

25 August 2020

Models matter - nearly as much as model deliverables

Learn More

Improving model quality using a Sparx EA reference model

25 August 2020

Maintain quality with tools to find and fix mechanical errors in your modelling

Learn More

Fixing your meta-model

25 August 2020

Advice for the new modeller #3 – Fixing your meta-model

Learn More

How much domain modelling is enough?

25 August 2020

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

Learn More

What needs to be included in your EA model content?

25 August 2020

Advice for the new modeller #4 – (not) Modelling The World

Learn More

Knowing when to give up

25 August 2020

Knowing when to step back makes for better Business Analysts

Learn More

Using UML icons for more useful models

25 August 2020

Diagram Graphics for Adults

Learn More

Using Enterprise Architect to document decision making

25 August 2020

Make your models more useful for future modellers

Learn More

Beck’s Map: an EA model abstraction example

25 August 2020

Possibly the best model abstraction in the world

Learn More

Use case, package or process?

25 August 2020

A time for Packages

Learn More

Explaining EA Sparx Systems to non-modellers

25 August 2020

Model driven analysis - the best way to define what we do?

Learn More

How to simplify BPMN Data Models

25 August 2020

Why simplifying your diagrams can actually make them more informative.

Learn More

Create useful models using the Sparx EA Tool

18 August 2020

Advice for the new modeller #3 - Producing useful outputs with your new EA tool.

Learn More

Beginners guide to Enterprise Architect software

18 August 2020

Our advice for new EA modellers

Learn More

UML Business Analyst Solutions

14 August 2020

Using UML to resolve inconsistencies, gaps and overlaps.

Learn More

Cleaning: How to Simplify Enterprise Architecture Models

14 August 2020

Model Curation Techniques # 1 - Cleaning your EA model before you let other people see it

Learn More

Including Sparx EA Model Provenance

14 August 2020

Sparx EA model help to explain to others why your models look the way they do.

Learn More

What to include in your enterprise architect documentation

29 July 2020

How to create documents which communicate your ideas efficiently and effectively to stakeholders.

Learn More

Organising an Enterprise Architect Model

28 July 2020

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

Learn More

Choosing Your UML Subset

27 July 2020

Narrowing down the modelling ideas in your Enterprise Architect model to make consistent, understandable models.

Learn More

Webinar: Using Interactive Documents to Collate Sparx EA Model Feedback

17 July 2020

A webinar from the EA Global Summit 2020.

Learn More

Webinar: How to successfully scale up your Enterprise Architect team

30 June 2020

A webinar from the EA Global Summit 2020.

Learn More

Navigating Models: Enterprise Architect Help and Techniques

16 April 2020

EA Model Curation Techniques #2 - Making models easy to navigate.

Learn More

Validation: Improving your Enterprise Architecture Model Structure

16 April 2020

EA Model Curation Techniques #3 - Validating your model

Learn More

Modelling techniques for business architecture software to explain general patterns

16 April 2020

Using object diagrams to explain general patterns with specifics.

Learn More

How to create personalised documents using Sparx document generation tools

16 November 2018

A guide to creating documents from Sparx EA models so everyone can engage with your work, project or deliverables.

Learn More

Document or Enterprise Architect Views?

21 May 2018

Create documents to be used by non-EA users instead of model views.

Learn More

Improve your enterprise architecture model using colour

25 April 2018

Careful use of colour and shape makes models easier to digest.

Learn More

Model curation techniques for EA Sparx Systems

6 March 2018

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

Learn More

The most re-used model components in Sparx Enterprise Architect.

20 October 2017

Why is the project summary the most read element in an EA model?

Learn More

Creating a Glossary: Business Analyst Terminology

12 October 2017

Streamline your business understanding with shared definitions.

Learn More

Business Process Analyst Styles

11 October 2017

Find out if you are a 'hard' or 'soft' Business Analyst.

Learn More

How to Print Sparx EA Connectors

18 October 2016

Structure your documents using the connectors in your Sparx 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