<?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: Requirements and Software Development Process and Where Bugs Come From</title>
	<atom:link href="http://tynerblain.com/blog/2005/11/26/requirements-and-software-development-process-and-where-bugs-come-from/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2005/11/26/requirements-and-software-development-process-and-where-bugs-come-from/</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: Software testing series: Black box vs white box testing -Tyner Blain</title>
		<link>http://tynerblain.com/blog/2005/11/26/requirements-and-software-development-process-and-where-bugs-come-from/comment-page-1/#comment-146</link>
		<dc:creator>Software testing series: Black box vs white box testing -Tyner Blain</dc:creator>
		<pubDate>Wed, 25 Jan 2006 23:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2005/11/26/requirements-and-software-development-process-and-where-bugs-come-from/#comment-146</guid>
		<description>[...] Hard to catch misinterpretation of requirements. Developers read the requirements. They also design the tests. If they implement the wrong idea in the code because the requirement is ambiguous, the white box test will also check for the wrong thing. Specifically, the developers risk testing that the wrong requirement is properly implemented. [...]</description>
		<content:encoded><![CDATA[<p>[...] Hard to catch misinterpretation of requirements. Developers read the requirements. They also design the tests. If they implement the wrong idea in the code because the requirement is ambiguous, the white box test will also check for the wrong thing. Specifically, the developers risk testing that the wrong requirement is properly implemented. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
