<?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 Engineering Explained</title>
	<atom:link href="http://blog.deversus.com/2008/12/requirements-engineering-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/</link>
	<description>Vancouver Web and Software Development Company Blog</description>
	<lastBuildDate>Thu, 12 Jan 2012 19:28:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: crealotoagelt</title>
		<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/#comment-15565</link>
		<dc:creator>crealotoagelt</dc:creator>
		<pubDate>Mon, 21 Feb 2011 17:20:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.deversus.com/?p=24#comment-15565</guid>
		<description>hi, new to the site, thanks.</description>
		<content:encoded><![CDATA[<p>hi, new to the site, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: empanddiepe</title>
		<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/#comment-15046</link>
		<dc:creator>empanddiepe</dc:creator>
		<pubDate>Sun, 09 Jan 2011 09:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.deversus.com/?p=24#comment-15046</guid>
		<description>thanks</description>
		<content:encoded><![CDATA[<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/#comment-267</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 11 Feb 2009 18:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.deversus.com/?p=24#comment-267</guid>
		<description>Hi Kevin, thanks for the comments. I definitely agree with you in that change is inevitable; we subscribe to an agile development methodology and as such are constantly refining our Requirements Engineering findings during project development. In the first conclusion paragraph, I touch on the fact that it is overly optimistic to believe that everything necessary will be uncovered during the first phase, and that things will not change during development. 

Thanks again!</description>
		<content:encoded><![CDATA[<p>Hi Kevin, thanks for the comments. I definitely agree with you in that change is inevitable; we subscribe to an agile development methodology and as such are constantly refining our Requirements Engineering findings during project development. In the first conclusion paragraph, I touch on the fact that it is overly optimistic to believe that everything necessary will be uncovered during the first phase, and that things will not change during development. </p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Godden</title>
		<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/#comment-265</link>
		<dc:creator>Kevin Godden</dc:creator>
		<pubDate>Wed, 11 Feb 2009 18:05:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.deversus.com/?p=24#comment-265</guid>
		<description>Hi, that&#039;s a nice outline of requirements engineering.  One thing that often catches people out though is that they expect that once the project requirements have been gathered and analysed, they will politely stay static and won&#039;t change throughout the project.  This rarely turns out to be the case, and so a successful software engineering process is often one that can handle changes to the project requirements.  Expect change!

PS Your blog&#039;s captcha is very difficult to figure out!</description>
		<content:encoded><![CDATA[<p>Hi, that&#8217;s a nice outline of requirements engineering.  One thing that often catches people out though is that they expect that once the project requirements have been gathered and analysed, they will politely stay static and won&#8217;t change throughout the project.  This rarely turns out to be the case, and so a successful software engineering process is often one that can handle changes to the project requirements.  Expect change!</p>
<p>PS Your blog&#8217;s captcha is very difficult to figure out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linear Actuators</title>
		<link>http://blog.deversus.com/2008/12/requirements-engineering-explained/#comment-102</link>
		<dc:creator>Linear Actuators</dc:creator>
		<pubDate>Wed, 21 Jan 2009 06:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.deversus.com/?p=24#comment-102</guid>
		<description>Great post!</description>
		<content:encoded><![CDATA[<p>Great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

