<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: nothing but &#8220;uses&#8221; and &#8220;implements&#8221;</title>
	<atom:link href="http://silkandspinach.net/2006/11/11/nothing-but-uses-and-implements/feed/" rel="self" type="application/rss+xml" />
	<link>http://silkandspinach.net/2006/11/11/nothing-but-uses-and-implements/</link>
	<description>development, by example</description>
	<lastBuildDate>Mon, 19 Mar 2012 12:48:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: David Drpaer</title>
		<link>http://silkandspinach.net/2006/11/11/nothing-but-uses-and-implements/#comment-218</link>
		<dc:creator><![CDATA[David Drpaer]]></dc:creator>
		<pubDate>Sun, 12 Nov 2006 10:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://silkandspinach.wordpress.com/2006/11/11/nothing-but-uses-and-implements/#comment-218</guid>
		<description><![CDATA[Over these two articles you have highlighted a real problem with UML. The richness of UML can draw people into trying to reproduce the code in a diagrammatic form. By considering who the model is for you have discovered the required level of detail and this dictates the notation you use.

For me the key is not the restriction your use of UML but your understanding of your readers needs.
]]></description>
		<content:encoded><![CDATA[<p>Over these two articles you have highlighted a real problem with UML. The richness of UML can draw people into trying to reproduce the code in a diagrammatic form. By considering who the model is for you have discovered the required level of detail and this dictates the notation you use.</p>
<p>For me the key is not the restriction your use of UML but your understanding of your readers needs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

