<?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: Where we are coming from &#8211; Part I</title>
	<atom:link href="http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/feed/" rel="self" type="application/rss+xml" />
	<link>http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/</link>
	<description>We have one obsession: stopping people from writing so much code</description>
	<lastBuildDate>Sun, 18 Mar 2012 21:29:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: abstratt: news from the front &#187; Model-driven Development with Executable UML models</title>
		<link>http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/comment-page-1/#comment-1570</link>
		<dc:creator>abstratt: news from the front &#187; Model-driven Development with Executable UML models</dc:creator>
		<pubDate>Mon, 07 Feb 2011 01:52:42 +0000</pubDate>
		<guid isPermaLink="false">http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-1570</guid>
		<description>[...] are two dominant dimensions in enterprise software: business domain concerns and technological [...]</description>
		<content:encoded><![CDATA[<p>[...] are two dominant dimensions in enterprise software: business domain concerns and technological [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where we are coming from - Part II &#124; abstratt: news from the front</title>
		<link>http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/comment-page-1/#comment-572</link>
		<dc:creator>Where we are coming from - Part II &#124; abstratt: news from the front</dc:creator>
		<pubDate>Mon, 24 Nov 2008 07:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-572</guid>
		<description>[...] development industry, and how we plan to fix it. If you haven&#8217;t done it yet, read the first post [...]</description>
		<content:encoded><![CDATA[<p>[...] development industry, and how we plan to fix it. If you haven&#8217;t done it yet, read the first post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where we are coming from - Part III &#124; abstratt: news from the front</title>
		<link>http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/comment-page-1/#comment-571</link>
		<dc:creator>Where we are coming from - Part III &#124; abstratt: news from the front</dc:creator>
		<pubDate>Mon, 24 Nov 2008 07:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-571</guid>
		<description>[...] posts. In summary, we should strive for addressing concerns as independently as possible (points #1 and #2), and that depending on the dimension (point #3) the concern lives in we should deploy the [...]</description>
		<content:encoded><![CDATA[<p>[...] posts. In summary, we should strive for addressing concerns as independently as possible (points #1 and #2), and that depending on the dimension (point #3) the concern lives in we should deploy the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Platform independence in MDA &#124; abstratt: news from the front</title>
		<link>http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/comment-page-1/#comment-569</link>
		<dc:creator>Platform independence in MDA &#124; abstratt: news from the front</dc:creator>
		<pubDate>Mon, 24 Nov 2008 07:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-569</guid>
		<description>[...] MDA promotes platform-independence by adopting a design-centric approach. Models are removed from implementation related concerns and thus are inherently platform independent: a single design can be reused for building the same system for multiple target platforms. The implementation details are taken care of by target platform specific templates. The templates are applied to the user models then generating concrete platform-specific artifacts (running code, documentation, database schema, configuration files). Differently from Java (even if Martin Fowler says so), MDA does not promote another platform. What it does is to promote a clear separation between problem domain concerns and implementation concerns (as covered before here in the inaugural series entitled &#8220;Where we are coming from&#8220;). [...]</description>
		<content:encoded><![CDATA[<p>[...] MDA promotes platform-independence by adopting a design-centric approach. Models are removed from implementation related concerns and thus are inherently platform independent: a single design can be reused for building the same system for multiple target platforms. The implementation details are taken care of by target platform specific templates. The templates are applied to the user models then generating concrete platform-specific artifacts (running code, documentation, database schema, configuration files). Differently from Java (even if Martin Fowler says so), MDA does not promote another platform. What it does is to promote a clear separation between problem domain concerns and implementation concerns (as covered before here in the inaugural series entitled &#8220;Where we are coming from&#8220;). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

