<?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: Writing a functional specification</title>
	<atom:link href="http://www.fusioncube.net/index.php/writing-a-functional-specification/feed" rel="self" type="application/rss+xml" />
	<link>http://www.fusioncube.net/index.php/writing-a-functional-specification</link>
	<description>The online journey of a technophile, by Steve Brownlee</description>
	<lastBuildDate>Mon, 30 Jan 2012 21:28:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Steve Brownlee</title>
		<link>http://www.fusioncube.net/index.php/writing-a-functional-specification/comment-page-1#comment-32801</link>
		<dc:creator>Steve Brownlee</dc:creator>
		<pubDate>Tue, 30 Dec 2008 18:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.fusioncube.net/?p=269#comment-32801</guid>
		<description>That&#039;s a great link, Tony, thanks.  As for next steps, usually a technical spec is created that&#039;s used by the development and architecture folks to get started.  It will include things like conceptual database models, use case diagrams, essential code components (with unit testing information), and in some cases UML diagrams if there are tricky processes to the project.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great link, Tony, thanks.  As for next steps, usually a technical spec is created that&#8217;s used by the development and architecture folks to get started.  It will include things like conceptual database models, use case diagrams, essential code components (with unit testing information), and in some cases UML diagrams if there are tricky processes to the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Brandner</title>
		<link>http://www.fusioncube.net/index.php/writing-a-functional-specification/comment-page-1#comment-32799</link>
		<dc:creator>Tony Brandner</dc:creator>
		<pubDate>Tue, 30 Dec 2008 18:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.fusioncube.net/?p=269#comment-32799</guid>
		<description>Great post Steve, and helpful links. I definitely agree with the structure you put forth.

I found this page that breaks down some of the acronyms related to project documentation, kinda handy:
http://michael.hightechproductmanagement.com/2006/08/requirements_document_alphabet_1.html

I&#039;m curious - after the functional specs are written and approved, what do you do next? Does your next phase include documentation preparing for unit or scenario testing before development starts?

Tony</description>
		<content:encoded><![CDATA[<p>Great post Steve, and helpful links. I definitely agree with the structure you put forth.</p>
<p>I found this page that breaks down some of the acronyms related to project documentation, kinda handy:<br />
<a href="http://michael.hightechproductmanagement.com/2006/08/requirements_document_alphabet_1.html" rel="nofollow">http://michael.hightechproductmanagement.com/2006/08/requirements_document_alphabet_1.html</a></p>
<p>I&#8217;m curious &#8211; after the functional specs are written and approved, what do you do next? Does your next phase include documentation preparing for unit or scenario testing before development starts?</p>
<p>Tony</p>
]]></content:encoded>
	</item>
</channel>
</rss>

