<?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: Use Case Basics: Distinguishing Between Exception and Alternative Paths</title>
	<atom:link href="http://practicalanalyst.com/2008/12/16/use-case-basics-distinguishing-between-exception-and-alternative-paths/feed/" rel="self" type="application/rss+xml" />
	<link>http://practicalanalyst.com/2008/12/16/use-case-basics-distinguishing-between-exception-and-alternative-paths/</link>
	<description>Practical Insight for Business Analysts and Project Professionals</description>
	<lastBuildDate>Thu, 22 Jul 2010 11:35:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Matt Terski</title>
		<link>http://practicalanalyst.com/2008/12/16/use-case-basics-distinguishing-between-exception-and-alternative-paths/comment-page-1/#comment-4809</link>
		<dc:creator>Matt Terski</dc:creator>
		<pubDate>Wed, 31 Dec 2008 17:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanbabcock.com/?p=271#comment-4809</guid>
		<description>Interesting. I&#039;d stopped making this distinction a long time ago and just grouped both exception and alternative paths together. When I read your post, my first reaction was: Why would I do this? What&#039;s the value? 
 
Since then, someone pointed out that you could probably ship a system *without* all of the alternate paths in place. But, it&#039;s probably *not* a good idea to ship a system that doesn&#039;t handle the exception paths. 
 
Is this the primary reason for making the distinction? Are there others? </description>
		<content:encoded><![CDATA[<p>Interesting. I&#039;d stopped making this distinction a long time ago and just grouped both exception and alternative paths together. When I read your post, my first reaction was: Why would I do this? What&#039;s the value? </p>
<p>Since then, someone pointed out that you could probably ship a system *without* all of the alternate paths in place. But, it&#039;s probably *not* a good idea to ship a system that doesn&#039;t handle the exception paths. </p>
<p>Is this the primary reason for making the distinction? Are there others?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
