<?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: patterns &amp; practices Solution Engineering</title>
	<atom:link href="http://shapingsoftware.com/2008/09/15/patterns-practices-solution-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://shapingsoftware.com/2008/09/15/patterns-practices-solution-engineering/</link>
	<description>Patterns and Practices for Software Success.</description>
	<pubDate>Fri, 10 Sep 2010 12:47:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben Gillis</title>
		<link>http://shapingsoftware.com/2008/09/15/patterns-practices-solution-engineering/comment-page-1/#comment-50280</link>
		<dc:creator>Ben Gillis</dc:creator>
		<pubDate>Wed, 22 Apr 2009 22:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://shapingsoftware.com/2008/09/15/patterns-practices-solution-engineering/#comment-50280</guid>
		<description>&gt; one of my favorite figures

it's probably a great diagram to start with for upcoming Microsoft Oslo modeling.  The above is a tangible point many will be able to grasp to move into modeling.  

It's a good diagram to start with examples of domain-specific languages, correlating patterns to DSL keywords, correlating functional (storyboards, requirements and use cases) domain-specific languages to technical entities, etc.</description>
		<content:encoded><![CDATA[<p>&gt; one of my favorite figures</p>
<p>it&#8217;s probably a great diagram to start with for upcoming Microsoft Oslo modeling.  The above is a tangible point many will be able to grasp to move into modeling.  </p>
<p>It&#8217;s a good diagram to start with examples of domain-specific languages, correlating patterns to DSL keywords, correlating functional (storyboards, requirements and use cases) domain-specific languages to technical entities, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
