<?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>Embedded Insights Channels &#187; Exploration &amp; Prototyping</title>
	<atom:link href="http://www.embeddedinsights.com/channels/channels/exploration-prototyping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embeddedinsights.com/channels</link>
	<description>Shedding Light on the Hidden World of Embedded Systems</description>
	<lastBuildDate>Fri, 14 Jun 2013 17:33:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>What should design reviews accomplish?</title>
		<link>http://www.embeddedinsights.com/channels/2011/09/07/what-should-design-reviews-accomplish/</link>
		<comments>http://www.embeddedinsights.com/channels/2011/09/07/what-should-design-reviews-accomplish/#comments</comments>
		<pubDate>Wed, 07 Sep 2011 19:40:04 +0000</pubDate>
		<dc:creator>Robert Cravotta</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Question of the Week]]></category>
		<category><![CDATA[Verification & Validation]]></category>
		<category><![CDATA[Design Review]]></category>
		<category><![CDATA[Requirements Compliance]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=628</guid>
		<description><![CDATA[I remember the lessons I learned while performing my first design review because it significantly shifted my view of what a design review is supposed to accomplish. What should be the primary accomplishment of a successful design review?]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2011/09/07/what-should-design-reviews-accomplish/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Is testing always essential?</title>
		<link>http://www.embeddedinsights.com/channels/2011/08/24/is-testing-always-essential/</link>
		<comments>http://www.embeddedinsights.com/channels/2011/08/24/is-testing-always-essential/#comments</comments>
		<pubDate>Wed, 24 Aug 2011 20:44:10 +0000</pubDate>
		<dc:creator>Robert Cravotta</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Question of the Week]]></category>
		<category><![CDATA[Simulation & Debugging]]></category>
		<category><![CDATA[Recall]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=620</guid>
		<description><![CDATA[The recent audit of the Army’s ballistic armor inserts finds that testing was performed inconsistently, or in some cases, completely skipped. While no substantial claim has been filed that shows these inserts do not perform as required, the process for assuring their quality was definitely abridged. Is all testing always essential?]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2011/08/24/is-testing-always-essential/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>How does your company handle test failures?</title>
		<link>http://www.embeddedinsights.com/channels/2011/08/17/how-does-your-company-handle-test-failures/</link>
		<comments>http://www.embeddedinsights.com/channels/2011/08/17/how-does-your-company-handle-test-failures/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 17:40:42 +0000</pubDate>
		<dc:creator>Robert Cravotta</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Question of the Week]]></category>
		<category><![CDATA[Simulation & Debugging]]></category>
		<category><![CDATA[Failure]]></category>
		<category><![CDATA[System Integration]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=618</guid>
		<description><![CDATA[For some projects, the company knows that a series of failures might be unavoidable, but many projects are not able to justify a high level of stress testing and analysis. Is it appropriate to analyze test data less diligently and let potential anomalies slip through and be discovered later when you might not be on the project anymore? How does your company handle failures?]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2011/08/17/how-does-your-company-handle-test-failures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How much trial and error do you rely on in designs?</title>
		<link>http://www.embeddedinsights.com/channels/2011/08/10/how-much-trial-and-error-do-you-rely-on-in-designs/</link>
		<comments>http://www.embeddedinsights.com/channels/2011/08/10/how-much-trial-and-error-do-you-rely-on-in-designs/#comments</comments>
		<pubDate>Wed, 10 Aug 2011 19:05:49 +0000</pubDate>
		<dc:creator>Robert Cravotta</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Question of the Week]]></category>
		<category><![CDATA[Simulation & Debugging]]></category>
		<category><![CDATA[God Complex]]></category>
		<category><![CDATA[Trial and Error]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=616</guid>
		<description><![CDATA[The process of iterative trial and error has been used by numerous design teams to solve complex problems. Is this a mechanism that applies to a small set of problems or is it successfully used in more problem spaces than is first apparent?]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2011/08/10/how-much-trial-and-error-do-you-rely-on-in-designs/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>The importance of failing quickly and often</title>
		<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/</link>
		<comments>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 17:54:08 +0000</pubDate>
		<dc:creator>Robert Cravotta</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Debugging]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=394</guid>
		<description><![CDATA[Kindergarteners consistently outperform business school graduates in the Marshmallow Challenge. This exercise teaches the importance of prototyping and iterative design processes. The poor performance of the business graduates also suggest that engineers need to not only deal with constraints of real world physics, but that they may have to teach or remind their management about the importance of iterative failures.]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>To Design Innovative Products, You Must Fail Quickly.</title>
		<link>http://www.embeddedinsights.com/channels/2010/11/12/to-design-innovative-products-you-must-fail-quickly/</link>
		<comments>http://www.embeddedinsights.com/channels/2010/11/12/to-design-innovative-products-you-must-fail-quickly/#comments</comments>
		<pubDate>Fri, 12 Nov 2010 16:53:19 +0000</pubDate>
		<dc:creator>Casey Weltzin</dc:creator>
				<category><![CDATA[Exploration & Prototyping]]></category>
		<category><![CDATA[Voices of Industry]]></category>

		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=375</guid>
		<description><![CDATA[Complex devices and machines typically require tens or even hundreds of iterations during the design process; in short, failures. A prototyping platform enables developers to more easily add and change resources, such as extra I/O points, tap into the power of custom logic without the costs of an ASIC, and “fail quickly.” Rapid “failing” helps design teams to be more nimble at weeding out good ideas from bad.]]></description>
		<wfw:commentRss>http://www.embeddedinsights.com/channels/2010/11/12/to-design-innovative-products-you-must-fail-quickly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
