http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspxMy good friend Malcolm posted a response to my IFaP article and asked, in essence, "what is the minimum amount of architecture needed for a system built with Test Driven Design." I had to stare at that. For me, TDD meant Test Driven Development, not Testen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspx#1705831Sun, 18 Feb 2007 19:17:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:1705831Sam Gentile<p>Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software</p>http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspx#1705832Sun, 18 Feb 2007 19:17:37 GMT91d46819-8472-40ad-a661-2c78acb4018c:1705832Sam Gentile<p>Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software</p>http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspx#1705839Sun, 18 Feb 2007 19:18:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:1705839Sam Gentile<p>Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software</p> http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspx#1714113Mon, 19 Feb 2007 13:20:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:1714113Impersonation Failure<p>WF, WCF and CardSpace training materials The .NET Framework 3.0 training kit for WF, WCF, and CardSpace</p> http://blogs.msdn.com/nickmalik/archive/2007/02/09/the-minimum-amount-of-architecture-needed-for-test-driven-design.aspx#1728004Tue, 20 Feb 2007 20:28:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:1728004Scott Sehlhorst<p>Really interesting discussion - the same concepts abstract to requirements. &nbsp;Not touching the requirements is also &quot;not agile.&quot;</p> <p>Part of the problem is that &quot;change management processes&quot; are usually &quot;change prevention processes&quot; mislabeled.</p> <p>We also have the issue of &quot;don't spend time on doc - spend time on code&quot; that is regularly oversimplified.</p> <p>It's true that the goal is to deliver software, not doc (requirements or design). &nbsp;However, having good doc does enable delivery of software.</p> <p>Nice thorny, unresolved issue.</p> <p>Anyway - good article, trying to force me to think about stuff that I don't have time to do today, as I'm buried in some business analysis tasks at the moment. &nbsp;Looking forward to reading more here, and thanks for the link!</p> <p>Scott</p>