<?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: Your SOA product choices should be based on the QUINT model</title>
	<atom:link href="http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 20:40:47 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Erwin Bolwidt</title>
		<link>http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/comment-page-1/#comment-30891</link>
		<dc:creator>Erwin Bolwidt</dc:creator>
		<pubDate>Fri, 18 Jan 2008 14:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2008/01/16/your-soa-product-choices-should-be-based-on-the-quint-model/#comment-30891</guid>
		<description>Interesting piece, Viktor. I will definitely check out Quint2 for non-functionals.

I think you should mention that in the case you describe, a direction for the solution has already been chosen (a SOA architecture) so you don&#039;t need to go through a process of selecting the direction of the solution first.
That&#039;s very valid, &quot;The solution must consist of an off-the-shelf ESB product&quot; is a perfectly valid requirement (constraint) if it helps to satisfy the needs of a stakeholder. It also represents on externally observable aspect of the system, so even though that requirement is a &quot;design&quot; (a &#039;how&#039;), it can still be a good requirement.


Erwin</description>
		<content:encoded><![CDATA[<p>Interesting piece, Viktor. I will definitely check out Quint2 for non-functionals.</p>
<p>I think you should mention that in the case you describe, a direction for the solution has already been chosen (a SOA architecture) so you don&#8217;t need to go through a process of selecting the direction of the solution first.<br />
That&#8217;s very valid, &#8220;The solution must consist of an off-the-shelf ESB product&#8221; is a perfectly valid requirement (constraint) if it helps to satisfy the needs of a stakeholder. It also represents on externally observable aspect of the system, so even though that requirement is a &#8220;design&#8221; (a &#8216;how&#8217;), it can still be a good requirement.</p>
<p>Erwin</p>
]]></content:encoded>
	</item>
</channel>
</rss>
