<?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: Model Driven Architecture</title>
	<atom:link href="http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/</link>
	<description>Tales from the field...</description>
	<lastBuildDate>Sat, 11 Feb 2012 08:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Joe Ocampo</title>
		<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/#comment-277</link>
		<dc:creator>Joe Ocampo</dc:creator>
		<pubDate>Thu, 01 Nov 2007 17:29:02 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joe_ocampo/archive/2007/10/30/model-driven-architecture.aspx#comment-277</guid>
		<description>Yeah the song has been sung to many times before.  Enabling communication between developers and analyst should be the fundamental guiding principle of these tools.  We you start expecting the communication tool to produce code or production artifacts, this is where the crack meets the pipe.</description>
		<content:encoded><![CDATA[<p>Yeah the song has been sung to many times before.  Enabling communication between developers and analyst should be the fundamental guiding principle of these tools.  We you start expecting the communication tool to produce code or production artifacts, this is where the crack meets the pipe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Reddy</title>
		<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/#comment-276</link>
		<dc:creator>Joe Reddy</dc:creator>
		<pubDate>Thu, 01 Nov 2007 13:09:34 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joe_ocampo/archive/2007/10/30/model-driven-architecture.aspx#comment-276</guid>
		<description>Nevermind, I just F&#039;n Googled it.  I am not impressed...scared a little, but I think I have heard this song before.</description>
		<content:encoded><![CDATA[<p>Nevermind, I just F&#8217;n Googled it.  I am not impressed&#8230;scared a little, but I think I have heard this song before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Reddy</title>
		<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/#comment-275</link>
		<dc:creator>Joe Reddy</dc:creator>
		<pubDate>Thu, 01 Nov 2007 12:56:09 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joe_ocampo/archive/2007/10/30/model-driven-architecture.aspx#comment-275</guid>
		<description>&quot;What I am talking about is the modeling exercise outside of any tool right now.&quot;
What exactly are these tools doing that Visio can&#039;t do?
Thanks, 
Joe</description>
		<content:encoded><![CDATA[<p>&#8220;What I am talking about is the modeling exercise outside of any tool right now.&#8221;<br />
What exactly are these tools doing that Visio can&#8217;t do?<br />
Thanks,<br />
Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Ocampo</title>
		<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/#comment-274</link>
		<dc:creator>Joe Ocampo</dc:creator>
		<pubDate>Wed, 31 Oct 2007 12:31:10 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joe_ocampo/archive/2007/10/30/model-driven-architecture.aspx#comment-274</guid>
		<description>@The Hoff

I want to make things clear, I am not talking about executable diagrams. I am not to found of design tools magically creating code.  This is where Rational failed.

What I am talking about is the modeling exercise outside of any tool right now.  We use index cards and create a pretty impressive colorful collage of a domain issue.

The cards allow us to communicate in a tactile medium where all stakeholders have a common talking point that is evolutionary.

Why the MS Tool or any other tool for that matter is important, is that it would allow for quick modeling of domain.  This helps with remote customers that do not always have the luxury of being on site.</description>
		<content:encoded><![CDATA[<p>@The Hoff</p>
<p>I want to make things clear, I am not talking about executable diagrams. I am not to found of design tools magically creating code.  This is where Rational failed.</p>
<p>What I am talking about is the modeling exercise outside of any tool right now.  We use index cards and create a pretty impressive colorful collage of a domain issue.</p>
<p>The cards allow us to communicate in a tactile medium where all stakeholders have a common talking point that is evolutionary.</p>
<p>Why the MS Tool or any other tool for that matter is important, is that it would allow for quick modeling of domain.  This helps with remote customers that do not always have the luxury of being on site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evan</title>
		<link>http://lostechies.com/joeocampo/2007/10/30/model-driven-architecture/#comment-273</link>
		<dc:creator>Evan</dc:creator>
		<pubDate>Wed, 31 Oct 2007 05:54:20 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joe_ocampo/archive/2007/10/30/model-driven-architecture.aspx#comment-273</guid>
		<description>I&#039;m afraid I&#039;ve already written this one off.  One thing my BAs aren&#039;t asking for, executable diagrams.  They don&#039;t want to write code, neither do they want to doodle pictures.  Personally, I can type faster than I can drag and drop, so I&#039;ll pass as well.  Diagrams are great for communication, but I don&#039;t really want to use them in any capacity beyond that.  That&#039;s doubly true if the tools don&#039;t support roundtripping from the hidden abstraction when I have to modify it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid I&#8217;ve already written this one off.  One thing my BAs aren&#8217;t asking for, executable diagrams.  They don&#8217;t want to write code, neither do they want to doodle pictures.  Personally, I can type faster than I can drag and drop, so I&#8217;ll pass as well.  Diagrams are great for communication, but I don&#8217;t really want to use them in any capacity beyond that.  That&#8217;s doubly true if the tools don&#8217;t support roundtripping from the hidden abstraction when I have to modify it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
