Jargon gone amuck!

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.

Please Rate This Article!

(1 votes, average: 4 out of 5)

 Loading ...

This article was published on Wednesday, February 15th, 2006 at 5:57 am and is filed under Communication, Presentation, Requirements, Software requirements specification, Writing.
You can leave a comment on this post.
Trackback URL