Common Domain Specific Language

Last two days in my work place was spent only for discussions . It raised one thoguht in my mind, : If the business requirements are not clear, complex, and if both business anlalists and designers /developers struggle to fix "things"(requirements that not clear enough to express in any language!...) related to domain/business areas, what are the best possible ways in which an agile team can overcome these ?

1. Can we (Techies) all talk UbiquitousLanguage ?
2. How much effecient it is in specific domain areas? It it really amtured enough?

Let me put it for you in a better terms (Expert way)

Problem:

A project faces serious problems when its language is fractured. Domain experts use their jargon while technical team members have their own language tuned for discussing the domain in terms of design.The terminology of day-to-day discussions is disconnected from the terminology embedded in the code (ultimately the most important product of the software project). And even the same person uses different language in speech and in writing, so that the most incisive impression of the domain often emerges in a transient form that is never captured in the code or even in writing.Translation blunts communication and makes knowledge crunching anemic.Yet none of these dialects can be a common language because none serves all needs.

Solution:

Use the model as a backbone of a language. Commit the team to exercising that language relentlessly in all communication within the team and in the code. Use the same language in diagrams, writing and especially speech.Iron out difficulties by experimenting with alternative expressions, which reflect alternative models. Then refactor the code, renaming classes, methods and modules to conform to the new model. Resolve confusion over terms in conversaion, in just the way we come to agree on the meaning of ordinary words.