<?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: Data Flow Diagram for Services Example</title>
	<atom:link href="http://www.designdecomposition.com/blog/?feed=rss2&#038;p=14" rel="self" type="application/rss+xml" />
	<link>http://www.designdecomposition.com/blog/?p=14</link>
	<description>Better decomposition means better design</description>
	<lastBuildDate>Sat, 19 Jun 2010 06:49:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Baldylocks</title>
		<link>http://www.designdecomposition.com/blog/?p=14&#038;cpage=1#comment-5295</link>
		<dc:creator>Baldylocks</dc:creator>
		<pubDate>Sat, 19 Jun 2010 06:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.designdecomposition.com/blog/?p=14#comment-5295</guid>
		<description>Nice little app you have here. Very useful for looking at data flow from a different perspective...much more organized than what I&#039;m used to...Thank you very much!</description>
		<content:encoded><![CDATA[<p>Nice little app you have here. Very useful for looking at data flow from a different perspective&#8230;much more organized than what I&#8217;m used to&#8230;Thank you very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Barry</title>
		<link>http://www.designdecomposition.com/blog/?p=14&#038;cpage=1#comment-2066</link>
		<dc:creator>Doug Barry</dc:creator>
		<pubDate>Wed, 03 Jun 2009 20:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.designdecomposition.com/blog/?p=14#comment-2066</guid>
		<description>This example is intended to show how a data flow diagram generated using the decomposition matrix can help determine the appropriate decomposition of services for a service-oriented architecture. Some of the external entities/databases are the legacy systems mentioned as the inputs near the beginning of the original blog entry. Other external entities related to the outputs. I only showed some generic examples since they would vary based the needs of the particular business. My intent was to show enough of the possible outputs to create a useful example.</description>
		<content:encoded><![CDATA[<p>This example is intended to show how a data flow diagram generated using the decomposition matrix can help determine the appropriate decomposition of services for a service-oriented architecture. Some of the external entities/databases are the legacy systems mentioned as the inputs near the beginning of the original blog entry. Other external entities related to the outputs. I only showed some generic examples since they would vary based the needs of the particular business. My intent was to show enough of the possible outputs to create a useful example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Muzammil</title>
		<link>http://www.designdecomposition.com/blog/?p=14&#038;cpage=1#comment-2053</link>
		<dc:creator>Muzammil</dc:creator>
		<pubDate>Wed, 03 Jun 2009 06:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.designdecomposition.com/blog/?p=14#comment-2053</guid>
		<description>Bit confusing. Nothing like exteral entities was discussed and the electronic databases was also discussed.</description>
		<content:encoded><![CDATA[<p>Bit confusing. Nothing like exteral entities was discussed and the electronic databases was also discussed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kamran</title>
		<link>http://www.designdecomposition.com/blog/?p=14&#038;cpage=1#comment-22</link>
		<dc:creator>kamran</dc:creator>
		<pubDate>Wed, 05 Nov 2008 04:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.designdecomposition.com/blog/?p=14#comment-22</guid>
		<description>tanks</description>
		<content:encoded><![CDATA[<p>tanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
