<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Scenario-Based Architecture Evaluation Methods</title><link>http://blogs.msdn.com/jmeier/archive/2008/09/25/scenario-based-architecture-evaluation-methods.aspx</link><description>I'm a fan of scenarios.&amp;#160; Whether you use scenarios for scenario-driven development,&amp;#160; scenario-based evaluations, competitive assessments or for shaping products ...&amp;#160; scenarios are where the rubber meets the road.&amp;#160; I think scenarios</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>