<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Evolving Software &#187; tips</title>
	<atom:link href="http://evolving-software.co.uk/blog/tag/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://evolving-software.co.uk/blog</link>
	<description>General tidbits about Domain Driven Design and TrueView</description>
	<lastBuildDate>Tue, 06 Dec 2011 21:29:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Tips for Domain Driven Design and TrueView</title>
		<link>http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/</link>
		<comments>http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 07:27:00 +0000</pubDate>
		<dc:creator>Vijay</dc:creator>
				<category><![CDATA[TrueView tips]]></category>
		<category><![CDATA[ddd]]></category>
		<category><![CDATA[domain driven design]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://evolving-software.co.uk/blog/?p=230</guid>
		<description><![CDATA[<a href="http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/" title="Tips for Domain Driven Design and TrueView"></a>Here are some tips for DDD newbies.  It&#8217;s easy to fall back to doing &#8216;what you know best&#8217;, so use these tips to stay focused. Hopefully your design skills will get better (and faster) as a result. Don&#8217;t start with &#8230;<p class="read-more"><a href="http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/">Read more &#187;</a></p>]]></description>
			<content:encoded><![CDATA[<a href="http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/" title="Tips for Domain Driven Design and TrueView"></a><p>Here are some tips for DDD newbies.  It&#8217;s easy to fall back to doing &#8216;what you know best&#8217;, so use these tips to stay focused. Hopefully your design skills will get better (and faster) as a result. <img src='http://evolving-software.co.uk/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<ol>
<li><strong>Don&#8217;t start with the User Interface</strong><br />
Instead of asking &#8220;<em>How will the user solve this problem?</em>&#8220;, ask &#8220;<em>What is the problem?</em>&#8220;</li>
<li><strong>Design Domain Models, not database schemas</strong><br />
Most business users don&#8217;t understand database schemas &#8211; so don&#8217;t make them</li>
<li><strong>Design your Domain Model incrementally</strong><br />
Defining too much detail early on is the fastest way to get side-tracked</li>
<li><strong>Get constant feedback from your Domain Experts</strong><br />
Take advantage of TrueView’s auto-generated prototypes to get instant feedback</li>
<li><strong>Separate <em>business concerns</em> from </strong><em><strong>technical concerns</strong><br />
</em>Writing technical infrastructure code can be counter-productive during the modelling phase</li>
<li><strong>Unit testing wisely</strong><br />
Focus on testing         non-trivial behaviour and complex business logic, possibly using BDD</li>
<li><strong>Think agile, be agile</strong><br />
Your clients don&#8217;t have time to wait, so don&#8217;t make them</li>
</ol>
<p>You can read the detailed version <a href="http://evolving-software.co.uk/tips-for-domain-driven-design.html">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://evolving-software.co.uk/blog/2009/06/02/tips-for-domain-driven-design-and-trueview/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

