Iterative and incremental developments. a brief history
By Craig Larman, Victor R. Basili. 2003
377 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/ad17c82ae6447979e31120de0eec921ec1595233
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- J. Magee
- J. Kramer
- Ladan Tahvildari
- Torgeir Dingsøyr
- Fátima Poza-Vilches
- Abigail López-Alcarria
- Alberto Olivares-Vicente
- Sam Malek
In Information Systems
- J. Magee
- J. Kramer
- Tore Dybå
- Torgeir Dingsøyr
- Ladan Tahvildari
- Fátima Poza-Vilches
- Abigail López-Alcarria
- Alberto Olivares-Vicente
Citations in the corpus
- A Systematic Review of the Use of Agile Methodologies in Education to Foster Sustainability Competencies (2019, methodology): “Different experiences with quick incremental definition-execution-evaluation-correction production cycles can be tracked back to the 1950s based on a publication from 2003 by Craig Larman and Victor Basili [8] in which they describe having worked with incremental development technologies at IBM in 1”
- Continuous software engineering: A roadmap and agenda (2017, background): “Other authors, including Royce who documented the waterall approach, also argued that the waterfall approach does not work or any but the most trivial systems (Larman and Basili, 2003; Peersen and Wohlin, 2010; Royce, 1987).”
- Empirical studies of agile software development: A systematic review (2008, methodology): “In an article that describes the history of iterative and incremental development, Larman and Basili [40] identify Dynamic Systems Development Method (DSDM) [60] as the first agile method, followed by extreme programming (XP) [9], which originated from the Chrysler C3 project in 1996 [5].”
- Software Engineering for Self-Adaptive Systems: A Second Research Roadmap (2010, methodology): “This awareness has impacted software process models to better address the inherent need for change and evolution by introducing iterative, incremental, and evolutionary approaches to software development as an alternative to strictly separating sequenced disciplines of requirements engineering, desi”