<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Domain-Driven Documentation</title>
	<atom:link href="http://richarddingwall.name/2009/12/10/domain-driven-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/</link>
	<description>The adventures of a young kiwi software developer in London</description>
	<lastBuildDate>Thu, 10 May 2012 16:20:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Transitioning to Event Sourcing, part 4: track state changes &#124; Julien&#039;s blog</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-15847</link>
		<dc:creator>Transitioning to Event Sourcing, part 4: track state changes &#124; Julien&#039;s blog</dc:creator>
		<pubDate>Tue, 03 Aug 2010 17:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-15847</guid>
		<description>[...] For the formatting of domain terms: Richard Dingwall [...]</description>
		<content:encoded><![CDATA[<p>[...] For the formatting of domain terms: Richard Dingwall [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdn</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-15557</link>
		<dc:creator>jdn</dc:creator>
		<pubDate>Tue, 20 Jul 2010 18:08:34 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-15557</guid>
		<description>The synonym thing drives me nuts.  Working with a client that insists on calling the same thing by different names, semi-randomly, really hinders communication.</description>
		<content:encoded><![CDATA[<p>The synonym thing drives me nuts.  Working with a client that insists on calling the same thing by different names, semi-randomly, really hinders communication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-12911</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Sun, 14 Mar 2010 16:09:16 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-12911</guid>
		<description>Daniel: http://yuml.me</description>
		<content:encoded><![CDATA[<p>Daniel: <a href="http://yuml.me" rel="nofollow">http://yuml.me</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-12910</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 14 Mar 2010 15:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-12910</guid>
		<description>Hi,
Which tool did you use to build these above diagrams?

Thanks,
Daniel</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Which tool did you use to build these above diagrams?</p>
<p>Thanks,<br />
Daniel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-12880</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Tue, 09 Mar 2010 23:02:54 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-12880</guid>
		<description>Magesh : sure no problem, let me explain with yuml. First we created an &lt;a href=&quot;http://www.infoq.com/presentations/Making-Roles-Explicit-Udi-Dahan&quot; rel=&quot;nofollow&quot;&gt;explicit domain role&lt;/a&gt; for a real-life role played by an Employee:

&lt;img src=&quot;http://yuml.me/diagram/scruffy/class/%5B%3C%3CIRole%3E%3E%5DPlayer+-%3E1%5BEmployee%5D&quot; alt=&quot;IRole domain role&quot; /&gt;

Monitored Individual is then an instance of this role. It is played by an Employee, has a collection of required Competencies you can add/remove, and other behaviour related to recording practice of the Competencies.

&lt;img src=&quot;http://yuml.me/diagram/scruffy/class/%5B%3C%3CIRole%3E%3E%5D%5E%5BMonitoredIndividual%5D%2C%20%5BMonitoredIndividual%5DRequiredCompetencies+-*%3E%5BCompetency%5D&quot; alt=&quot;MonitoredIndividual&quot; /&gt;</description>
		<content:encoded><![CDATA[<p>Magesh : sure no problem, let me explain with yuml. First we created an <a href="http://www.infoq.com/presentations/Making-Roles-Explicit-Udi-Dahan" rel="nofollow">explicit domain role</a> for a real-life role played by an Employee:</p>
<p><img src="http://yuml.me/diagram/scruffy/class/%5B%3C%3CIRole%3E%3E%5DPlayer+-%3E1%5BEmployee%5D" alt="IRole domain role" /></p>
<p>Monitored Individual is then an instance of this role. It is played by an Employee, has a collection of required Competencies you can add/remove, and other behaviour related to recording practice of the Competencies.</p>
<p><img src="http://yuml.me/diagram/scruffy/class/%5B%3C%3CIRole%3E%3E%5D%5E%5BMonitoredIndividual%5D%2C%20%5BMonitoredIndividual%5DRequiredCompetencies+-*%3E%5BCompetency%5D" alt="MonitoredIndividual" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magesh</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-12842</link>
		<dc:creator>Magesh</dc:creator>
		<pubDate>Thu, 04 Mar 2010 13:33:59 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-12842</guid>
		<description>Hi Richard,

Thanks for all the great posts.  For someone like me who had been designing data driven applications for quite a few years and gradually making progress towards a better OO backed applications, your posts are real eye openers.

I have a small favour to ask.  I tried to model the domain you described in this post as an exercise and found it quite challenging due to inexperience.  I am really interested to learn how you modeled this one. (I am struggling with the &quot;A Monitored Individual is a role played by certain Employees. Each Monitored Individual is required to be proficient in a number of Competencies&quot; part). Would you mind sharing your design?

Thanks,
Magesh</description>
		<content:encoded><![CDATA[<p>Hi Richard,</p>
<p>Thanks for all the great posts.  For someone like me who had been designing data driven applications for quite a few years and gradually making progress towards a better OO backed applications, your posts are real eye openers.</p>
<p>I have a small favour to ask.  I tried to model the domain you described in this post as an exercise and found it quite challenging due to inexperience.  I am really interested to learn how you modeled this one. (I am struggling with the &#8220;A Monitored Individual is a role played by certain Employees. Each Monitored Individual is required to be proficient in a number of Competencies&#8221; part). Would you mind sharing your design?</p>
<p>Thanks,<br />
Magesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #496</title>
		<link>http://richarddingwall.name/2009/12/10/domain-driven-documentation/comment-page-1/#comment-11991</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #496</dc:creator>
		<pubDate>Fri, 11 Dec 2009 08:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=2603#comment-11991</guid>
		<description>[...] Domain-Driven Documentation - Richard Dingwall talks about how the expression of requirements in the Domain Driven Development (Evans) style can help you in your more general documentation to craft documentation which is clear and consistent. [...]</description>
		<content:encoded><![CDATA[<p>[...] Domain-Driven Documentation &#8211; Richard Dingwall talks about how the expression of requirements in the Domain Driven Development (Evans) style can help you in your more general documentation to craft documentation which is clear and consistent. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

