<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reflections on Software Engineering &#187; Design</title>
	<atom:link href="http://neverletdown.net/topics/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://neverletdown.net</link>
	<description>by Michael Keeling</description>
	<lastBuildDate>Wed, 14 Sep 2011 02:23:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Exploring the Design Space</title>
		<link>http://neverletdown.net/2010/09/exploring-the-design-space/</link>
		<comments>http://neverletdown.net/2010/09/exploring-the-design-space/#comments</comments>
		<pubDate>Fri, 03 Sep 2010 14:18:01 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[bduf]]></category>
		<category><![CDATA[Big Design Up Front]]></category>
		<category><![CDATA[emergent design]]></category>
		<category><![CDATA[science of the artificial]]></category>
		<category><![CDATA[software architecture]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=405</guid>
		<description><![CDATA[In Choosing a Software Design Strategy I proposed that your understanding of the design space will determine what design strategies are appropriate for your project. That is, how much you know about the problem domain and solution space will determine how much design work is appropriate for your project. Rather than fussing over dogma, the [...]]]></description>
			<content:encoded><![CDATA[In Choosing a Software Design Strategy I proposed that your understanding of the design space will determine what design strategies are appropriate for your project.  That is, how much you know about the problem domain and solution space will determi]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/09/exploring-the-design-space/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Choosing a Software Design Strategy</title>
		<link>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/</link>
		<comments>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 22:01:36 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[ACDM]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[emergent design]]></category>
		<category><![CDATA[science of the artificial]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software engineering]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=384</guid>
		<description><![CDATA[I was reading an article from the Joel on Software archives and was struck by this quote from The Project Aardvark Spec: I can't tell you how strongly I believe in Big Design Up Front, which the proponents of Extreme Programming consider anathema. I]]></description>
			<content:encoded><![CDATA[I was reading an article from the Joel on Software archives and was struck by this quote from The Project Aardvark Spec:
I can't tell you how strongly I believe in Big Design Up Front, which the proponents of Extreme Programming consider anathema. I]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/08/choosing-a-software-design-strategy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improvisational Architecture</title>
		<link>http://neverletdown.net/2010/07/improvisational-architecture/</link>
		<comments>http://neverletdown.net/2010/07/improvisational-architecture/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 04:30:14 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Agile Development]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[Big Design Up Front]]></category>
		<category><![CDATA[emergent design]]></category>
		<category><![CDATA[improvisation]]></category>
		<category><![CDATA[jazz]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[xp2010]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=370</guid>
		<description><![CDATA[If you were to go to two improvisational jazz performances, even two concerts by the same band, you'd hear different music at each show. The thrill of experiencing something unique, as it is created, without any kind of real plan or rehearsal, is bo]]></description>
			<content:encoded><![CDATA[If you were to go to two improvisational jazz performances, even two concerts by the same band, you'd hear different music at each show.  The thrill of experiencing something unique, as it is created, without any kind of real plan or rehearsal, is bo]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/07/improvisational-architecture/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Book Review: The Design of Design by Fred Brooks</title>
		<link>http://neverletdown.net/2010/04/book-review-the-design-of-design-by-fred-brooks/</link>
		<comments>http://neverletdown.net/2010/04/book-review-the-design-of-design-by-fred-brooks/#comments</comments>
		<pubDate>Thu, 01 Apr 2010 14:15:31 +0000</pubDate>
		<dc:creator>Michael Keeling</dc:creator>
				<category><![CDATA[Book Review]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Fred Brooks]]></category>
		<category><![CDATA[science of the artificial]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software engineering]]></category>
		<category><![CDATA[waterfall]]></category>

		<guid isPermaLink="false">http://neverletdown.net/?p=242</guid>
		<description><![CDATA[During one of the last discussions in my great papers in software engineering reading course Mary Shaw, our discussion moderator, casually alluded to a follow-up class in the next fall semester, "Fred sent me an early draft manuscript of a book he’]]></description>
			<content:encoded><![CDATA[During one of the last discussions in my great papers in software engineering reading course Mary Shaw, our discussion moderator, casually alluded to a follow-up class in the next fall semester, "Fred sent me an early draft manuscript of a book he’]]></content:encoded>
			<wfw:commentRss>http://neverletdown.net/2010/04/book-review-the-design-of-design-by-fred-brooks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

