<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blog of ducklink.com &#187; Software Architecture</title>
	<atom:link href="http://libg.org/tag/software-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://libg.org</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jan 2011 04:54:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Do’s on writing software design and architecture documents</title>
		<link>http://libg.org/2008/10/09/dos-on-writing-software-design-and-architecture-documents/</link>
		<comments>http://libg.org/2008/10/09/dos-on-writing-software-design-and-architecture-documents/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 05:20:58 +0000</pubDate>
		<dc:creator>Mason</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Software Architecture]]></category>

		<guid isPermaLink="false">http://libg.org/2008/10/09/dos-on-writing-software-design-and-architecture-documents/</guid>
		<description><![CDATA[&#160; · If you drone endlessly with details, you don&#8217;t see the forest from the trees. · If you don&#8217;t use multiple views, you are likely to miss important aspects of the solution · If you aren&#8217;t focused on quality attributes, then you are most likely documenting design and not architecture · And if you [...]]]></description>
			<content:encoded><![CDATA[<p>&#160;</p>
<blockquote><p>· If you drone endlessly with details, you don&#8217;t see the forest from the trees. </p>
<p>· If you don&#8217;t use multiple views, you are likely to miss important aspects of the solution </p>
<p>· If you aren&#8217;t focused on quality attributes, then you are most likely documenting design and not architecture </p>
<p>· And if you don&#8217;t explain the rationale,&#160; then the document doesn&#8217;t have a lot of added value beyond the code itself</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://libg.org/2008/10/09/dos-on-writing-software-design-and-architecture-documents/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

