<?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: Use Cases</title>
	<atom:link href="http://nebtech.wordpress.com/2007/05/31/use-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://nebtech.wordpress.com/2007/05/31/use-cases/</link>
	<description>Delving into software development and marketing lifecycles</description>
	<lastBuildDate>Mon, 09 Mar 2009 00:49:18 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jethris</title>
		<link>http://nebtech.wordpress.com/2007/05/31/use-cases/#comment-179</link>
		<dc:creator>jethris</dc:creator>
		<pubDate>Fri, 15 Jun 2007 21:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://nebtech.wordpress.com/2007/05/31/use-cases/#comment-179</guid>
		<description>You need to flush out your use cases.  A use case is not a paragraph detailing everything an actor can do.  It is specify individual actions allowed by the system, or any number of actors.  They need to be generic enough to allow for flexibility, but specific enough that anyone could code.

For example, the use case for opening a door would look like:

Action:  Open a door
Actors:  Members of the household
Precondition:  Member has a key
Post Condition:  Door is open

Steps:
1:  Actor turns knob
2:  System opens the door

Alternative Steps:

1:  Actor turns door.
2:  Door locked, error returned to Actor
3:  Actor inserts key
4:  Actor turns key
5:  If key is correct, door unlocks
6:  Actor opens door</description>
		<content:encoded><![CDATA[<p>You need to flush out your use cases.  A use case is not a paragraph detailing everything an actor can do.  It is specify individual actions allowed by the system, or any number of actors.  They need to be generic enough to allow for flexibility, but specific enough that anyone could code.</p>
<p>For example, the use case for opening a door would look like:</p>
<p>Action:  Open a door<br />
Actors:  Members of the household<br />
Precondition:  Member has a key<br />
Post Condition:  Door is open</p>
<p>Steps:<br />
1:  Actor turns knob<br />
2:  System opens the door</p>
<p>Alternative Steps:</p>
<p>1:  Actor turns door.<br />
2:  Door locked, error returned to Actor<br />
3:  Actor inserts key<br />
4:  Actor turns key<br />
5:  If key is correct, door unlocks<br />
6:  Actor opens door</p>
]]></content:encoded>
	</item>
</channel>
</rss>
