SoftONELogic Alliance Network

Ok, assume we got the project to develop the system in SoftONEAlliance Capital Investment Banking. We have a great  Java Enterprise Edition development  team: we have excellent Project Manager, experience System Analyst and ‘geek’ type of System Developer. Don’t forget we have sweet cute Software Testing girl (so if she raise the bug, the guys in development team will not angry to her  )

But, we don’t have domain expert on Investment Banking. Try and find from the client side. We need to have someone who are be able to be our reference in the development phase, person who expert in Investment Banking business process.

Ok, found it as well, now what???

We, the development team need to meet the domain expert. Let us find out all the requirements based on the domain expert explanation. But wait, can they , the domain expert, understand ‘our language’? Does the domain expert understand things like how we understand them? Does the development team have the same understanding like theirs?

Errr…. So?

Yes, we need to use an Ubiquitous Language.

The Ubiquitous Language in DDD is a negotiated language between the Domain Experts and the technical guys – but the rule is that the Domain Experts lead and the technical people follow. As the UL evolves, and this may take weeks or many months, the language becomes more and more refined.

This disjoint is what the concept of the Ubiquitous Language (or UL) is intended to eliminate in Domain Driven Design.

The concept is simple, that development team and the domain expert should share a common language, that both understand to mean the same things, and more importantly, that is set in business terminology, not technical terminology.

references:

Charlton, C.(2009). Domain Driven Design: Step by Step Guide