UML Business Analyst Solutions
Using UML to resolve inconsistencies, gaps and overlaps.
I still meet people, usually at industry conferences – who are ‘not into’ modelling. They think its some sort of high-powered, ivory tower exercise, involving creating lots of unnecessary diagrams which aren’t useful.
Sometimes I take the time to persuade these people, and this is the argument I use. It’s specific to Business Analysis, which is what I do, but the same argument can be modified for other roles which use modelling.
Start with – “what’s your job?“. If the answer is Business Analysts or even their new big brothers “Enterprise Architects” then ask “what’s the purpose or ‘added value’ of your job?“.
If the answer from the BA is ‘I write down all the requirements, then feed them back to stakeholders‘ then give up – this person isn’t a BA: they are a secretary, and may never get what you’re talking about. Replace them with a Dictaphone.
Of the rest – thankfully the majority – most will come up with some variation of:
“My job is to look for the gaps, overlaps and inconsistencies in what is being requested“. This is the best summary I know for what I do as a BA.
So how do we do this? If the problem is small then this might be done by just screwing up your face, reading everything about the problem, thinking hard, and writing down what’s missing, where the overlaps are, and what’s inconsistent.
Not many problems are this small. If they were, they probably wouldn’t need a BA. So we’re left with the awkward, bigger problems, and here’s where the good BA gets organised. I seem to follow 3 steps:
- Categorize and sort it – take what you find out, and put into piles of similar knowledge. Requirements, assumptions, stakeholders, software systems. All of these get mentioned, I need to decide what a piece of knowledge is. Without this, I can’t do the next step.
- Model it – this means taking the piles of similar-styled knowledge, and linking things to other things. So stakeholders get hooked-up to Requirements because they ‘own’ them. Use cases get put inside Software systems, because the one implements the other.
- Think about it – which is where we really earn our money. So far, (1) and (2) have resulted in some nice diagrams, and lists of things. But no value-add.
Now I can start to look for gaps, overlaps and inconsistencies, and, if I’ve put all these things, relationships and diagrams into a model, I can get the model to do the work.
More Insights
Where's the best place to start modelling?
19 October 2020
Advice for the new modeller #1 - Where do you start?
Learn MoreProcess based model styles
25 August 2020
How to use BPMN and UML to make models which last.
Learn MoreModels matter - nearly as much as deliverables
25 August 2020
Models matter - nearly as much as model deliverables
Learn MoreImproving 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 MoreFixing your meta-model
25 August 2020
Advice for the new modeller #3 – Fixing your meta-model
Learn MoreHow much domain modelling is enough?
25 August 2020
Advice for the new modeller #2 – (not) Melting the Pan
Learn MoreWhat needs to be included in your EA model content?
25 August 2020
Advice for the new modeller #4 – (not) Modelling The World
Learn MoreKnowing when to give up
25 August 2020
Knowing when to step back makes for better Business Analysts
Learn MoreUsing Enterprise Architect to document decision making
25 August 2020
Make your models more useful for future modellers
Learn MoreBeck’s Map: an EA model abstraction example
25 August 2020
Possibly the best model abstraction in the world
Learn MoreSimplifying ideas in a BPMN Process Diagram
25 August 2020
How to find the right number of ideas to include in your model.
Learn MoreExplaining EA Sparx Systems to non-modellers
25 August 2020
Model driven analysis - the best way to define what we do?
Learn MoreHow to simplify BPMN Data Models
25 August 2020
Why simplifying your diagrams can actually make them more informative.
Learn MoreCreate 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 MoreBeginners guide to Enterprise Architect software
18 August 2020
Our advice for new EA modellers
Learn MoreCleaning: 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 MoreIncluding Sparx EA Model Provenance
14 August 2020
Sparx EA model help to explain to others why your models look the way they do.
Learn MoreWhat to include in your enterprise architect documentation
29 July 2020
How to create documents which communicate your ideas efficiently and effectively to stakeholders.
Learn MoreOrganising an Enterprise Architect Model
28 July 2020
Seven ways to organise your EA models so that other people can understand them
Learn MoreChoosing Your UML Subset
27 July 2020
Narrowing down the modelling ideas in your Enterprise Architect model to make consistent, understandable models.
Learn MoreWebinar: Using Interactive Documents to Collate Sparx EA Model Feedback
17 July 2020
A webinar from the EA Global Summit 2020.
Learn MoreWebinar: How to successfully scale up your Enterprise Architect team
30 June 2020
A webinar from the EA Global Summit 2020.
Learn MoreNavigating Models: Enterprise Architect Help and Techniques
16 April 2020
EA Model Curation Techniques #2 - Making models easy to navigate.
Learn MoreValidation: Improving your Enterprise Architecture Model Structure
16 April 2020
EA Model Curation Techniques #3 - Validating your model
Learn MoreExplaining the General with a Specific
16 April 2020
Explaining ideas using Object diagrams
Learn MoreDifferent 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 MoreColor 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 MoreModel Curation
6 March 2018
How cleaning, navigating and validating your EA model makes sharing and collaborating much more effective.
Learn MoreContext - 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 MoreGlossary
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 MoreHard and Soft
11 October 2017
No, not about Brexit… More about styles of Business Analyst.
Learn MorePrinting connectors
18 October 2016
Creating documents that start with the connections between the things in your model
Learn MoreUsing 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