The myth of 'top-down' software development and its consequences for software maintenance

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.<
>