<?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: A framework on top of a framework</title>
	<atom:link href="http://www.ghost23.de/2007/12/a-framework-on-top-of-a-framework/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ghost23.de/2007/12/a-framework-on-top-of-a-framework/</link>
	<description>A blog about Flash and stuff</description>
	<lastBuildDate>Tue, 03 Jan 2012 15:20:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Hannes Stockner</title>
		<link>http://www.ghost23.de/2007/12/a-framework-on-top-of-a-framework/comment-page-1/#comment-23</link>
		<dc:creator>Hannes Stockner</dc:creator>
		<pubDate>Wed, 02 Jan 2008 20:44:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ghost23.de/blog/?p=64#comment-23</guid>
		<description>Hi Sven
Developers often concentrate all one’s effort on the technical infrastructure, learn different libraries and frameworks believing that the sole use of them makes the software better.
In my opinion a good approach for new projects would be to find an ubiquitous language between domain experts, software architects and developers to make them understand the business domain and following, to make them elaborate a rich domain model which reflects what they are talking about. So the model becomes the basic of the language used by all team members. It becomes the heart of the application as it solves domain specific problems.
This approach does not exclude the use of any frameworks. A framework such as e.g. IoC Container can support the Domain Driven Design philosophy, but the main focus should not lie on it.
This topic has been fascinating me for longer time and I would recommend the book „Domain Driven Design“ by Eric Evans.
Best regards
Hannes
</description>
		<content:encoded><![CDATA[<p>Hi Sven<br />
Developers often concentrate all one’s effort on the technical infrastructure, learn different libraries and frameworks believing that the sole use of them makes the software better.<br />
In my opinion a good approach for new projects would be to find an ubiquitous language between domain experts, software architects and developers to make them understand the business domain and following, to make them elaborate a rich domain model which reflects what they are talking about. So the model becomes the basic of the language used by all team members. It becomes the heart of the application as it solves domain specific problems.<br />
This approach does not exclude the use of any frameworks. A framework such as e.g. IoC Container can support the Domain Driven Design philosophy, but the main focus should not lie on it.<br />
This topic has been fascinating me for longer time and I would recommend the book „Domain Driven Design“ by Eric Evans.<br />
Best regards<br />
Hannes</p>
]]></content:encoded>
	</item>
</channel>
</rss>

