<?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: Joint Application Design &amp; Architecture Review Board</title>
	<atom:link href="http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/feed/" rel="self" type="application/rss+xml" />
	<link>http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/</link>
	<description>The Scalability Blog</description>
	<lastBuildDate>Sun, 27 Nov 2011 04:02:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Evolving Architecture And Software &#124; AKF Partners Blog</title>
		<link>http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-86</link>
		<dc:creator>Evolving Architecture And Software &#124; AKF Partners Blog</dc:creator>
		<pubDate>Mon, 05 Jul 2010 15:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-86</guid>
		<description>[...] the architecture description accurately reflects the software? By using JAD and ARB processes, which we&#8217;ve covered in detail before on this blog as well as in the book, we can help ensure that software artifacts that deviate from [...]</description>
		<content:encoded><![CDATA[<p>[...] the architecture description accurately reflects the software? By using JAD and ARB processes, which we&#8217;ve covered in detail before on this blog as well as in the book, we can help ensure that software artifacts that deviate from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: architectural services</title>
		<link>http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-85</link>
		<dc:creator>architectural services</dc:creator>
		<pubDate>Sun, 27 Jun 2010 03:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-85</guid>
		<description>It’s hard to find knowledgeable people on this topic, lot of details about each of the processes. You sound like you know what you’re talking about! Thanks</description>
		<content:encoded><![CDATA[<p>It’s hard to find knowledgeable people on this topic, lot of details about each of the processes. You sound like you know what you’re talking about! Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile Architects &#124; AKF Partners Blog</title>
		<link>http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-84</link>
		<dc:creator>Agile Architects &#124; AKF Partners Blog</dc:creator>
		<pubDate>Wed, 02 Jun 2010 19:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-84</guid>
		<description>[...] covered JAD before but as a recap, this is the process by which features are designed in a series of meetings where [...]</description>
		<content:encoded><![CDATA[<p>[...] covered JAD before but as a recap, this is the process by which features are designed in a series of meetings where [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</title>
		<link>http://akfpartners.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-83</link>
		<dc:creator>Abbott, Keeven, Fisher &#38;#038 Fortuna Consulting</dc:creator>
		<pubDate>Tue, 09 Sep 2008 02:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/07/03/joint-application-design-architecture-review-board/#comment-83</guid>
		<description>[...] Additionally, world class teams include an architectural principle addressing the need to be monitored as a criterion for release for any new functionality.  ARB is a process or meeting in which the criterion is evaluated.  Questions such as “How will we know the system is functioning properly” are asked, and a bad answer is one that sounds like “Because we log errors to a log file” whereas a good answer might be “Because we plot the rate of errors and timeliness of responses in real time and alert on statistically significant anomalies”. [...]</description>
		<content:encoded><![CDATA[<p>[...] Additionally, world class teams include an architectural principle addressing the need to be monitored as a criterion for release for any new functionality.  ARB is a process or meeting in which the criterion is evaluated.  Questions such as “How will we know the system is functioning properly” are asked, and a bad answer is one that sounds like “Because we log errors to a log file” whereas a good answer might be “Because we plot the rate of errors and timeliness of responses in real time and alert on statistically significant anomalies”. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

