<?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 terminology</title> <atom:link href="http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/feed/" rel="self" type="application/rss+xml" /><link>http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/</link> <description>Weblog of Eva, Bas, Koen and Stijn van Gils</description> <lastBuildDate>Sun, 21 Aug 2011 22:04:41 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.2.1</generator> <item><title>By: Roger L. Cauvin</title><link>http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/comment-page-1/#comment-10792</link> <dc:creator>Roger L. Cauvin</dc:creator> <pubDate>Mon, 15 Jan 2007 14:52:11 +0000</pubDate> <guid isPermaLink="false">http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/#comment-10792</guid> <description>very nice; I like the approach.  I&#039;d like to see how you flesh out the diagram with more detail about how use cases and requirements relate, and how nonfunctional requirements fit in.</description> <content:encoded><![CDATA[<p>very nice; I like the approach.  I&#8217;d like to see how you flesh out the diagram with more detail about how use cases and requirements relate, and how nonfunctional requirements fit in.</p> ]]></content:encoded> </item> <item><title>By: Bas</title><link>http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/comment-page-1/#comment-10220</link> <dc:creator>Bas</dc:creator> <pubDate>Thu, 04 Jan 2007 15:46:02 +0000</pubDate> <guid isPermaLink="false">http://van-gils.org/wordpress/index.php/2006/12/26/requirements-terminology/#comment-10220</guid> <description>I forgot to mention in the above text that this model does &lt;em&gt;not&lt;/em&gt; include non-functional requirements. The point is that NF&#039;s can not be mapped (directly) onto features. Including NF&#039;s in the model would thus mean that the mandatory role contstraint on the fact type &quot;Requirement stems from Feature&quot; should be removedl.</description> <content:encoded><![CDATA[<p>I forgot to mention in the above text that this model does <em>not</em> include non-functional requirements. The point is that NF&#8217;s can not be mapped (directly) onto features. Including NF&#8217;s in the model would thus mean that the mandatory role contstraint on the fact type &#8220;Requirement stems from Feature&#8221; should be removedl.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached
Page Caching using memcached (request URI is rejected)
Database Caching 1/9 queries in 0.000 seconds using memcached

Served from: van-gils.org @ 2012-02-08 08:41:41 -->
