<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Requirements are tools not weapons</title><link>http://blogs.msdn.com/b/stephen_cohen/archive/2009/11/29/requirements-are-tools-not-weapons.aspx</link><description>Consider these requirements; · The system shall properly calculate the taxes due at the time of payment. · The system shall properly display the location and speed of inbound projectiles. · All users will only be able to change data appropriate to their</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Requirements are tools not weapons</title><link>http://blogs.msdn.com/b/stephen_cohen/archive/2009/11/29/requirements-are-tools-not-weapons.aspx#9931235</link><pubDate>Wed, 02 Dec 2009 03:58:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9931235</guid><dc:creator>intelligentform</dc:creator><description>&lt;p&gt;We agree, Requirements are the Achilles heel of software development - with emphasis on narrative requirements. They cannot be tested or shown to be consistent, complete, or correct. Any requirement described in colloquial English is itself a significant analysis problem, expanding the problem domain, not solving it (as one of our customers said describing a 267 page narrative - 'it is an analysis problem not a solution!'). &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9931235" width="1" height="1"&gt;</description></item></channel></rss>