Originally posted by Rakesh Chaudhary:
I think its because the language is not very trivial,but with a editor having Code Sense and Syntax Highlighting its very much possible to grasp a repo for it.
I don't think the primary problem is writing the language. The primary problem is reading it and knowing whether it actually describes what you want it to describe. Developers are trained in using these kind of languages. Heck, they probably became developers because they have a knack for using them and/or like to use them (and even they don't always get it right). Business people don't typically.
I think its practically impossible,to have daily meeting's between the Business stakeholders and the IT stakeholders for a distributed project.
Yes. That's one of the reasons why distributed projects are so much harder.
Instead of that they can have the Overview of their project by help of some visual specifications.And how great it would be if the visual specification has the business constraints embedded in it,in a form of language which is readable by all the teams.Like OCL.
I still don't think why you'd think that OCL is in fact "readable by all the teams".
Are you trying to highlight something on Model Driven Testing.
No. Just some plain and simple Acceptance Testing.
For this approach too,I think we need a language which expresses or which makes the blueprints of a System under development more precise and informative,with a capability of generating code for the Business Logic as supported by some tools having OCL support.
I'm not sure how code generation entered the picture.