<?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: Actor Hierarchies And Then Some</title>
	<atom:link href="http://tynerblain.com/blog/2006/12/13/actor-hierarchies/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/12/13/actor-hierarchies/</link>
	<description>Software product success.</description>
	<lastBuildDate>Tue, 22 May 2012 20:46:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: David Locke</title>
		<link>http://tynerblain.com/blog/2006/12/13/actor-hierarchies/comment-page-1/#comment-475780</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Tue, 03 Feb 2009 03:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/12/13/actor-hierarchies/#comment-475780</guid>
		<description>In diagramming your actor heirarchy, something got lost. The casual driver is a buyer in a consumer market, as in B2C. The professional driver is a buyer in a vertical, or possibly horizontal business market, as in B2B. 

In the B2B situation there would be a proliferation of stakeholders. The professional drivers are also members of a domain-specific functional culture. This culture provides meaning similar to an ideology in its exclusiveness. That meaning is typically lost in the averaging of the requirements elicitation (RE), because RE is carried out from the perspective of the technologist, not the subculture participants. The way we are trained to do RE contributes to the problem. Mathematics and economics are inherently insensitive to culture. 

The professional driver deals with a logistics network that the casual driver has no awareness of. In that logistics network are &quot;functionality opportunities.&quot; Likewise, the management of professional drivers.</description>
		<content:encoded><![CDATA[<p>In diagramming your actor heirarchy, something got lost. The casual driver is a buyer in a consumer market, as in B2C. The professional driver is a buyer in a vertical, or possibly horizontal business market, as in B2B. </p>
<p>In the B2B situation there would be a proliferation of stakeholders. The professional drivers are also members of a domain-specific functional culture. This culture provides meaning similar to an ideology in its exclusiveness. That meaning is typically lost in the averaging of the requirements elicitation (RE), because RE is carried out from the perspective of the technologist, not the subculture participants. The way we are trained to do RE contributes to the problem. Mathematics and economics are inherently insensitive to culture. </p>
<p>The professional driver deals with a logistics network that the casual driver has no awareness of. In that logistics network are &#8220;functionality opportunities.&#8221; Likewise, the management of professional drivers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

