<?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: lib4code</title>
	<atom:link href="http://inkdroid.org/journal/2005/12/08/lib4code/feed/" rel="self" type="application/rss+xml" />
	<link>http://inkdroid.org/journal/2005/12/08/lib4code/</link>
	<description>$pithy_personal_mission_statement</description>
	<lastBuildDate>Wed, 10 Mar 2010 02:04:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Akerman</title>
		<link>http://inkdroid.org/journal/2005/12/08/lib4code/comment-page-1/#comment-18</link>
		<dc:creator>Richard Akerman</dc:creator>
		<pubDate>Thu, 08 Dec 2005 17:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.inkdroid.org/journal/?p=53#comment-18</guid>
		<description>Thanks, I&#039;m glad the posting raised some useful points.  The diagram is really there to show all the different roles and slices you can take as part of a systems development effort.  It does look kind of waterfall-y, that was kind of a tradeoff.  I think there is a whole separate software engineering discussion that you can have, and you have raised a lot of the important points (small teams, good communication etc.)  In terms of actual development process I very much agree with you that you need to use an iterative, incremental, rapid design process.  

I wrote about one that CISTI has tried in &quot;having a RAD time with GRAPPLE&quot;.

http://scilib.typepad.com/science_library_pad/2005/02/software_develo.html

I do believe as stated in that post that you need a strong requirements process and architecture in order to be able to do rapid development successfully.</description>
		<content:encoded><![CDATA[<p>Thanks, I&#8217;m glad the posting raised some useful points.  The diagram is really there to show all the different roles and slices you can take as part of a systems development effort.  It does look kind of waterfall-y, that was kind of a tradeoff.  I think there is a whole separate software engineering discussion that you can have, and you have raised a lot of the important points (small teams, good communication etc.)  In terms of actual development process I very much agree with you that you need to use an iterative, incremental, rapid design process.  </p>
<p>I wrote about one that CISTI has tried in &#8220;having a RAD time with GRAPPLE&#8221;.</p>
<p><a href="http://scilib.typepad.com/science_library_pad/2005/02/software_develo.html" rel="nofollow">http://scilib.typepad.com/science_library_pad/2005/02/software_develo.html</a></p>
<p>I do believe as stated in that post that you need a strong requirements process and architecture in order to be able to do rapid development successfully.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
