<?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: UML &#8211; Difference between Includes, Uses and Extends</title>
	<atom:link href="http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/</link>
	<description>For Smart Programmers</description>
	<lastBuildDate>Sun, 18 Jul 2010 15:38:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/comment-page-1/#comment-17</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 12 Sep 2007 16:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/#comment-17</guid>
		<description>Thank you for pointing that out !</description>
		<content:encoded><![CDATA[<p>Thank you for pointing that out !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ermin8</title>
		<link>http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/comment-page-1/#comment-16</link>
		<dc:creator>ermin8</dc:creator>
		<pubDate>Wed, 12 Sep 2007 09:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sharpprogrammer.com/uml/uml-difference-between-includes-uses-and-extends/#comment-16</guid>
		<description>Your statement: &#039;Saying “A includes B” implies that A is a higher level goal than B, A names B as a step, and B does not name A (ordinary subroutine call semantics).&#039; is probably the biggest mistake I see when using use cases. This leads to *very* poor use case modeling. 
To quote the standard: &quot;The include relationship is intended to be used when there are common parts of the behavior of two or more use cases.&quot;. Include is *not* about decomposition of goals, but about commonality. Decomposition is far more complex. I recommend looking at &quot;Intent Specifications: An Approach to Building Human-Centered Specifications&quot;  by Nancy Leveson found at http://sunnyday.mit.edu/papers.html
an d of course Cockburn&#039;s work.</description>
		<content:encoded><![CDATA[<p>Your statement: &#8216;Saying “A includes B” implies that A is a higher level goal than B, A names B as a step, and B does not name A (ordinary subroutine call semantics).&#8217; is probably the biggest mistake I see when using use cases. This leads to *very* poor use case modeling.<br />
To quote the standard: &#8220;The include relationship is intended to be used when there are common parts of the behavior of two or more use cases.&#8221;. Include is *not* about decomposition of goals, but about commonality. Decomposition is far more complex. I recommend looking at &#8220;Intent Specifications: An Approach to Building Human-Centered Specifications&#8221;  by Nancy Leveson found at <a href="http://sunnyday.mit.edu/papers.html" rel="nofollow">http://sunnyday.mit.edu/papers.html</a><br />
an d of course Cockburn&#8217;s work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
