Home / Support for EA Modelling With eaDocX / Insights / Using UML icons for more useful models

Using UML icons for more useful models

Diagram Graphics for Adults

The UML language gives us some simple graphical elements to represent the key ideas.

or example, a UML Use Case diagram looks like this.
I find that diagrams like this really don’t need explaining, even to non-UML readers.

Maybe I might have to say that the blue oval is a ‘story’ of how something gets done, but the rest is fairly obvious:

  • Some actors are involved in some Use Cases, and
  • a couple of the Use Case include another one.

But you might not know that this use of these shapes is optional. UML also says we can use a simpler ‘rectangle’ notation if we want:

Using this notation style doesn’t seem quite as obvious. The tool which I used for the diagrams – EA – helpfully added some default colors to the diagram, which I have removed, just to make the point that I don’t think this diagram is anything like so immediate. A box which says <<Actor>> doesn’t seem so obvious as one which has a stick-person. Which is why I have never seen a UML Use Case diagram use the rectangle notation.

So why use Rectangles ?

This use of the simple rectangle notation is taken to the extreme by Archimate. Most examples from that language seem to use the rectangle notation exclusively, even when it might give the reader a clue as to what’s being modelled:

An Archimate example, taken from the Open Group specification for Archimate. They are saying that:

  • There are three Business Actors: the luggage, medical insurance and sales department
  • Two of them take the respective Business Roles of Luggage Insurance Seller and Medical Insurance
  • There are some Business Collaborations, where these Roles and Collaborations get together to done something (not specified here)

The equivalent diagram using the non-rectangle notation looks like this:Archimate cartoons

I think that this diagram is easier to read than the one above. Apart from the disappointing visual pun of the ‘role (roll)’, the other two bits of notation seem sensible: the Business Actor looks like a person ,and “collaboration” as of two overlapping circles seems sensible.

I realize that in taking this view, I’m making myself into a  “Mickey-mouse”, child-like modeller. Gerben’s book (Mastering Archimate) comes out really, really strongly against this notation style, and in favour of the simple rectangle:

In my view, these forms are for children, not grown-ups..” and suggests that if I want to use this style, I should go the whole way and “..create a funny drawing with Greek columns, jumping dogs...” (you see, Gerben – I really DID read your book..:-) )

…which is a shame, because I really think that the more visual cues we give our readers, the easier they will find it to understand what we’re trying to say. Like Gerber, I believe PowerPoint and Visio, and especially ANY kind of clip-art are death to modeling, but these aren’t those kinds of random images: they are part of an industry-standard notation, which will be the same no matter who draws it.

Perhaps this is why I found Gerben’s book such a hard read. He does use a consistent color scheme for the Archimate layers, but uses the rectangle style for the boxes, which seems to make the diagrams very similar to each other. Even though they are saying very different things. And all the boxes are deliberately the same size, which means he can’t use the obvious abstraction of ‘big box = big thing’.

So i’m going to stick with my ‘child-like’ modelling, and use the non-rectangle notation.

I never wanted to be a adult anyway.

More Insights

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

Simplifying ideas in a BPMN Process Diagram

25 August 2020

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

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

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