Products

Home / Support for EA Modelling With eaTeamWorks / Insights / What needs to be included in your EA model content?

What needs to be included in your EA model content?

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

These are some of the most common or most expensive mistakes I’ve seen when people start to create models. All the names of customers and industries have been removed, to preserve the self-respect of the modelers.

The point of a model – of any sort- is to take some aspect of the real world and create an abstraction of it. Then use that to help do something new. How much of The World you choose to model can be a burden. A really big one. So choose your scope carefully, and only model what you NEED to model , and what you have time to understand.

I was once asked to review a model built by some experts in ecology. They wanted to model the causes of ecological threats, especially pollution, and what happens as a result. This could then serve as the basis for ecology-related software solutions.

As is often the case with model reviews, I’m shown into a meeting room with lots of smart people – industry experts – and me. I usually get a bad feeling when they all sit on one side of the table, and put me on the other. Sets a non-collaborative tone. So they explained their model was in three halves, set out on a HUGE whiteboard:

  • The left-hand side, bit which set out the main pollutants: animals, vegetable, mineral. Well thought through, very comprehensive
  • The right-hand side, which had all the effects of pollution: death, disaster etc. Also seemed well modelled.
  • They said the middle bit was a problem.

It was a while ago, but I’m sure that the middle bit, where they were going to describe how the pollutants on the left CAUSED the effects on the right, contain one class. It was called:

It really was. They said, in a very serious voice “we’re having a bit of a problem with this bit“.

You think!

They had got so “into” the problem that they couldn’t see the impossibility of what they were trying to do. I tried to be encouraging: “If you can fix that bit, I think a lot of people would like to talk to you“.

So, no matter how smart you are, and how much you know about the area you’re going to model, remember to be realistic. Don’t try to model the world. Take the smallest possible bit (but not too small) and model that. And get some value from it, somehow. Then maybe you’ll be allowed to carry on.

(first published on the “Artful Modeler” blog in 2015.)

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

Explaining modelling

22 June 2023

..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.

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

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