<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://mkdot.net/community/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>Software architect and his competencies</title><link>http://mkdot.net/community/mknetug/b/thearchitect/archive/2008/03/26/software-architect-and-his-competencies.aspx</link><description>&amp;quot;The software architect must be well-rounded, posses maturity, vision,
and a depth of experience that allows for grasping issues quickly and
making educated, critical judgment in the absence of complete
information.&amp;quot; 

 Role of the Software</description><dc:language>en-US</dc:language><generator>6.x Non-Production</generator></channel></rss>