When to stop writing use case scenarios
Knowing when to step back makes for better Business Analysts
I was recently teaching a new BA, helping her to analyse an existing system, prior to it being upgraded.
I taught her how to write use cases and create a domain model. A good starter-set of BA tools for a newbie.
Later in the week, she came to me having struggled for several hours to write a use case for a tricky bit of the user experience. It was a highly modal bit of UI, with the behavior being different for each of several types of user, and also changed based on the state of the users account. She’d done a few use cases, but they all had lots of if/then/else ideas in them, and none gave a good picture of what was required. And neither of us could figure out if we’d missed anything, and that’s a BIG problem.
- After all, the ‘Analysis’ part of the BA job title makes us look for ‘gaps, overlaps and inconsistencies‘, and we couldn’t be sure of seeing any at all.
I decided to create a state model for the user and their account. Sure enough, ten minutes thinking about the account states, and how they linked together, had us spotting the error – a missing Use Case, and another variable in the account domain class.
But I was surprised by her next question: how did you know to stop writing use cases and draw a state diagram?
[thinks]
Because I’ve been doing this for 15 years, and I know that if I’m going round in circles with one technique, and not learning anything, then it probably means I’m using the wrong technique.
So I stop. Look at the problem, and think which technique to use next. And with experience, I probably get it right second time. Or third maybe. Either way, change of technique nearly always delivers new insights.
All of which made me think about how I would differentiate between an OK BA and a good one.
- An OK one would continue doing use cases, because they have been taught to write use cases, and told to write use cases by someone higher up.
- A good one would spot they weren’t making progress, and switch.
- A great BA would get it right first time, and save lots of effort.
The good news is that this can be taught – you don’t need 15 years experience to get good. When you find yourself at a standstill,
- consciously step back and examine your set of BA techniques,
- think about why the current one isn’t working, and which other might work better.
- make a note somewhere of the characteristics which lead to your decision. With time, you’ll improve.
But the most important thing is to continuously add to your set of techniques. At first your list will grow quickly, but its never complete: there are always more to learn.
And as you learn new ones, try to also learn when it’s time to stop using them.
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 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 MoreUML Business Analyst Solutions
14 August 2020
Using UML to resolve inconsistencies, gaps and overlaps.
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