<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Talking Architects with Len Bass</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/mattdeacon/Talking-Architects-with-Len-Bass/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/502665_100x75.jpg</url>
		<title>Channel 9 - Talking Architects with Len Bass</title>
		<link></link>
	</image>
	<description>Quality Attributes (Non-functional requirements) as first class citizens of a project? Too far fetched?

Len Bass, co-author of 
Software Architecture in Practice and&amp;nbsp;longstanding member&amp;nbsp;of the Software Engineering Institute (SEI), thinks he has an answer.
But how does this fit in an agile world? </description>
	<link></link>
	<language>en</language>
	<pubDate>Sun, 19 May 2013 06:29:08 GMT</pubDate>
	<lastBuildDate>Sun, 19 May 2013 06:29:08 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Talking Architects with Len Bass</title>
		<description>
			<![CDATA[
<p>Learning to express NFR's in a form which is useful to the project is a good thing. However, the software domain is hard to measure - when did you last see a set of performance figures for a third party library, a protocol or a comms. channel ? That is,
 actual numbers and real world data which allow you to make &quot;on the project&quot; decisions ? So ! - knowing the behaviour of one component is very tricky, build a full stack for a complex application and it gets real difficult. So - rank those use cases, get early
 code delivery on a high risk use case, then spend HOWEVER MUCH TIME IT TAKES getting that use case to comply with the NFR's as best you can. Realising the remaining use cases is a piece of cake...?</p>
<p>posted by jwwjnr</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/mattdeacon/Talking-Architects-with-Len-Bass#c633926813840000000</link>
		<pubDate>Sun, 01 Nov 2009 14:09:44 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/mattdeacon/Talking-Architects-with-Len-Bass#c633926813840000000</guid>
		<dc:creator>jwwjnr</dc:creator>
	</item>
</channel>
</rss>