Talk:Continuous design

This article is inaccurate. Continuous design was not created by MartinFowler. It's also called "evolutionary design" or "incremental design," both of which were popularized by ExtremeProgramming. Continuous design is a possibly more accurate term because continuous design consists of designing continuously throughout software development rather than all up-front (in the WaterfallModel) or in bursts at the beginning of each iteration (as in the IterativeModel). It's characterized by constant TestDrivenDevelopment and Refactoring.

MartinFowler wrote a popular, and excellent, book called "Refactoring" as well as a popular article entitled "Is Design Dead?" that talked about continuous/evolutionary design. As Design column editor for IEEE, he published an article titled "Continuous Design" by Jim Shore (me). MartinFowler is certainly a person with close ties to continuous design, but it wouldn't be fair to say that he created it.

Hopefully this information will allow someone to flesh out the article a bit more. I don't have the energy to put this in proper encyclopedia form right now.  :)

• Done. And remember, you can type in your info onto the page and someone (like me) will make it more encyclopedic. Ziroby 22:53, 14 December 2005 (UTC)

Expand on development methodologies that work with continuous design

The article could use some expansion on which development methodologies work with continuous design.

As it stands now only Extreme programming is mentioned. Are there other noteworthy methodologies? 62.107.105.61 (talk) 23:45, 19 February 2014 (UTC)

Relation to continuous integration

What is the relation to continuous integration? The See also section links to Continuous integration but the rest of the article does not mention it. If it is actually related enough to be listed in the section why is Continuous delivery not? 62.107.105.61 (talk) 23:50, 19 February 2014 (UTC)