<?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: WSO2 expands ESB market with Apache Synapse-based, open source SOA offering</title>
	<atom:link href="http://www.fastforwardblog.com/2007/06/15/wso2-expands-esb-market-with-apache-synapse-based-open-source-soa-offering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2007/06/15/wso2-expands-esb-market-with-apache-synapse-based-open-source-soa-offering/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 03:02:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paula Thornton</title>
		<link>http://www.fastforwardblog.com/2007/06/15/wso2-expands-esb-market-with-apache-synapse-based-open-source-soa-offering/comment-page-1/#comment-16400</link>
		<dc:creator>Paula Thornton</dc:creator>
		<pubDate>Fri, 15 Jun 2007 21:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://fastforwardblog.com/2007/06/15/wso2-expands-esb-market-with-apache-synapse-based-open-source-soa-offering/#comment-16400</guid>
		<description>There's a reference in here to focusing on "user requirements". Again, there is a tendency to apply old mindsets to this. Therefore, I avoid alignment of 'user' and 'requirements' at all. The perspectivie of the individual is represented by design research and corresponding design artifacts (findings). "Requirements" are the instantiation of the design specification that can support testing...nothing more.

That means that someone can 'think' they're going through a process to gather and meet "user requirements" and still fail...it's the 'design research' that makes it successful.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a reference in here to focusing on &#8220;user requirements&#8221;. Again, there is a tendency to apply old mindsets to this. Therefore, I avoid alignment of &#8216;user&#8217; and &#8216;requirements&#8217; at all. The perspectivie of the individual is represented by design research and corresponding design artifacts (findings). &#8220;Requirements&#8221; are the instantiation of the design specification that can support testing&#8230;nothing more.</p>
<p>That means that someone can &#8216;think&#8217; they&#8217;re going through a process to gather and meet &#8220;user requirements&#8221; and still fail&#8230;it&#8217;s the &#8216;design research&#8217; that makes it successful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
