<?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: Does you code have integrity?</title>
	<atom:link href="http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/</link>
	<description>Creating better software</description>
	<lastBuildDate>Mon, 02 Jan 2012 09:09:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Development and Integrity Management by Eli Lopian &#187; Big Steps to Code Integrity</title>
		<link>http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/comment-page-1/#comment-39053</link>
		<dc:creator>Development and Integrity Management by Eli Lopian &#187; Big Steps to Code Integrity</dc:creator>
		<pubDate>Sun, 07 Jun 2009 10:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/#comment-39053</guid>
		<description>[...] Typemock is making big steps towards its goal of code integrity. Code integrity is what we consider the new paradigm of writing software. Moving the responsibility of code-correctness back to the developers. It is too easy to get sloppy and to leave it to the QA to find our bugs, thus developing without integrity and leading to waste in time and money. When developing with integrity, we are all responsible to make sure the code does what was intended to do. [...]</description>
		<content:encoded><![CDATA[<p>[...] Typemock is making big steps towards its goal of code integrity. Code integrity is what we consider the new paradigm of writing software. Moving the responsibility of code-correctness back to the developers. It is too easy to get sloppy and to leave it to the QA to find our bugs, thus developing without integrity and leading to waste in time and money. When developing with integrity, we are all responsible to make sure the code does what was intended to do. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eli Lopian</title>
		<link>http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/comment-page-1/#comment-36721</link>
		<dc:creator>Eli Lopian</dc:creator>
		<pubDate>Fri, 08 May 2009 11:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/#comment-36721</guid>
		<description>What you are suggesting are ways to reach a higher code integrity. But I am looking for a *measurement* of code integrity. Something that will help us see what actions have more impact on our code integrity</description>
		<content:encoded><![CDATA[<p>What you are suggesting are ways to reach a higher code integrity. But I am looking for a *measurement* of code integrity. Something that will help us see what actions have more impact on our code integrity</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/comment-page-1/#comment-36690</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 08 May 2009 04:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/#comment-36690</guid>
		<description>Integrity has another meaning which is to be unimpaired or even perfect in condition. I think of it more as the software should do what it is intended to do (you&#039;re right - whether it benefits the customer or not).  This means no bugs and no incomplete functionality (which could be characterized as a bug I guess). Regression tests, source code analysis, dynamic analysis, manual testing, code review, fuzzing, are just some of the many strategies for creating software with integrity.</description>
		<content:encoded><![CDATA[<p>Integrity has another meaning which is to be unimpaired or even perfect in condition. I think of it more as the software should do what it is intended to do (you&#8217;re right &#8211; whether it benefits the customer or not).  This means no bugs and no incomplete functionality (which could be characterized as a bug I guess). Regression tests, source code analysis, dynamic analysis, manual testing, code review, fuzzing, are just some of the many strategies for creating software with integrity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raoul Duke</title>
		<link>http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/comment-page-1/#comment-36667</link>
		<dc:creator>Raoul Duke</dc:creator>
		<pubDate>Thu, 07 May 2009 21:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.elilopian.com/2009/05/06/does-you-code-have-integrity/#comment-36667</guid>
		<description>seems like there are 2 approaches:

1) theory: proofs, modeling.

2) practice: testing, manual or automated.</description>
		<content:encoded><![CDATA[<p>seems like there are 2 approaches:</p>
<p>1) theory: proofs, modeling.</p>
<p>2) practice: testing, manual or automated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

