A Case Study in Software Maintenance
Susan A. Dart, Alan M. Christie, Alan W. Brown
Abstract
Susan A. Dart, Alan M. Christie, Alan W. Brown
Abstract
In an effort to find out more about the tools, procedures, and techniques project personnel use in their work, the Computer-Aided Software Engineering(CASE) Environments Project interviewed personnel in eight software maintenance projects within an agency of the U.S/government. These interviews highlighted problems that we believe are typical of many software maintenance organizations (i.e., the need for more effective software maintenance tools, lack of communication between individuals working on similar projects, low status of maintenance personnel, and lack of a design-for-maintenance philosophy during the software development phase). This report highlights the findings of these interviews, provides our analysis of the findings, and makes recommendations directed at the agency for improvement in the areas of tools, people, and process. We believe that what we observed is very typical of the state of the practice in these areas and as such that this report and its recommendations are applicable to other large or small software maintenance projects.... CASE tools, Environments, Computer-aided software, Software maintenance, Engineering environments
OpenAlex reports 19 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
In an effort to find out more about the tools, procedures, and techniques project personnel use in their work, the Computer-Aided Software Engineering(CASE) Environments Project interviewed personnel in eight software maintenance projects within an agency of the U.S/government. These interviews highlighted problems that we believe are typical of many software maintenance organizations (i.e., the need for more effective software maintenance tools, lack of communication between individuals working on similar projects, low status of maintenance personnel, and lack of a design-for-maintenance philosophy during the software development phase). This report highlights the findings of these interviews, provides our analysis of the findings, and makes recommendations directed at the agency for improvement in the areas of tools, people, and process. We believe that what we observed is very typical of the state of the practice in these areas and as such that this report and its recommendations are applicable to other large or small software maintenance projects.... CASE tools, Environments, Computer-aided software, Software maintenance, Engineering environments
Key concepts: Computer science, Software, Software engineering, Software maintenance, Programming language, Software development