A Comparative Analysis of Traditional Software Engineering and Agile Software Development
Authors:
- Ashley AitkenAAAshley Aitken
- Vishnu IlangoVIVishnu Ilango
- 1 January 2013
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15301605,p. 4751-4760
Abstract
Over the last decade (or two) the pendulum of developer mindshare has swung decidedly towards agile software development from a more traditional engineering approach to software development. To ascertain the essential differences and any possible incompatibilities between these two software development paradigms this research investigates a number of traditional and agile methodologies, methods, and techniques. The essential differences between traditional software engineering and agile software development are found not to be (as one may first suspect from a cursory consideration) related to iteration length or project management, but rather more related to other attributes like the variety of models employed, the purpose of the models, and the approach to modeling. In the end though the two approaches are not seen to be incompatible, leading to the future possibility of an Agile Software Engineering (ASE).Keywords
This publication has 13 references indexed in Scilit:
- Lean Software DevelopmentIEEE Software, 2012
- Software Engineering: An Idea Whose Time Has Come and Gone?IEEE Software, 2009
- Software development: what is the problem?Computer, 2007
- The Demise of the Waterfall Model Is Imminent, and Other Urban MythsQueue, 2004
- Professional software engineering: fact of fiction? [Guest Editorial]IEEE Software, 1999
- When are methods complementary?Information and Software Technology, 1999
- Using a defined and measured Personal Software ProcessIEEE Software, 1996
- Software's Chronic CrisisScientific American, 1994
- A spiral model of software development and enhancementComputer, 1988
- Prototyping: The New Paradigm for Systems DevelopmentMIS Quarterly, 1982