A spiral model of software development and enhancement
ACM SIGSOFT Software Engineering Notes
Prototyping a Process Monitoring Experiment
IEEE Transactions on Software Engineering
Software Magazine
Extreme programming explained: embrace change
Extreme programming explained: embrace change
SNOBOL , A String Manipulation Language
Journal of the ACM (JACM)
Agile software development
Commonality and Variability in Software Engineering
IEEE Software
Process Improvement - The Way Forward
CAiSe '95 Proceedings of the 7th International Conference on Advanced Information Systems Engineering
Integration and Evolution of Model-Based Tool Prototypes
RSP '00 Proceedings of the 11th IEEE International Workshop on Rapid System Prototyping (RSP 2000)
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
A major justification for the agile class of software processes is that customer requirements often change substantially during development, with the result that developers must work with a ever-changing specification. The best way of dealing with this, it is claimed, is a process including adaptive and iterative steps allowing the code under development to change to meet an evolving requirement. In this paper, we use quantitative process data to argue that the deliberate development of an evolvable design, based upon extensions and variations to the requirements, and the generality derivable from the implemented system, may provide agility within a more traditional development, showing that the two concepts are interchangeable, to some extent. In doing so, the paper draws upon our joint work on evolvable systems, and upon a concept developed by one of us in the 1980's, "The Contraction of Generality", to illustrate the alternatives.