Recently I came across a reference to "BDD", and context indicated similarity to Test Driven Development, so I looked it up.  It is Behavior Driven Development, and the short-form description appears to be "it is TTD with different naming conventions".

http://dannorth.net/introducing-bdd/

I can definitely see how this concept (and tools to support it) can be useful.  I know how the names you use change the way you think about things, and the effects may be subtle, but subtle effects can add up.  If your organization charges different prices to members and non-members, whether you call the difference "membership discount" or "non-member surcharge" reflects and reinforces different attitudes about membership.  I used to study aikido (I was terrible at it, but I enjoyed it), and at my dojo, the person we practiced with was our "partner".  If a new person or visitor said "opponent", they were corrected - politely, but automatically.  I think it helped keep the practices safe.

I'm not going to do anything with this for a while, as I'm still getting acquainted with modern programming tools (like Eclipse) and want to continue on with what I've started for a while.  But eventually I do want to try this other toolset.