Products

Explaining modelling

..or, "how to reduce 20 years of modelling into 5 bullets". If you need to explain to someone what we do, try this short explanation.

Explaining the idea of 'modelling' to non-modelers

On my last holiday, in between soaking up some rays and watching the sun go down over the ocean, I got around to reading some of those books that have been on the ‘must read’ list for months.

And even talked to the family for a change. One conversation started with ‘Dad – what do you actually DO‘.

This is a tough question when your life is spent manipulating ideas around a screen, and trying to understand how businesses want to work. All a bit abstract.

So this is what I came up with:

  1. We capture what we’re trying to think about in a rigorous form. Our ideas may start out as a Mind Map, but the blobs on the picture get quickly morphed into more definite things: Risks or Requirements, Domain concepts or processes, States or Business Functions, not just paragraphs of text.
    So no Blob and Stick diagrams, and no more Visio.
  2. We put those ‘things’ into some kind of tool. This is essential. What we’re grappling with here are problems which larger than will fit into a single head, so we out-source the remembering to a computer *.
  3. We think hard about the relationships between the ‘things’. Just like the WWW, it’s the links which provide the richness. So a Business Goal and a User Story are interesting ‘things’, but if we connect them together by saying ‘this User Story contributes to the achievement of the business goal, we start to add more value to the problem.
  4.  We use the modeled ideas, and the tool where they sit to help us to do a better job of analyzing.
    For example:

    • “This User Story doesn’t connect back to any project objectives? What’s it doing in scope?”
    • “Why do we have a stakeholder who doesn’t appear to be responsible for any Requirements? Did we miss something?”
    • “Have we implemented all the local security requirements somewhere in the solution?”
  5. We treat the model as an important organizational asset. Over time, the model will contain more and more knowledge about how and why our organization works. And we’ll have spent thousands or millions of (£/$/€) creating it, so we’d better look after it, and make sure it gets used by every project, but also stays consistent and useful.

So that’s it in 5 bullets.

(* the idea of ‘outsourcing the remembering’ came from a holiday reading book ‘The Organised Mind’)

Originally published: August 2013

More Insights

The eaTeamWorks product philosophy

22 November 2023

The eaTeamWorks product philosophy is simple - and it's all about you, the modeler.

Learn More

The role of diagrams in Enterprise Architect

20 November 2023

Not every modeling problem can be solved with a diagram. Some diagrams are essential, some are useful, but some may be misleading. But which ones?

Learn More

Where to start modelling

22 June 2023

Faced with an empty model and a problem to solve, where should you start? Some advice for people with no modelling experience

Learn More

Creating useful, long-lasting process models

22 June 2023

Process models are hard to maintain. Maybe that's because they have poor structure. Here are some ways to give them a longer life.

Learn More

eaTeamWorks Launch: What does this change mean for me?

15 June 2023

Information for existing eaDocX, Model Expert and Portfolio Manager license holders

Learn More

Create useful models using Sparx EA

1 June 2023

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

Learn More

What needs to be included in your EA model content?

1 June 2023

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

Learn More

Beginners guide to Enterprise Architect software

1 June 2023

Our advice for new EA modellers

Learn More

How much domain modelling is enough?

1 June 2023

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

Learn More

Simplifying ideas in a BPMN Process Diagram

1 June 2023

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

Learn More

Beck’s Map: an EA model abstraction example

1 June 2023

Possibly the best model abstraction in the world

Learn More

Process based model styles

1 June 2023

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

Learn More

Where to start with Enterprise Architect data modeling

1 June 2023

BPM Tips: Advice for the new modeler #1

Learn More

Reading diagrams

1 June 2023

Why some diagrams are better than others, how to present diagrams, and how big or small to make them

Learn More

Putting EA at the heart of your business

1 June 2023

Ian's workshop at the EA Global Summit on September 14th 2022

Learn More

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download