February 27, 2007

...Learn TDD with Codemanship

Bad Use Case Advice

I just wanted to draw your attention to some really bad use case advice from Matt Stephens, co-author of Use Case-driven Object Modeling with UML.

Matt confuses technical detail with clarity and abstraction with ambiguity. He argues that use cases should not be "essential", but should include details of the technical design to make them clearer.

Matt, you're just plain wrong, mate. Essential use cases can be just as testable as the ones you favour, if you choose to make them so. Indeed, writing them as executable tests - maybe even using a tool like FIT - will ensure that they are. Please don't confuse clarity with detail: they are most certainly not the same thing.

And I'm sure I don't need to warn you of the dangers of allowing use case authors to make technical design decisions, now do I?

Bad Matthew! Go to your room and think about what you've done!
Posted 13 years, 9 months ago on February 27, 2007