Feeds

Disintermangling use case scenarios from requirements

Yes, it is a word...

Beginner's guide to SSL certificates

It turns out that my co-author Doug Rosenberg has a few things to say on the subject of use case style. So this week I'm going to leap in the back of the Dodge Ram pick-up truck and let him drive.

Over to Doug:

There's often a fair bit of confusion in the early stages of a software project about what exactly needs to be built, Doug says. So it's worthwhile investing some effort in getting to a point of clarity about the requirements before leaping into construction.

One of the chief points of confusion is the mangling-up of "active voice stuff" with passive voice stuff. Scenarios (or stories) are "active voice stuff", e.g. "the user clicks the cancel button and the system erases the disk".

In the UML universe, we call the active voice stuff (which describes runtime behaviour) "use case scenario text" and the passive voice stuff "functional requirements".

It's useful to separate the scenarios from the functional requirements, not least because you must understand the runtime behaviour unambiguously before you code the system - and this is much harder to do when it's "intermangled" with the functional requirements.

At ICONIX, we often work with projects that are contractually required to demonstrate compliance against a formal, written set of requirements - banking systems, aerospace/defence projects, etc, and we've run into this "intermangling" phenomenon more times than we'd like to recall.

Here's an example: Once, when I walked into a client's building to conduct a training workshop, I was handed a hefty use case document. As I flipped through the use cases, I noticed that the scenario text was interspersed with lines that started with [REQUIREMENT]. So there would be a couple of lines of active voice scenario stuff, followed by a couple of lines of [REQUIREMENT]s, and so on.

Several of these uniquely numbered [REQUIREMENT]s were repeated on multiple pages (all with unique numbers, of course). So I took a deep breath and had the following conversation:

DOUG: It looks like some of these functional requirements repeat across several use cases...

CLIENT: Oh definitely! Some of them are in there 70 or 80 times.

DOUG: Oh... (silently emits "primal scream")

DOUG: Pauses (looking calm while still screaming silently)

DOUG: And they all seem to be uniquely numbered...

CLIENT: (brightly) Yep!

DOUG: So... how do you know whether you have 320 distinct requirements, or four requirements repeated 80 times each?

CLIENT: (smiling) Don't know... never thought about that one.

DOUG: What did you say your name was?

I had recently returned from teaching another class in Texas, where they're fond of taking liberties with the English language. Thus, the word "disintermangling" was born.

I'll wrap up with this thought: Unambiguous scenario descriptions are key to understanding what you're building before you code it. But before you can disambiguate the scenarios, you need to disintermangle them from the functional requirements.

Doug Rosenberg is an author and noted OO instructor, and runs public training classes worldwide.

Choosing a cloud hosting partner with confidence

More from The Register

next story
That dreaded syncing feeling: Will Microsoft EVER fix OneDrive?
Microsoft's long history of broken Windows sync
Mozilla, EFF, Cisco back free-as-in-FREE-BEER SSL cert authority
Let’s Encrypt to give HTTPS-everywhere a boost in 2015
SLURP! Flick your TONGUE around our LOLLIPOP – Google
Android 5 is coming – IF you're lucky enough to have the right gadget
Nokia's N1 fondleslab's HIDDEN BRILLIANCE: The 'Z Launcher'
Sugarcoating Android's Lollipop makes tab easier to swallow
Bug fixes! Get your APPLE BUG FIXES! iOS and OS X updates right here!
Yosemite fixes Wi-Fi hiccup, older iOS devices get performance boost
Microsoft: Your Linux Docker containers are now OURS to command
New tool lets admins wrangle Linux apps from Windows
Facebook, working on Facebook at Work, works on Facebook. At Work
You don't want your cat or drunk pics at the office
Soz, web devs: Google snatches its Wallet off the table
Killing off web service in 3 months... but app-happy bonkers are fine
Meet Windows 10's new UI for OneDrive – also known as File Explorer
New preview build continues Redmond's retreat to the desktop
prev story

Whitepapers

Choosing cloud Backup services
Demystify how you can address your data protection needs in your small- to medium-sized business and select the best online backup service to meet your needs.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Beginner's guide to SSL certificates
De-mystify the technology involved and give you the information you need to make the best decision when considering your online security options.
New hybrid storage solutions
Tackling data challenges through emerging hybrid storage solutions that enable optimum database performance whilst managing costs and increasingly large data stores.