Talk:Iterative and incremental development

From Wikipedia, the free encyclopedia

This is the talk page for discussing improvements to the Iterative and incremental development article. This is not a forum for general discussion about the article's subject.
Please sign and date your posts by typing four tildes (~~~~). Put new text under old text. Click here to start a new topic. New to Wikipedia? Welcome! Ask questions, get answers.	Be polite Assume good faith No personal attacks Be welcoming	Article policies No original research Neutral point of view Verifiability

[edit] V model

What are the advantages of "V" Model over the other life cycle models. —The preceding unsigned comment was added by 209.78.112.253 (talk • contribs) 19:09, 19 January 2006 (UTC2)

[edit] Merge with Incremental build model

Agree with the merge of Incremental build model.

1. A quick Googling of incremental build model shows that the term is hardly in use.
2. The article is a stub, and is vague to the point of being useless.
3. It is redundant to the text in this article.

—The preceding unsigned comment was added by 65.222.202.26 (talk • contribs) 18:45, 13 March 2006 (UTC2) Perhaps a bit too much emphasis on methodology guideines. In particular, methodology is a bit redundant in the "guidelines" section. I believe the incremental build model should be separate. I concur with many of the contributors; the incremental build model is rarely utilized as a business process model. Does anyone in Software use or employ this methodology? I am not aware of any such cases. On the other hand, I do know of many references to the iterative approach in Technology Consulting.

A project iteration, especially in the DW business process, is not necessarily incremental development. —The preceding unsigned comment was added by 83.41.43.222 (talk • contribs) 00:37, 25 March 2006 (UTC2)

I can certainly understand the point of merging these two documents. However, as a student studying Software Engineering, I can recognize the differences. I think it would be beneficial to keep these two articles separate. I realize that there is an overlap in material, but there is also a vast amount of differences that the stub seems not to have taken account of. —The preceding unsigned comment was added by Blatyo (talk • contribs) 16:40, 6 April 2006 (UTC2)

I am also a student of Software Engineering, and we are currently doing research on building a specific model for incremental development. It differs greatly from iterative development. In ID, each iteration is like a mini-software lifecycle, with design, coding, and testing phases. Incremental development involves adding features in small chuncks, where each change produces valid, working software. The software is complete when all requirements are met. I will add more to the Incremental Development article once research paper is completed. —The preceding unsigned comment was added by 68.62.22.177 (talk • contribs) 2006-09-20T21:57:18.

---

Please sign your comments! --Bdoserror 22:15, 23 October 2006 (UTC)

[edit] What development models *aren't* iterative and incremental?

Obviously the 'evil' rigid waterfall model wasn't incremental, but it was never really advocated. It seems to me that all software development models, spiral on, have been iterative whenever possible. Could someone add an example or examples of development methodologies that don't fit in this category? If there aren't any, what use does this term serve? --Logomachist 03:40, 5 January 2007 (UTC)

• Was wondering this myself. 71.240.184.133 18:17, 31 January 2007 (UTC)

The waterfall model is apparently still used. The distinction should probably be that other models are designed to be incremental/iterative, while the waterfall model is not designed this way, but since software is rarely 100% right first time... --Michig 19:17, 31 January 2007 (UTC)