Home / Support for EA Modelling With eaDocX / Insights / Use case, package or process?

Use case, package or process?

A time for Packages

Over the last few months, I’ve visited a couple of customers who were each having trouble with packages: one had lots of what they called Use Cases which were really Packages, and the other had lots of Packages which were really Processes.

Their reactions to finding out that maybe this wasn’t the best way to structure their models was also instructive, but more of this later. First the problems.

Elements which are packages

First, the Use Cases which were packages. This is a fairly common beginners error, and usually means the modeller hasn’t quite understood what a Use Case really is: One Person, One Place, One Time. So their first model looked like this:

Use-case experts will be shouting at their screens . ” How can  a Use Case be called ‘Customer Management’ – it doesn’t start with a active verb!”

So clearly these higher-level blue blobs aren’t Use Cases at all – they are groups of other use cases. But these were smart people, and they knew about functional decomposition, so this looked right to them. Then we talked about what a Use Case was, and we decided to change to something more normal:

Hopefully most people would agree that this looks more like a Use Case model should. The strange ‘use cases’ have become packages – just groups of other use cases

Packages which are elements

Now the opposite case. A process model, created by some very good BPMN process modellers, who somewhere took a wrong turn.

So here the problem was reversed. They had somehow decided that there was such a lot of ‘stuff’ under ‘Configure Widgets’ that it must be a Package. That made his documents look really neat as well.

But it’s not: Configure Widgets is a Process, and should be made into an Element (a lower-level ‘thing’ in most tools, which is a child of a Package). So again, we had a chat, and decided to change to something more ‘normal’.

But it’s not: Configure Widgets is a Process, and should be made into an Element (a lower-level ‘thing’ in most tools, which is a child of a Package). So again, we had a chat, and decided to change to something more ‘normal’.good processes
In both cases, I made the argument that it matters how models are structured. These will be viewed, used and changed (hopefully) by many people over many years, so making them conform to what most people will expect to see is really useful. In both cases, they could have happily continued modelling in their original style, and still satisfied their own projects’ needs. But future viewers would be confused

Different Reactions

So far, this is a minor modelling point, and maybe not one which you care about too much. But what made these two events memorable was the differing reactions of the two teams.

One – the Use Cases team – was very reluctant to change their model. It had been produced by several people over many weeks, and had 100’s of use cases. Changing it would be hard (it wasn’t, as it happened – we wrote a little EA script to fix it).

The other team also had lots of processes, listened to the arguments, and immediately decided to change to a more ‘normal’ style.

Now I wish I had a neat theory as to why one team was reluctant to change, and the other not. The ‘process’ team had much more modelling experience than Use Case one, so maybe they felt they understood the argument better. The Process team had already been given lots of feedback on their model, so maybe they were happier to take external suggestions: the Use Case team were blazing a trail for model-based development, so hadn’t had much external feedback.

My learning points – which I’m going have to apply to my own models 🙁   are therefore:

  1. Don’t get too attached to your models. It’s just a way of writing stuff down, not a part of your soul. You’ll leave them behind anyway some day. It’s not personal.
  2. Get other people (who know something about modelling) to look at your stuff, as often as possible. They may know even less than you, but two pairs of eyes is always better than none. And the less they know, the more chance they will ask the ‘stupid question’ which turns out not to be.

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

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