As much as I enjoy some of the other answers and love Scott Adam's work, I'd like to offer a bit of a serious take on the OP's question (what sort of alternate reality did I enter that I'm going to try to be serious one?).
First of all, business analysts are people too :) And like all people, people in a technical trade develop jargon - often what seems like a complete vocabulary stuffed full of specialized words, phrases, and non-standard usages. Sometimes it reaches a point where it's like they are speaking a completely different language - the Math Stack Exchange site is great for this. I love reading it sometimes, because it is so often written in pure Mathlish (Mathon?) that I retreat to English Language Learners to make sure I still know English. It's humbling.
Being a developer, this has likely become so second-nature that you know longer realize how weird your usages of some words are to people outside your peer group. As an example, someone outside of design will almost never refer to anything as an "interface" (they access or use, they don't interact with an interface ever), they don't "develop" anything other than maybe real estate (they "come up with" or "think about" a plan, maybe). People read words, not "text", "iterating" would be something you might need to see a doctor for, and it's polite to keep your hands to yourself and do your grepping in private.
Because of this, we can apply some general linguistic knowledge to business analysts. Like anyone else, people who are unsure of themselves and lacking in confidence often use excessive verbiage and invoke overly complex concepts to attempt to establish themselves as knowledgeable, powerful, or high in status; this works only when the other person has considerably less awareness, status, or knowledge, as people who know their stuff and don't need to bluster know that we don't need to have a to "colocate cross-disciplinary knowledge centers and synchronize strategic objectives" instead of "have a meeting"; they know that's crap and they take it as a sign of being a - to use different lingo - total n00b.
There are actually academic studies of professors that show that professors are not, in fact, snowed by random lingo - and that in grading papers and reviewing presentations if a person is spouting BS lingo in the professors area of knowledge they will judge them far more harshly than simpler (and equally wrong) wording. It's just a matter of skills and experience in the field - some people do actually know what they are doing.
And with business analysts, some actually do know what they are doing and choose their words carefully. All of the 'real' jargon has actual meaning, and each word often has a long and specific history that causes it to be the best word for the task at hand. "Developing and implementing strategic objectives to maximize balanced scorecard results for all stakeholders" may sound like nonsense, but the words do have very specific meanings, and a person with experience in the field can immediately tell if you are using any of them incorrectly or are trying to blow smoke at them.
Amongst those who know what they are doing, many business analysts have training in not just business, but psychology, philosophy, communications, linguistics, and some of the more traveled speak multiple languages as well. So to speak with them, I suggest taking a page from their playbook - "ask".
In training a business analyst, much of the work is about asking questions. It is their job to ask, ask, ask, and ask again - but to always record the answers and never need to ask the same question twice. They build models, and then they compare them to reality, often in technical areas they don't understand at a low level and so must rely on higher level descriptions and abstractions. This means they understand the value of a good question, and one who is comfortable with you might be happy to explain all you want to know about what a "vision statement" is and why it's important, and why "strategic alignment" is a real thing, and they'd probably be happy to deal with questions about something they actually know a lot about!
If you just want to learn to use words in a weird and kind of useless way, that's both fun and amusing, and no one does it better than Scott Adams! If you want to learn something new and want to learn to "talk the talk" and not make yourself look a freshly minted BS In Business graduate, I'd suggest some introductory text in business management and analysis, or better yet to "do lunch" with some of your company business analysts and find out about what they really do for a living.