This video showing the abuse of jargon (2 minutes) is absolutely hysterical, and should be watched for humor alone. However, it also drives the point home about the effects of using jargon when writing requirements.
When we write a PRD or SRS if we use the jargon of one domain, this is what we will sound like to everyone who isn’t in on it.
To avoid this mistake start with Writing requirements unambiguously.
Another related, and very funny article:
http://www.hanniganhole.co.uk/blog/2006/08/technobabble-and-social-engineering.html
Thanks Tom for sending it offline!