Content deleted Content added
m computing project |
|||
Line 32:
The definition (the first sentence) is no definition. It only states why this topic exists and where it is used - but not what is ment by iterative and incremental development. --[[User:Sebastian Dietrich|Sebastian Dietrich]] 09:23, 24 May 2007 (UTC)
==History==
I moved the following section to the talk page here. There is a cleanup tag for two year now. This should first be improved before replacing this section. -- [[User:Mdd|Marcel Douwe Dekker]] ([[User talk:Mdd|talk]]) 23:59, 9 October 2008 (UTC)
{{Cleanup|date=October 2006}}
For the June 2003 IEEE Computer issue dedicated to agile methods (edited by A. Cockburn and L. Williams), Vic Basili and CraigLarman are writing a short 1-2 page history of iterative/incremental lifecycle processes.
1970: [[W. W. Royce|Royce, W.W.]], ''[[Managing the Development of Large-Scale Software: Concepts and Techniques]]'' Proceedings, Wescon, August 1970 (also reprinted in Proceedings, ICSE9), which includes a "build it twice" prototyping step -- entered by [[Barry Boehm]]
1971: [[Mills, H.]], ''[[Top-down programming in large systems]]'' Debugging Techniques in Large Systems, R. Rustin, ed., Englewood Cliffs, N.J., Prentice-Hall, 1971. (Frederick Brooks mentions this in NoSilverBullet: "Some years ago Harlan Mills proposed that any software system should be grown by incremental development.") - entered by [[Christian Ohman]]
1973: [[Mills, H.]], ''[[On the Development of Large, Reliable Programs]]'' IEEE Symp. Comp. SW Reliability. Notes: I have heard this paper has relevance to iterative, but haven't read it yet. - CraigLarman
1975: [[Williams, R.D.]], ''[[Managing the Development of Reliable Software]]'' Proceedings, 1975 International Conference on Reliable Software, [[Association for Computing Machinery|ACM]]/[[IEEE]], April 1975, pp.3-8.
:Discusses the use of incremental development on the $100M TRW/Army Site Defense software project for ballistic missile defense. The project began in February 1972 and developed the software in 5 loops or increments of functional capability. Loop 1 just did tracking of a single object; Loop 5 covered the full mission. -- entered by BarryBoehm
1975: [[Fred Brooks|Brooks, F.]], [[The Mythical Man-Month]]
:"Plan to throw one away; you will, anyhow." - entered by PhilippeKruchten
:Please note that Brooks writes in The Mythical Man-Month after 20 years: "This I now perceive to be wrong, not because it is too radical, but because it is too simplistic.
:The biggest mistake in the "Build one to throw away" concept is that it implicitly assumes the classical sequential or waterfall model of software construction."
:The problem is that you only will know what parts to throw away after the system is finished and the system testing is over. - ChristianOhman
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 0-13-822122-7 (pages 41-2, 254) allows for an iterative process when developing software.
1983: [[Booch, G.]], ''[[Software Engineering with Ada]]'' Benjamin-Cummings. (Around page 43) describes an iterative process for growing an object-oriented system.
1984: [[Madden, W and Rone, K.]], ''[[Design, Development, Integration: Space Shuttle Primary Flight Software System]]'', CACM 27 9, Sept 1984, 914-925.
:-- Although the publication was only in 1984, they used an iterative approach in 1977-79..
:"An implementation approach was devised for STS-1, which met the objectives by applying the ideal cycle (they mean the waterfall cycle), to small elements of the overall software package on an iterative basis. ... STS-1 had 17 interim release drops in a 31-month period starting October 1977. Full software capability was provided after the 9th release in December 1978." - PhilippeKruchten
1984: [[Rzevski, G.]], ''[[Prototypes Versus Pilot Systems: Strategies For Evolutionary Information Systems Development]]'', Approaches to Prototyping, Editors Budde et al, Springer-Verlag
1985: [[Barry Boehm|Boehm, B.]], ''[[A Spiral Model Of Software Development And Enhancement]]'', 2nd. International Software Process Workshop. Coto de Caza, Trabuco Canyon, USA 1985. Wileden, J. and Dowson, M. (Eds.)
:Notes: I'm not sure this citation is correct. - CraigLarman; PhilippeKruchten can offer this alternate:
1986: [[Barry Boehm]], ''[[A Spiral Model of Software Development and Enhancement]]'', ACM SIGSOFT Software Engineering Notes (SEN), August 19–6 1985: [[Rzevski, G.]], ''[[Trends in Information Systems Design]]'', Infotech State of the Art Review, [[Mature Systems Design]], edited by L. Evans, Pergamon Press
1986: [[Currit, P. Allen]], [[Dyer]], Michael and [[Harlan Mills|Mills, Harlan D]], ''[[Certifying the Reliability of Software]]'' [[IEEE]] TOSE, Vol. SE-12, No. 1, Jan86.
:Notes: pp 3-11. Executable product increments are the basis for MTTF estimates. - TomGilb
1988: [[Tom Gilb|Gilb, T]] ''[[Principles of Software Engineering Management]]'' AW.
:Notes: This had three chapters on Evolutionary Dev. - CraigLarman
1988: Brigader General [[H Edward]] USA (ret.), ''[[Evolutionary Acquisition of Command and Control Systems: Becoming a Reality]]'' Signal, January 1988
:Notes: pp 23-26 Found this reference in SPUCK93 (JPL, RDM) - TomGilb
1988: [[Barry Boehm|Boehm, B]], ''[[A Spiral Model Of Software Development And Enhancement]]'' [[IEEE Computer]]. May 1988.
1991: [[Booch, G]], ''[[Object-oriented Analysis and Design with Applications]]'' Addison-Wesley
:Describes a process for iteratively and incrementally growing a system.
1992: [[Ph. Kruchten]], ''[[Un Processus de Développement de Logiciel Itératif et Centré sur l'Architecture]]'' 4e Congrès de Génie Logiciel, Toulouse, France, Décembre 1991, EC2, Paris
:Iterative approach the "Rational way" (English version exists as a whitepaper from Rational) - PhilippeKruchten
1993: [[Alistair Cockburn]], ''[http://www.research.ibm.com/journal/sj/323/ibmsj3203E.pdf The Impact of Object-Orientation on Application Development] (PDF)'' IBM Systems Journal, 32(3), March 1993, pp. 420-444, reprinted in the 50-year anniversary issue, IBM Systems Journal 38(2-3), 1999. http://www.research.ibm.com/journal/sj38-23.html,
:Presents one view of the difference between ''incremental'' and ''iterative'' development (p. 311)
1996: [[Ph. Kruchten]], ''[[A Rational Development Process]]'' Crosstalk, 9 (7) July 1996, pp.11-16.
:(see [http://www.stsc.hill.af.mil/crosstalk/frames.asp?uri=1996/07/rational.asp])
:What will become the RUP lifecycle. - PhilippeKruchten
1996: [[Barry Boehm|Barry W. Boehm]], 1996, ''[[Anchoring the Software Process]]'' [[IEEE Software]], July 1996, pp.73-82.
:where MBASE and RUP aligns concepts and terminology. - PhilippeKruchten
1996: [[Grady Booch|Booch, G]], ''[[Object Solutions]]'' Addison-Wesley.
:Explains the importance and substance of an iterative and incremental lifecycle; talks about the growing of an architecture through successive refinement; introduces the notion of different rhythms (micro and macro process) in the lifecycle. About the same time there was a book by Adele Goldberg and Kenny Rubin of a similar nature. Alistair Cockburn's "SOOP" book followed shortly afterwards.
1998: [[Jennifer Stapleton]], ''[[DSDM: Dynamic Systems Development Method]]'' Addison-Wesley
1998: [[Walker Royce]], ''[[Software Project Management?A Unified Framework]]'', Addison-Wesley-Longman
1999: [[Beedle, Mike]]; [[Devos, Martine]]; [[Sharon, Yonat]]; [[Schwaber, Ken]]; [[Sutherland, Jeff]]. ''[[SCRUM: An extension pattern language for hyperproductive software development]]''. In Harrison, Neil; Foote, Brian; Ronhert, Hans (Eds.) Pattern Languages of Program Design 4. Addison-Wesley Software Patterns Series.
1992: [[Ivar Jacobson|Jacobson, Ivar]], ''[[Object-Oriented Software Engineering: A Use Case Driven Approach]]''. Chapter 2, The system life cycle.
:In my edition, Addison-Wesley revised 1998, pp 23ff. --StevenNewton
1997 [[Alistair Cockburn]], ''[http://alistair.cockburn.us/index.php/Using_VW_staging_to_clarify_spiral_development Using VW Staging to Clarify Spiral Development]''
| |||