<?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 To Actor Mapping</title>
	<atom:link href="http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/</link>
	<description>Software product success.</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:39:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Use Case To Actor Mapping &#171; Peter Bakker&#8217;s Sketches</title>
		<link>http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/comment-page-1/#comment-409262</link>
		<dc:creator>Use Case To Actor Mapping &#171; Peter Bakker&#8217;s Sketches</dc:creator>
		<pubDate>Sun, 27 Jul 2008 09:12:28 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=685#comment-409262</guid>
		<description>[...] pm on June 11, 2008 &#124; # &#124;     Use Case To Actor Mapping &#124; Tyner Blain We know the importance of identifying the use cases that enable our business goals. We also know [...]</description>
		<content:encoded><![CDATA[<p>[...] pm on June 11, 2008 | # |     Use Case To Actor Mapping | Tyner Blain We know the importance of identifying the use cases that enable our business goals. We also know [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; &#187; Use Case To Actor Mapping Agile Cases</title>
		<link>http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/comment-page-1/#comment-387093</link>
		<dc:creator>&#187; &#187; Use Case To Actor Mapping Agile Cases</dc:creator>
		<pubDate>Wed, 11 Jun 2008 20:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=685#comment-387093</guid>
		<description>[...] Use Case To Actor Mapping &#124; Tyner Blain We know the importance of identifying the use cases that enable our business goals. We also know the value of understanding the actors that will use our products. This article shows how to demonstrate a simple but powerful view that maps the use cases to the actors. &#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Use Case To Actor Mapping | Tyner Blain We know the importance of identifying the use cases that enable our business goals. We also know the value of understanding the actors that will use our products. This article shows how to demonstrate a simple but powerful view that maps the use cases to the actors. &nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/comment-page-1/#comment-386668</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 10 Jun 2008 23:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=685#comment-386668</guid>
		<description>Hey Harry thanks for commenting on Tyner Blain!  And yes, it is.  However, and maybe this is just a matter of style, but I think the effort to maintain a table (and have it look good) is a lot lower than a UML use case diagram.  I also find that the information density of the table encourages the analysis more effectively than a UML use case diagram.

So maybe it is personal preference.</description>
		<content:encoded><![CDATA[<p>Hey Harry thanks for commenting on Tyner Blain!  And yes, it is.  However, and maybe this is just a matter of style, but I think the effort to maintain a table (and have it look good) is a lot lower than a UML use case diagram.  I also find that the information density of the table encourages the analysis more effectively than a UML use case diagram.</p>
<p>So maybe it is personal preference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://tynerblain.com/blog/2008/06/09/use-case-to-actor-mapping/comment-page-1/#comment-386565</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Tue, 10 Jun 2008 19:20:41 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/?p=685#comment-386565</guid>
		<description>Isn&#039;t the whole point of UML&#039;s Use Case Diagram to provide an overview of this mapping (and also the relationship between use cases)? If so, do we need another table?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t the whole point of UML&#8217;s Use Case Diagram to provide an overview of this mapping (and also the relationship between use cases)? If so, do we need another table?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
