Feeds

Telltale signs your model is stuck

Analysis paralysis: part two

High performance access to file storage

Teams can get stuck wallowing in trivial details when modeling in UML. Sweating such details can lead to frustration and premature, and rash, decisions on using UML later in a project. But how do you know when a particular nuance is inconsequential and when it's an important item to specify?

You learn to recognize the signs of analysis paralysis - aside from the obvious one, that no progress is being made: the team is having a profound philosophical discussion around the whiteboard, and it has virtually nothing to do with the project, and virtually everything to do with splitting hairs. The line from the Gershwin classic on "tomato" versus "tom-ah-to" sums up these debates pretty well.

It's understandable that people spend ages arguing over the finer details, because most UML books describe each part of the notation with equal weight. You might see a description of dependencies between packages - not terribly important, except maybe as a high-level overview - right next to a description of relationships between classes.

One rule of thumb is: will it affect the source code that falls out of the end of the design process? If you use <<precedes>> instead of the <<invokes>> stereotype to link up your use cases, will the code - or the unit tests, or the test specs - be any different? Answer: Almost certainly not.

Similarly, modeling the dependencies between packages will have absolutely no effect whatsoever on the resultant source code. It's also debatable whether it would add any value to your documentation. However, modeling the relationships between classes definitely will affect the source code - especially if you're generating code directly from the model.

Another rule of thumb: is the distinction less about the semantics of your problem domain or design, and more about the semantics of the modeling language? If so, the distinction probably isn't an important one.

And finally: are you worrying about finer details at the wrong stage? For example, debating the multiplicity between domain objects before you've even begun to think about the design, or debating too early - when the domain model is only just emerging, all wide-eyed and blinking in its innocence, from the customer's subconscious - whether two real-world domain objects should be connected with aggregation or composition. When teams discuss this stuff too early, you end up with some deep discussions that border on philosophy and existentialism: is object A object B's keeper? If A pings out of existence, what happens to B? Is an A without its B really an A? And so on.

In the song, the tomato versus tom-ah-to impasse produces the exasperated cry of: "Let's call the whole thing off!". This is pretty much what people decide to do with UML after they have wasted time and effort getting into the not-very-important and extremely arcane aspects of modeling.

And that's a shame, because they miss out on all the useful, pragmatic aspects such as allocating behavior, eliminating ambiguity in your requirements descriptions, and identifying code "hot spots" ripe for unit and functional testing.

Analysis paralysis is an insidious beast that pounces when you have disagreements over issues that seem important and takes things off track. Keep an eye out for this creature's tell tale signs, and you'll quickly start to recognize when your project is spinning its wheels over non-issues.®

Matt Stephens has co-authored Use Case Driven Object Modeling with UML: Theory and Practice, which illustrates how to step nimbly from use cases to code while avoiding the dreaded analysis paralysis.

Combat fraud and increase customer satisfaction

More from The Register

next story
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Oh no, Joe: WinPhone users already griping over 8.1 mega-update
Hang on. Which bit of Developer Preview don't you understand?
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
Next Windows obsolescence panic is 450 days from … NOW!
The clock is ticking louder for Windows Server 2003 R2 users
Ditch the sync, paddle in the Streem: Upstart offers syncless sharing
Upload, delete and carry on sharing afterwards?
Microsoft TIER SMEAR changes app prices whether devs ask or not
Some go up, some go down, Redmond goes silent
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
prev story

Whitepapers

SANS - Survey on application security programs
In this whitepaper learn about the state of application security programs and practices of 488 surveyed respondents, and discover how mature and effective these programs are.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.