<?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>Engineering Institute &#187; chief goal</title>
	<atom:link href="http://www.etoinstitute.org/tag/chief-goal/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.etoinstitute.org</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 02:18:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Software Maintenance is a Solution, Not a Problem (An Excerpt from Software Conflict 2.0) By Robert L. Glass</title>
		<link>http://www.etoinstitute.org/software-maintenance-is-a-solution-not-a-problem-an-excerpt-from-software-conflict-2-0-by-robert-l-glass/</link>
		<comments>http://www.etoinstitute.org/software-maintenance-is-a-solution-not-a-problem-an-excerpt-from-software-conflict-2-0-by-robert-l-glass/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 04:19:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[chief goal]]></category>
		<category><![CDATA[excerpt from]]></category>
		<category><![CDATA[oriented view]]></category>
		<category><![CDATA[robert l glass]]></category>
		<category><![CDATA[software conflict]]></category>
		<category><![CDATA[software maintenance]]></category>
		<category><![CDATA[software solution]]></category>

		<guid isPermaLink="false">http://www.etoinstitute.org/software-maintenance-is-a-solution-not-a-problem-an-excerpt-from-software-conflict-2-0-by-robert-l-glass/</guid>
		<description><![CDATA[The traditional, problem-oriented view of maintenance says that our chief goal in maintenance should be to reduce costs. I think that&#8217;s the wrong emphasis. If maintenance is a solution instead of a problem, we can quickly see that what we really want to do is more of it, not less of it. And the emphasis, [...]]]></description>
			<content:encoded><![CDATA[<p>The traditional, problem-oriented view of maintenance says that our chief goal in maintenance should be to reduce costs. I think that&#8217;s the wrong emphasis. If maintenance is a solution instead of a problem, we can quickly see that what we really want to do is more of it, not less of it. And the emphasis, when we do it, should be on maximizing effectiveness, and not on minimizing cost. An excerpt from Software Conflict 2.0.<br/><a href="http://www.developerdotstar.com/mag/articles/maintenance_solution.html" />Click here for the full article.<br />
    <a href="http://www.developerdotstar.com/mag/articles/maintenance_solution.html">Read More</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.etoinstitute.org/software-maintenance-is-a-solution-not-a-problem-an-excerpt-from-software-conflict-2-0-by-robert-l-glass/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

