Change Driven Development

Change Driven Development (CDD) is introduced in my Phd Thesis, as an agile development process or agile approach for maintaining Scientific Legacy Software written in Fortran. This approach to software development is based on:

• Software Essence (changeability, complexity, invisibility and conformity) described by Frederick P. Brooks in "No Silver Bullet: Essence and Accidents of Software Engineering," IEEE Computer, Vol. 20, No. 4 (April 1987) pp. 10-19. a must read article.
• Integrated development tools in order improve the developer's work process and to reduce some aspects that bring alone the use of not integrated tools such as vi, notepad, emacs among others. The use of simple text editors are not enough in programming.
• Source Code Transformations are required and should be integrated in an all-in-one IDE such as eclipse, Microsoft Visual Studio, NetBeans among other. Ralph Johnson explains the source code transformation's value in his article "Software development is program transformation" (2010).
• An Iterative and Incremental Process, in the case for CDD the IIP is performed by applying a cycle of four stages: Understand -> Transform -> Verify -> Review to start another cycle modified or improved by the last stage.

to be continued...

Note: please do not mistake with plan-driven or change-drive approaches. This is a software development process proposal.