<?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>James Grenning's Blog &#187; Embedded</title>
	<atom:link href="http://www.renaissancesoftware.net/blog/archives/tag/embedded/feed" rel="self" type="application/rss+xml" />
	<link>http://www.renaissancesoftware.net/blog</link>
	<description>Blogging about Agile Development, especially embedded.  Follow me on twitter: jwgrenning</description>
	<lastBuildDate>Thu, 12 Jan 2012 00:59:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Agile Design and Embedded</title>
		<link>http://www.renaissancesoftware.net/blog/archives/81</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/81#comments</comments>
		<pubDate>Thu, 12 Nov 2009 12:31:03 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Evolutionary Design]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=81</guid>
		<description><![CDATA[One important realization on the journey from a BDUF approach to an iterative and agile approach is that design is never done. Designs evolve. The waterfall emphasis has been to unnaturally try to control software physics by imposing requirements freezes and burdensome change control. The process of developing software is part science and part creative. [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/81/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t Let Embedded Tool Chain Slow You Down.</title>
		<link>http://www.renaissancesoftware.net/blog/archives/41</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/41#comments</comments>
		<pubDate>Wed, 01 Apr 2009 22:55:15 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[TDD]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=41</guid>
		<description><![CDATA[During my TDD session at the Embedded Systems Conference yesterday, I did a demo. Before the demo, I make the case for TDD as a way to prevent bugs (see Physics of TDD). For the live demo I usually code on my mac and run the tests there as well. The question always comes up: [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/41/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Deep Agile Embedded Brain Storm</title>
		<link>http://www.renaissancesoftware.net/blog/archives/40</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/40#comments</comments>
		<pubDate>Tue, 24 Feb 2009 16:07:52 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Deep Agile Embedded]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[TDD]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=40</guid>
		<description><![CDATA[Let&#8217;s say you were an embedded systems developer, and you were planning on attending a conference like the Deep Agile Embedded. What questions would you hope you could get answers for at the conference? What if you already knew it all but were sending your boss, co-worker, or CEO who needed to learn more, what [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/40/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Now I&#8217;ll really use test driven development to write device driver code</title>
		<link>http://www.renaissancesoftware.net/blog/archives/8</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/8#comments</comments>
		<pubDate>Thu, 06 Mar 2008 10:38:46 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[TDD Device Driver]]></category>

		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=8</guid>
		<description><![CDATA[In the last article, I added tests to existing code. So I did not really do Test Driven Development. I did Test After Development. Let&#8217;s do some TDD now and design the block erase function. I&#8217;ll go from the spec, to the test to the code. The data sheet for the device describes block erase [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/8/feed</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Who says you can’t test drive a device driver?</title>
		<link>http://www.renaissancesoftware.net/blog/archives/7</link>
		<comments>http://www.renaissancesoftware.net/blog/archives/7#comments</comments>
		<pubDate>Mon, 18 Feb 2008 01:53:29 +0000</pubDate>
		<dc:creator>jwgrenning</dc:creator>
				<category><![CDATA[Agile Embedded]]></category>
		<category><![CDATA[Embedded TDD]]></category>
		<category><![CDATA[Test Driven Development]]></category>
		<category><![CDATA[Embedded]]></category>
		<category><![CDATA[Embedded Agile]]></category>
		<category><![CDATA[TDD]]></category>
		<category><![CDATA[TDD Device Driver]]></category>

		<guid isPermaLink="false">http://blog.renaissancesoftware.net/?p=7</guid>
		<description><![CDATA[I keep hearing that you can&#8217;t write unit tests for device drivers. I don&#8217;t believe that&#8217;s true. To disprove this claim, I thought I would find a device driver and write some unit tests for it. This blog posting shows what device driver unit tests look line. I found a flash memory driver at the [...]]]></description>
		<wfw:commentRss>http://www.renaissancesoftware.net/blog/archives/7/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

