<?xml version="1.0" encoding="iso-8859-2"?><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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Just in Case Tool</title>
	<atom:link href="http://fracturedbloughts.rolandhesz.com/2008/07/25/just-in-case-tool/feed/" rel="self" type="application/rss+xml" />
	<link>http://fracturedbloughts.rolandhesz.com/2008/07/25/just-in-case-tool/</link>
	<description>Musings about work and life</description>
	<lastBuildDate>Thu, 06 May 2010 07:00:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19827</generator>
	<item>
		<title>By: Peter Moore</title>
		<link>http://fracturedbloughts.rolandhesz.com/2008/07/25/just-in-case-tool/comment-page-1/#comment-1396</link>
		<dc:creator>Peter Moore</dc:creator>
		<pubDate>Sun, 13 Sep 2009 22:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://fracturedbloughts.heszroland.hu/?p=181#comment-1396</guid>
		<description>I&#039;ll post the same information to my blog, thanks for ideas and great article.</description>
		<content:encoded><![CDATA[<p>I&#39;ll post the same information to my blog, thanks for ideas and great article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland Hesz</title>
		<link>http://fracturedbloughts.rolandhesz.com/2008/07/25/just-in-case-tool/comment-page-1/#comment-1304</link>
		<dc:creator>Roland Hesz</dc:creator>
		<pubDate>Tue, 27 Jan 2009 17:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://fracturedbloughts.heszroland.hu/?p=181#comment-1304</guid>
		<description>Well, we used EA for every design, and yes, there were times when we lost touch with reality for a time.&lt;br&gt;&lt;br&gt;One thing that is important with every CASE tool is that you have to keep it in synch with the actual system.&lt;br&gt;Otherwise you will end up with a useless set of documentation.&lt;br&gt;&lt;br&gt;And you should never forget that a CASE tool is that: a tool and nothing else.</description>
		<content:encoded><![CDATA[<p>Well, we used EA for every design, and yes, there were times when we lost touch with reality for a time.</p>
<p>One thing that is important with every CASE tool is that you have to keep it in synch with the actual system.<br />Otherwise you will end up with a useless set of documentation.</p>
<p>And you should never forget that a CASE tool is that: a tool and nothing else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arpad</title>
		<link>http://fracturedbloughts.rolandhesz.com/2008/07/25/just-in-case-tool/comment-page-1/#comment-1303</link>
		<dc:creator>Arpad</dc:creator>
		<pubDate>Tue, 27 Jan 2009 17:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://fracturedbloughts.heszroland.hu/?p=181#comment-1303</guid>
		<description>Let me agree with you on this post :)&lt;br&gt;Having standard documents, shared best practices and templates is important.&lt;br&gt;EA is a good tool, i know many firms using it.&lt;br&gt;&lt;br&gt;But let me highlight the danger of EA: it is too good. &lt;br&gt;If you use EA too much, you will lose touch with the reailty.</description>
		<content:encoded><![CDATA[<p>Let me agree with you on this post :)<br />Having standard documents, shared best practices and templates is important.<br />EA is a good tool, i know many firms using it.</p>
<p>But let me highlight the danger of EA: it is too good. <br />If you use EA too much, you will lose touch with the reailty.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

