<br><br><div class="gmail_quote">On Thu, Jun 23, 2011 at 10:15 PM, wren ng thornton <span dir="ltr"><<a href="mailto:wren@freegeek.org">wren@freegeek.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 6/23/11 1:39 AM, Arnaud Bailly wrote:<br>
> Of course, we can always say that each<br>
> system is a language of its own (rather than *has* a language...) which is<br>
> what Eric Evans coined with its "Ubiquitous language" term. But I find it<br>
> difficult to connect that particular dots.<br>
<br>
</div>That's certainly my take on things (which I argued for at a workshop last<br>
week). Then again, I'm a linguist and type theorist, so viewing systems as<br>
languages[1] comes naturally. Do you have a link to Evans' coinage and<br>
argument?<br>
<br></blockquote><div><br>Sure. His most famous book is "Domain Driven Design" (see <a href="http://domaindrivendesign.org/about">http://domaindrivendesign.org/about</a>). Please note this is extremely "soft" and not at all mathematically founded. Ubiquitous language is one of the tools he proposes to guide software development: Use the language of the people who will use your software to define a "Core domain", a well-defined set of objects and methods that faithfully represent the business domain. <br>
<br></div></div><br>Best regards<br>Arnaud<br>