<?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: Verify Correct Requirements with Use Cases</title>
	<atom:link href="http://tynerblain.com/blog/2006/07/10/verify-correct-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/07/10/verify-correct-requirements/</link>
	<description>Software product success.</description>
	<lastBuildDate>Fri, 12 Mar 2010 01:42:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Effective Communication of Requirements &#171; LetZcommunicate</title>
		<link>http://tynerblain.com/blog/2006/07/10/verify-correct-requirements/comment-page-1/#comment-268243</link>
		<dc:creator>Effective Communication of Requirements &#171; LetZcommunicate</dc:creator>
		<pubDate>Tue, 15 Jan 2008 05:21:53 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/07/10/verify-correct-requirements/#comment-268243</guid>
		<description>[...] Interaction vs. Broadcasting. Strikingly distinctive is the difference between interaction and broadcasting. It is the difference between a community and an audience. Intuitively, you know that “throw it over the wall” is bad. Alistair’s research validates this. Determining the correctness of requirements requires interaction. You can use use cases to verify requirement correctness - but doing it without interaction is less effective. [...]</description>
		<content:encoded><![CDATA[<p>[...] Interaction vs. Broadcasting. Strikingly distinctive is the difference between interaction and broadcasting. It is the difference between a community and an audience. Intuitively, you know that “throw it over the wall” is bad. Alistair’s research validates this. Determining the correctness of requirements requires interaction. You can use use cases to verify requirement correctness &#8211; but doing it without interaction is less effective. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
