<?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>Product Development Blog &#187; documentation</title>
	<atom:link href="http://www.flashpointdevelopment.com/blog/index.php/tag/documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flashpointdevelopment.com/blog</link>
	<description>How to develop ideas and inventions into successful products</description>
	<lastBuildDate>Tue, 13 Jul 2010 14:15:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Specifications Documents</title>
		<link>http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/</link>
		<comments>http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/#comments</comments>
		<pubDate>Wed, 04 Jun 2008 17:12:43 +0000</pubDate>
		<dc:creator>Sam</dc:creator>
				<category><![CDATA[Consultants]]></category>
		<category><![CDATA[NPD Process]]></category>
		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://www.flashpointdevelopment.com/blog/?p=14</guid>
		<description><![CDATA[<p>Spec Docs are a way to communicate the goals of the product in a specific area.  Spec Docs need to be focused on a specific aspect of the development like electronics, design, mold and provide all the necessary information for an expert to execute that aspect of the project.  Spec Docs are often replied to [...]]]></description>
			<content:encoded><![CDATA[<p>Spec Docs are a way to communicate the goals of the product in a specific area.  Spec Docs need to be focused on a specific aspect of the development like electronics, design, mold and provide all the necessary information for an expert to execute that aspect of the project.  Spec Docs are often replied to with technical questions that need to be investigated and answered.  Eventually a spec doc will result in a commitment, a quote or a partnership.  Even when a spec doc is accepted it will change, new parts will become available, technical aspects will emerge or the environment will change etc.  It is important to update the spec doc to reflect your new findings.</p>
<p>Format of a Spec Doc</p>
<p><strong>General Description: </strong>Quick overview of the product including the T5+2 elements.</p>
<p><strong>General Specifications:</strong> Guidlines for work across several aspects of the device.</p>
<p>Might Include:</p>
<ul>
<li>Durability</li>
<li>Cost</li>
<li>Weight</li>
<li>Size</li>
<li>Use Environment</li>
</ul>
<p><strong>Specifications: </strong>(Specific Area of Product)</p>
<p>Primary Specs:  The most important elements in outline form with as much detail as you have</p>
<p>Ancilary Specs:  Lower priority elements in same form.</p>
<p>Other things that might be appropriate include:</p>
<ul>
<li>Concept Drawings</li>
<li>Schedule with task list</li>
<li>Bill of Materials</li>
</ul>
<p>These documents should be focused, don&#8217;t view this as an opportunity to show off all the work you have done in different areas.  Go into every detail you have for the specific area.</p>
<p>Unfortunately because development projects are very diverse we cannot provide a complete spec doc guide, but these are the basics that we use to build ideas.  You should insert what you feel is important given the audience.</p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Specifications+Documents+http://3hxd3.th8.us" title="Post to Twitter"><img class="nothumb" src="http://www.flashpointdevelopment.com/blog/wp-content/plugins/tweet-this/icons/tt-twitter.png" alt="Post to Twitter" border="0" /></a>&nbsp; <a class="tt" href="http://delicious.com/post?url=http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/&amp;title=Specifications+Documents" title="Post to Delicious"><img class="nothumb" src="http://www.flashpointdevelopment.com/blog/wp-content/plugins/tweet-this/icons/tt-delicious.png" alt="Post to Delicious" border="0" /></a>&nbsp; <a class="tt" href="http://digg.com/submit?url=http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/&amp;title=Specifications+Documents" title="Post to Digg"><img class="nothumb" src="http://www.flashpointdevelopment.com/blog/wp-content/plugins/tweet-this/icons/tt-digg.png" alt="Post to Digg" border="0" /></a>&nbsp; <a class="tt" href="http://www.facebook.com/share.php?u=http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/&amp;t=Specifications+Documents" title="Post to Facebook"><img class="nothumb" src="http://www.flashpointdevelopment.com/blog/wp-content/plugins/tweet-this/icons/tt-facebook.png" alt="Post to Facebook" border="0" /></a>&nbsp; <a class="tt" href="http://stumbleupon.com/submit?url=http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/&amp;title=Specifications+Documents" title="Post to StumbleUpon"><img class="nothumb" src="http://www.flashpointdevelopment.com/blog/wp-content/plugins/tweet-this/icons/tt-su.png" alt="Post to StumbleUpon" border="0" /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.flashpointdevelopment.com/blog/index.php/newproductdevelopmentprocess/specifications-documents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
