<?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 for Jorge Manrubia</title>
	<atom:link href="http://jorgemanrubia.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jorgemanrubia.net</link>
	<description>Personal Page</description>
	<lastBuildDate>Mon, 06 Apr 2009 15:02:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on The role of models in Agile and Model Driven Development approaches by Mike Jones</title>
		<link>http://jorgemanrubia.net/2009/04/05/the-role-of-models-in-agile-and-mde-development-approaches/comment-page-1/#comment-165</link>
		<dc:creator>Mike Jones</dc:creator>
		<pubDate>Mon, 06 Apr 2009 15:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://jorgemanrubia.net/2009/04/05/the-role-of-models-in-agile-and-mde-development-approaches/#comment-165</guid>
		<description>&lt;p&gt;Models cannot be converted into code easily?  I have to disagree with this statement.  If you have been a developer for more than, say 12 years, you will undoubtedly remember the days of CASE tools.  Several of these products did an excellent job of generating code from models.  The problem was that the models were developed using a waterfall approach (Information Engineering was the most common method) which ended not accurately representing the business need.  And since we spent all the time up front modeling to get it &#039;right&#039; we did not show the end users a working solution until everything was done.   The end result, applications that did not meet end user expectations, were late and cost more than estimated.&lt;/p&gt;

&lt;p&gt;In my experience Agile directly addresses the issue of an inability to accurately specify exactly what the business needs as a requirement.  Why?  Until the end users see the working application they cannot accurately imagine how it will support their process and how they might modify their working process to accommodate automation.  Thus Agile&#039;s iterative approach allows us to deliver early and often taking into account feedback from the end user community as we go resulting in fit for purpose applications that only deliver the needed functionality to meet business needs!  Of course if we manage the project, its backlog and work with the business to trade high value needs for lower value items we end up delivering on time and in budget!&lt;/p&gt;

&lt;p&gt;To learn more about the approach we use go read our methodology white paper titled ‘Eight stages of an Agile approach that works’.  You can find it at this link under white papers:  http://tinyurl.com/dmnf8w.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Models cannot be converted into code easily?  I have to disagree with this statement.  If you have been a developer for more than, say 12 years, you will undoubtedly remember the days of CASE tools.  Several of these products did an excellent job of generating code from models.  The problem was that the models were developed using a waterfall approach (Information Engineering was the most common method) which ended not accurately representing the business need.  And since we spent all the time up front modeling to get it &#8216;right&#8217; we did not show the end users a working solution until everything was done.   The end result, applications that did not meet end user expectations, were late and cost more than estimated.</p>

<p>In my experience Agile directly addresses the issue of an inability to accurately specify exactly what the business needs as a requirement.  Why?  Until the end users see the working application they cannot accurately imagine how it will support their process and how they might modify their working process to accommodate automation.  Thus Agile&#8217;s iterative approach allows us to deliver early and often taking into account feedback from the end user community as we go resulting in fit for purpose applications that only deliver the needed functionality to meet business needs!  Of course if we manage the project, its backlog and work with the business to trade high value needs for lower value items we end up delivering on time and in budget!</p>

<p>To learn more about the approach we use go read our methodology white paper titled ‘Eight stages of an Agile approach that works’.  You can find it at this link under white papers:  <a href="http://tinyurl.com/dmnf8w" rel="nofollow">http://tinyurl.com/dmnf8w</a>.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Changed to Wordpress by Ben</title>
		<link>http://jorgemanrubia.net/2009/02/08/changed-to-wordpress/comment-page-1/#comment-9</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 09 Feb 2009 05:03:41 +0000</pubDate>
		<guid isPermaLink="false">http://jorgemanrubia.net/2009/02/08/changed-to-wordpress/#comment-9</guid>
		<description>&lt;p&gt;Hi! We are actually upgrading Rails after MySQL 5 updates in mid to later February, an announcement with details and dates will be sent out this week with Ruby details.&lt;/p&gt;

&lt;p&gt;Thanks, Ben&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi! We are actually upgrading Rails after MySQL 5 updates in mid to later February, an announcement with details and dates will be sent out this week with Ruby details.</p>

<p>Thanks, Ben</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Skittlish theme for Typo by Changed to Wordpress - Jorge Manrubia</title>
		<link>http://jorgemanrubia.net/2008/05/23/skittlish-theme-for-typo/comment-page-1/#comment-7</link>
		<dc:creator>Changed to Wordpress - Jorge Manrubia</dc:creator>
		<pubDate>Sun, 08 Feb 2009 21:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://jorgemanrubia.net/blog/?p=11#comment-7</guid>
		<description>&lt;p&gt;[...] first theme choice was Skittish (the theme I was using with Typo). The problem was that it wasn&#8217;t updated to the last version of Wordpress and it needed minor [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] first theme choice was Skittish (the theme I was using with Typo). The problem was that it wasn&#8217;t updated to the last version of Wordpress and it needed minor [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Comparing EMF Models by Errors in my post on Comparing EMF Models - Jorge Manrubia</title>
		<link>http://jorgemanrubia.net/2008/07/06/comparing-emf-models/comment-page-1/#comment-2</link>
		<dc:creator>Errors in my post on Comparing EMF Models - Jorge Manrubia</dc:creator>
		<pubDate>Sun, 08 Feb 2009 01:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://jorgemanrubia.net/blog/?p=30#comment-2</guid>
		<description>&lt;p&gt;[...] was an error in the code originally posted in my article on Comparing EMF models. Thank you so much to Jim Showalter for warning me. The post has been updated with the right code. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] was an error in the code originally posted in my article on Comparing EMF models. Thank you so much to Jim Showalter for warning me. The post has been updated with the right code. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Comparing EMF Models by Code Reviewer</title>
		<link>http://jorgemanrubia.net/2008/07/06/comparing-emf-models/comment-page-1/#comment-3</link>
		<dc:creator>Code Reviewer</dc:creator>
		<pubDate>Wed, 19 Nov 2008 01:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://jorgemanrubia.net/blog/?p=30#comment-3</guid>
		<description>&lt;p&gt;This code doesn&#039;t actually work. If you look at the chain of calls, you&#039;re basically doing: replace o1.toString().hashCode() in o1.toString(), but o1.toString() contains the hashCode of o1, not of o1&#039;s toString(). Also, there&#039;s no reason to replace the class name, and even if there was you&#039;re replacing o1.toString().getClass().getName(), which will always return java.lang.String, when what you want is to replace o1.getClass().getName(). And even if you get both replaces working, ordering will fail when comparing two models generated from the same diagram but with different seeds for the IDs, because the IDs won&#039;t match, so the sorts won&#039;t match.&quot;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This code doesn&#8217;t actually work. If you look at the chain of calls, you&#8217;re basically doing: replace o1.toString().hashCode() in o1.toString(), but o1.toString() contains the hashCode of o1, not of o1&#8217;s toString(). Also, there&#8217;s no reason to replace the class name, and even if there was you&#8217;re replacing o1.toString().getClass().getName(), which will always return java.lang.String, when what you want is to replace o1.getClass().getName(). And even if you get both replaces working, ordering will fail when comparing two models generated from the same diagram but with different seeds for the IDs, because the IDs won&#8217;t match, so the sorts won&#8217;t match.&#8221;</p>]]></content:encoded>
	</item>
</channel>
</rss>
