<?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: What is the key to writing a good Use Case?</title>
	<atom:link href="http://ask.goodproductmanager.com/2008/02/04/what-is-the-key-to-writing-a-good-use-case/feed/" rel="self" type="application/rss+xml" />
	<link>http://ask.goodproductmanager.com/2008/02/04/what-is-the-key-to-writing-a-good-use-case/</link>
	<description>Your product management questions answered</description>
	<lastBuildDate>Mon, 08 Feb 2010 13:24:53 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Patrick Masi</title>
		<link>http://ask.goodproductmanager.com/2008/02/04/what-is-the-key-to-writing-a-good-use-case/comment-page-1/#comment-13</link>
		<dc:creator>Patrick Masi</dc:creator>
		<pubDate>Wed, 27 Feb 2008 20:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/2008/02/04/what-is-the-key-to-writing-a-good-use-case/#comment-13</guid>
		<description>Another decent test for a good use case is just to make sure that it avoids any language that implies specific designs.  Sentences that start with &quot;the user clicks the start button&quot; or &quot;the user selects an option from the menu&quot; are red flags - instead of defining the business requirements, you are dictating the design.

We like to say that a good use case should be accurate even in a world without computers - this way, you are sure that the business process is driving the software solution, not the other way around.</description>
		<content:encoded><![CDATA[<p>Another decent test for a good use case is just to make sure that it avoids any language that implies specific designs.  Sentences that start with &#8220;the user clicks the start button&#8221; or &#8220;the user selects an option from the menu&#8221; are red flags &#8211; instead of defining the business requirements, you are dictating the design.</p>
<p>We like to say that a good use case should be accurate even in a world without computers &#8211; this way, you are sure that the business process is driving the software solution, not the other way around.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
