The myth of 'top-down' software development and its consequences for software maintenance
- 7 January 2003
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
Abstract
Four case studies in which the top-down transformation approach has led to significant maintenance problems are presented. All of these had to do with the derivation of programs from a requirements specification, an approach advocated by most CASE tools. It is explained why this approach failed and the lessons derived from such experiences are discussed. It is suggested how software reengineering may help to remedy the situation.Keywords
This publication has 14 references indexed in Scilit:
- A spiral model of software development and enhancementComputer, 1988
- Box structured information systemsIBM Systems Journal, 1987
- The last 10 percentIEEE Transactions on Software Engineering, 1986
- Abstraction-based software developmentCommunications of the ACM, 1986
- An overview of JSDIEEE Transactions on Software Engineering, 1986
- Reusability in Programming: A Survey of the State of the ArtIEEE Transactions on Software Engineering, 1984
- Software Renewal: A case StudyIEEE Software, 1984
- Life cycle concept considered harmfulACM SIGSOFT Software Engineering Notes, 1982
- Stop the life-cycle, I want to get offACM SIGSOFT Software Engineering Notes, 1982
- The entity-relationship model—toward a unified view of dataACM Transactions on Database Systems, 1976