Comments on: Time Travel for Context-free Use Cases

By: Jonathan

Jonathan — Tue, 16 Feb 2010 01:00:09 +0000

Thanks, Tami, and you're right about the banks. It's interesting to contemplate how different fulfillment of services and functions we take for granted may change and how much of our lingo is tied to terms for tools and technology used for fulfillment. I'm thinking about "dialing numbers" for example.

By: Tami Bussing

Tami Bussing — Tue, 12 Jan 2010 18:21:26 +0000

Great post, Jonathan. Thank you for sharing. A process improvement person, I've seen change of hands/orgs, duties/responsibilities across the board. I might venture to suggest that one replace the word 'bank' with more generic form of provider, such as 'supplier'. In the future, 'bank' may be an investment firm. Just a thought.

By: Jennifer Banzon

Jennifer Banzon — Sat, 26 Sep 2009 05:53:53 +0000

Great advice, as always. –> "Time Travel for Context-free Use Cases : Practical Analyst" http://j.mp/1nhMKn

By: juliansammy

juliansammy — Sat, 26 Sep 2009 04:01:33 +0000

@bainsight might like this ‘timeless use case’ blog – related to his upcoming Quick Tip http://ow.ly/r7F0 #iiba #QT4BBA #baot

By: JB

JB — Sat, 26 Sep 2009 00:00:37 +0000

Thanks, Alan. Appreciate you stopping by commenting.

And you make a good point – at the rate things are changing today, it doesn’t take long for one type of UI element or “best practice” to be replaced by another.

By: Alan Maxwell

Alan Maxwell — Fri, 25 Sep 2009 01:55:35 +0000

That was a very clear and concise explanation, and I very much agree that it is good to avoid solution specific language in requirements if possible.

In these days, even in screen based UI’s like web based solutions or the ‘older’ style client applications, functionality can be triggered in a variety of ways, (e.g. via buttons, images or hyperklinks etc).

It means the time travel period is even shorter to find you have been assuming a particular solution context that needs to be changed. E.g. perhaps using ‘The user clicks on the Save button…’ instead of ‘The user triggers the option to Save…’.