<?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: Software Prototyping – Part 2: Throw Away or Evolve?</title>
	<atom:link href="http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/</link>
	<description>News and events about Caretta Software, GUI Design Studio, User Interface Design and Software Prototyping</description>
	<lastBuildDate>Thu, 10 Nov 2011 16:55:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: lanbede</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-4836</link>
		<dc:creator>lanbede</dc:creator>
		<pubDate>Wed, 29 Dec 2010 08:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-4836</guid>
		<description>&quot;Because it involves implementation of the system itself, the coding has to be of production quality from the start. The idea of ‘cleaning it up later’ is a very bad one since this will never happen in practice, leading to potential problems and instability later on. But this conflicts with one of the key benefits of being able to create prototypes quickly. Also, because of the effort that’s gone into it, there can become too much attachment to the implementation which leads to a resistance to change.&quot;
You can see more about that?</description>
		<content:encoded><![CDATA[<p>&#8220;Because it involves implementation of the system itself, the coding has to be of production quality from the start. The idea of ‘cleaning it up later’ is a very bad one since this will never happen in practice, leading to potential problems and instability later on. But this conflicts with one of the key benefits of being able to create prototypes quickly. Also, because of the effort that’s gone into it, there can become too much attachment to the implementation which leads to a resistance to change.&#8221;<br />
You can see more about that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: incremental prototyping</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-492</link>
		<dc:creator>incremental prototyping</dc:creator>
		<pubDate>Fri, 19 Mar 2010 10:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-492</guid>
		<description>[...] has its own language. One example of this product speak is the term product champion. ManySoftware Prototyping Part 2: Throw Away or Evolve ...... the final, delivered application (or system) through incremental developments and changes. ... [...]</description>
		<content:encoded><![CDATA[<p>[...] has its own language. One example of this product speak is the term product champion. ManySoftware Prototyping Part 2: Throw Away or Evolve &#8230;&#8230; the final, delivered application (or system) through incremental developments and changes. &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-116</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Wed, 30 Dec 2009 12:09:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-116</guid>
		<description>Thanks for your comment, Justin.

Even with dedicated development resources and constraints on the architecture or tools (that will almost certainly be present once an application moves into actual implementation and beyond &#039;version 1&#039;), I think that the very nature of evolutionary development without some sort of up-front throw-away prototyping will miss opportunities for a better design.

Presenting and evaluating multiple alternatives can be very tricky when you&#039;re building them into the application itself whereas a lot can be explored and learned even from quick sketches on paper.

All the best,
Jonathan</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Justin.</p>
<p>Even with dedicated development resources and constraints on the architecture or tools (that will almost certainly be present once an application moves into actual implementation and beyond &#8216;version 1&#8242;), I think that the very nature of evolutionary development without some sort of up-front throw-away prototyping will miss opportunities for a better design.</p>
<p>Presenting and evaluating multiple alternatives can be very tricky when you&#8217;re building them into the application itself whereas a lot can be explored and learned even from quick sketches on paper.</p>
<p>All the best,<br />
Jonathan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin McNeal</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-98</link>
		<dc:creator>Justin McNeal</dc:creator>
		<pubDate>Fri, 18 Dec 2009 10:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-98</guid>
		<description>Good Article. I agree with everything that you&#039;ve stated. I am a big fan of throw-away prototypes, however if you have dedicated development resources, and an architecture that is constrained to a specific set of tools/languages, then an evolutionary prototype can be the best model. Keep the articles coming. Thank you.</description>
		<content:encoded><![CDATA[<p>Good Article. I agree with everything that you&#8217;ve stated. I am a big fan of throw-away prototypes, however if you have dedicated development resources, and an architecture that is constrained to a specific set of tools/languages, then an evolutionary prototype can be the best model. Keep the articles coming. Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Software Prototyping – Part 2: Throw Away or Evolve? « Caretta Software Blog -- Topsy.com</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-97</link>
		<dc:creator>Tweets that mention Software Prototyping – Part 2: Throw Away or Evolve? « Caretta Software Blog -- Topsy.com</dc:creator>
		<pubDate>Thu, 17 Dec 2009 21:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-97</guid>
		<description>[...] This post was mentioned on Twitter by Jan Jursa, brian_henderson. brian_henderson said: RT@IATV Good article: &quot;Software Prototyping – Part 2: Throw Away or Evolve?&quot; http://bit.ly/8JLB0f (carettasoftware.com) [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Jan Jursa, brian_henderson. brian_henderson said: RT@IATV Good article: &quot;Software Prototyping – Part 2: Throw Away or Evolve?&quot; <a href="http://bit.ly/8JLB0f" rel="nofollow">http://bit.ly/8JLB0f</a> (carettasoftware.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Blog</title>
		<link>http://www.carettasoftware.com/blog/software-prototyping-%e2%80%93-part-2-throw-away-or-evolve/175/comment-page-1/#comment-33</link>
		<dc:creator>Interesting Blog</dc:creator>
		<pubDate>Sun, 29 Nov 2009 18:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.carettasoftware.com/blog/?p=175#comment-33</guid>
		<description>It?s good to see you make postings on this topic, I have to bookmark this web site. Keep up the good work.</description>
		<content:encoded><![CDATA[<p>It?s good to see you make postings on this topic, I have to bookmark this web site. Keep up the good work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

