<?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: Searching for Artifacts</title>
	<atom:link href="http://www.xengineering.com/articles/searching-for-artifacts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xengineering.com/articles/searching-for-artifacts/</link>
	<description>the art and science of software engineering</description>
	<lastBuildDate>Wed, 07 Oct 2009 21:23:48 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tristan</title>
		<link>http://www.xengineering.com/articles/searching-for-artifacts/comment-page-1/#comment-1635</link>
		<dc:creator>Tristan</dc:creator>
		<pubDate>Wed, 07 Oct 2009 21:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.xengineering.com/?p=10#comment-1635</guid>
		<description>(Likes)

I started doing my own design and development projects this year. Since I had the freedom and time (after all I was the only one setting the expectations on how long it would take to bring the deliverables), I decided to make myself go through as rigorous a process of collecting and validating requirements as possible, and then actually designing the system - including trying to write complete specifications before doing any coding whatsoever. This helped me a lot - I think - in getting it right the first time around. Furthermore, the design documents served a useful purpose in helping me to understand the system after I had finished coding it. This was true even right away when I wanted to create some user documentation.</description>
		<content:encoded><![CDATA[<p>(Likes)</p>
<p>I started doing my own design and development projects this year. Since I had the freedom and time (after all I was the only one setting the expectations on how long it would take to bring the deliverables), I decided to make myself go through as rigorous a process of collecting and validating requirements as possible, and then actually designing the system &#8211; including trying to write complete specifications before doing any coding whatsoever. This helped me a lot &#8211; I think &#8211; in getting it right the first time around. Furthermore, the design documents served a useful purpose in helping me to understand the system after I had finished coding it. This was true even right away when I wanted to create some user documentation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
