<?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>QA&#38;TEST Blog &#187; embedded</title>
	<atom:link href="http://www.qatest.org/en/blog/index.php/tag/embedded/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.qatest.org/en/blog</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 16:31:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Build checklist for embedded software projects</title>
		<link>http://www.qatest.org/en/blog/index.php/2008/07/22/build-checklist-for-embedded-software-projects/</link>
		<comments>http://www.qatest.org/en/blog/index.php/2008/07/22/build-checklist-for-embedded-software-projects/#comments</comments>
		<pubDate>Tue, 22 Jul 2008 11:37:00 +0000</pubDate>
		<dc:creator>Itzi</dc:creator>
				<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[checklist]]></category>
		<category><![CDATA[embedded]]></category>
		<category><![CDATA[jason cohen]]></category>

		<guid isPermaLink="false">http://www.qatest.org/en/blog/index.php/2008/07/22/build-checklist-for-embedded-software-projects/</guid>
		<description><![CDATA[Code review checklists are usually a pain. They&#8217;re often ridiculous in length or content. They&#8217;re not fun to use. Checklists can be an excellent way of finding defects early in the development process, but most of the time, checklists are so impractical that they&#8217;re more of a hindrance than a help. The problem is that [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.qatest.org/en/blog/wp-content/uploads/2008/07/lista.jpg" alt="lista.jpg" align="left" width="211" height="208" />Code review <strong>checklists</strong> are usually a pain. They&#8217;re often ridiculous in length or content. They&#8217;re not fun to use. Checklists can be an excellent way of <strong>finding defects</strong> early in the development process, but most of the time, checklists are so impractical that they&#8217;re more of a hindrance than a help.<br />
The problem is that people use the list as a <strong>general guide</strong>. They don&#8217;t consider every item in every file. Which items will they remember as they look at the code? Will it be the most important ones?</p>
<p>If you want to continue reading Jason Cohen’s article at <strong>Embedded.com</strong>, click <a href="http://embedded.com/columns/technicalinsights/208803162;jsessionid=OC0URYRW5PJTSQSNDLRSKH0CJUNN2JVN" target="_blank">here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.qatest.org/en/blog/index.php/2008/07/22/build-checklist-for-embedded-software-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

