Content deleted Content added
m Subst: {{unsigned}} (& regularise templates) |
|||
| (16 intermediate revisions by 11 users not shown) | |||
Line 1:
{{WikiProject
{{WikiProject Computing|importance=Low}}
{{WikiProject Software|importance=Mid}}
}}
{{Talk header}}
{{Broken anchors|links=
* <nowiki>{{section link|DevOps|Incremental adoption}}</nowiki> The anchor (,DevOps,) has been [[Special:Diff/790936063,|deleted by other users]] before. <!-- {"title":"Incremental adoption","appear":{"revid":699982028,"parentid":698511770,"timestamp":"2016-01-15T17:08:02Z","replaced_anchors":{"Cultural Change":"Cultural change","Building a DevOps Culture":"Building a DevOps culture","Incremental Adoption":"Incremental adoption"},"removed_section_titles":["Cultural Change","Building a DevOps Culture","Incremental Adoption"],"added_section_titles":["Cultural change","Building a DevOps culture","Incremental adoption"]},"disappear":{"revid":790936063,"parentid":790935291,"timestamp":"2017-07-17T01:44:22Z","removed_section_titles":["Incremental adoption","CITEREFBhargava2014","CITEREFKim2013","CITEREFKim"],"added_section_titles":[]}} -->
* <nowiki>[[History of IBM#IBM Federal Systems Division .28FSD.29|new division within IBM]]</nowiki> The anchor (IBM Federal Systems Division (FSD)) [[Special:Diff/1182255066|has been deleted]]. <!-- {"title":"IBM Federal Systems Division (FSD)","appear":{"revid":702798624,"parentid":702797777,"timestamp":"2016-02-01T19:08:15Z","removed_section_titles":["IBM Federal Systems Division"],"added_section_titles":["IBM Federal Systems Division (FSD)"],"replaced_anchors":{"IBM Federal Systems Division":"IBM Federal Systems Division (FSD)"}},"disappear":{"revid":1182255066,"parentid":1182254941,"timestamp":"2023-10-28T04:01:15Z","removed_section_titles":["Organization","CEOs, Notable IBMers","IBM Global Services","IBM Research","IBM Federal Systems Division (FSD)","IBM service organizations"],"added_section_titles":[]}} -->
}}
== Move to Agile whatever is Agile and not about the Title topic ==
Folks are mistakenly putting content here that should go to [[Agile Software Development]]
Text is not describing title, it is stating that it's a key part of Agile, then first section
"The basic idea behind the agile method is", and many references listed here were lost
because they were agile so deleted as being Agile... People putting Agile content here is
a waste, put it where it will apply and be found.
[[User:Markbassett|Markbassett]] ([[User talk:Markbassett|talk]]) 17:27, 28 August 2012 (UTC)
== [[V model]] ==
What are the advantages of "V" Model over the other life cycle models. <small>—The preceding [[Wikipedia:Sign your posts on talk pages|unsigned]] comment was added by [[User:209.78.112.253|209.78.112.253]] ([[User talk:209.78.112.253|talk]] • [[Special:Contributions/209.78.112.253|contribs]]) 19:09, 19 January 2006 (UTC2)</small><!-- [Template:Unsigned2] -->
The proper place to see that is in the article about [[v_model]]
[[User:Markbassett|Markbassett]] ([[User talk:Markbassett|talk]]) 15:14, 28 August 2012 (UTC)
== Merge with [[Incremental build model]] ==
Line 21 ⟶ 39:
----
Please sign your comments! --[[User:Bdoserror|Bdoserror]] 22:15, 23 October 2006 (UTC)
The reason it is CURRENTLY hardly used is because it was used in the 1950s (the WWW did not exist at those times). Just because something does not have lots of search engine hits does not mean it did not exist or that it is not relevant.
Both incremental and iterative principles were born at about the same time and were used in large military projects together. It seems that the incremental part was adopted in civilian environments first (oldest written mention from 1957) and the iterative part was more widely adopted later (oldest written mention from 1968).
The military got the iterative part from other methodologies such as PDCA and PDSA. The incremental part was already in use for any large project since ages. So, it was a natural choice for the military. I have the sources but not the time to explain more or edit this article now. As a final statement, several Agile frameworks combine both. The iterative incremental development process is also called "EVOLUTIONARY" !! [[User:George Rodney Maruri Game|George Rodney Maruri Game]] ([[User talk:George Rodney Maruri Game|talk]]) 06:14, 7 July 2023 (UTC)
== What development models *aren't* iterative and incremental? ==
Line 57 ⟶ 79:
1975: [[Basili, V.]] and [[Turner, A.]], ''[[Iterative Enhancement: A Practical Technique for Software Development]]'' :[[IEEE]] Transactions on SW Eng.
1981: [[Barry Boehm|Boehm, B.]], ''[[software engineering economics|Software Engineering Economics]]'' Prentice-Hall. {{ISBN
1983: [[Booch, G.]], ''[[Software Engineering with Ada]]'' Benjamin-Cummings. (Around page 43) describes an iterative process for growing an object-oriented system.
Line 121 ⟶ 143:
I did not find velocity (factor to calculate actual development time from workdays) in any software engineering topic. I think this is a very important term and should be explained somewhere (or rather, should even have its own topic). I'd be glad if someone could add this. Kind regards -- [[User:Mafutrct|mafutrct]] ([[User talk:Mafutrct|talk]]) 11:10, 11 November 2009 (UTC)
== The image of Iterative development may be misleading ==
The image is rather a good illustration of an incremental development, and not iterative. We see increments within phases, we do not see iterations.
It is quiet common procedure to execute more than just one iteration, in order to achieve the amount of software desired for one increment. This can not be seen here, and the first misleading impression can be, iteration and increment are the same. <small><span class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:MarekLewandowski|MarekLewandowski]] ([[User talk:MarekLewandowski|talk]] • [[Special:Contributions/MarekLewandowski|contribs]]) 08:20, 27 July 2011 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
== Merge from Incremental build model ==
It seems to me as if there is no good reason to have a separate article at [[Incremental build model]]. --[[User:Slashme|Slashme]] ([[User talk:Slashme|talk]]) 12:32, 22 August 2011 (UTC)
: There is a naming problem here, not just an overlap for merging. What's a "build model"? IMHE (not actually that humble, this has been my day job for years), a "build model" is a manufacturing process within software development, as for [[software build]]. The design process is not referred to under that same name. So the article we have at [[Incremental build model]] talks about the design evolution, just as this article at [[Iterative and incremental development]], and it's sourced by sources that don't apply the term "build" to it either. It's thus a good target for merging, and the name isn't appropriate to preserve as a redirect.
: If we are to have an article on [[incremental build]], then this should be (probably a redirect to a section within [[software build]]) an article on the build technique of building by incremental compilation of changed modules, and the need to manage their inter-dependencies. It's a good topic, but it's then of little relation to [[Iterative and incremental development]]. [[User:Andy Dingley|Andy Dingley]] ([[User talk:Andy Dingley|talk]]) 11:44, 7 January 2013 (UTC)
* {{agree}}. Merge [[Incremental build model]] into [[Iterative and incremental development]]. {{emdash}} {{user|Aaditya 7}} {{time}}
* {{disagree}}. Both incremental and iterative principles were born at about the same time and were used in large military projects together but subsequently they were adopted separatedly. It seems that the incremental part was adopted in civilian environments first (oldest written mention from 1957) and the iterative part was more widely adopted later (oldest written mention from 1968). The military got the iterative part from other methodologies such as PDCA and PDSA. The incremental part was already in use for any large project since ages. So, it was a natural choice for the military. I have the sources but not the time to explain more or edit this article now. As a final statement, several Agile frameworks combine both so, everything just came back to its roots. The iterative incremental development process is also called evolutionary as I have also mentioned here. [[User:George Rodney Maruri Game|George Rodney Maruri Game]] ([[User talk:George Rodney Maruri Game|talk]]) 06:44, 7 July 2023 (UTC)
== Alternative name: EVOLUTIONARY ==
Another name for this development model is EVOLUTIONARY. Please, add this datum to the article.
https://dspace.mit.edu/bitstream/handle/1721.1/80490/42757317-MIT.pdF
https://www.geeksforgeeks.org/software-engineering-evolutionary-model/
[[User:George Rodney Maruri Game|George Rodney Maruri Game]] ([[User talk:George Rodney Maruri Game|talk]]) 06:24, 7 July 2023 (UTC)
== "Contrast with Waterfall development" section is misleading ==
That's some pretty broad statements there that have no evidence like Waterfall needing more human resources than incremental, and Waterfall being unsuitable for small projects. There are counterexamples in real life for these two and other points from this section. I'd add the evidence or delete the section. [[Special:Contributions/2003:DB:4F0C:7196:9DB8:E58A:C6AB:D197|2003:DB:4F0C:7196:9DB8:E58A:C6AB:D197]] ([[User talk:2003:DB:4F0C:7196:9DB8:E58A:C6AB:D197|talk]]) 16:38, 11 July 2023 (UTC)
| |||