Software maintenance: don't chase problems; control them

For software maintenance, tools are available that help automate both reactive and active maintenance. Reactive maintenance involves responding to a problem, while active maintenance focuses on analyzing and updating applications in response to changing needs while the system is stable. Some static...

Full description

Saved in:
Bibliographic Details
Published inComputerworld Vol. 25; no. 12; p. 65
Main Authors Barnes, Geoffrey, Decherd, Bill
Format Magazine Article
LanguageEnglish
Published Framingham Computerworld, Inc 25.03.1991
Foundry
Subjects
Analysis
Automation
Codes
Engineering
Functions
Management
Manycompanies
Manyproducts
Modularity
Personal computers
Product Development
Readability
Repair & maintenance
Software
Software maintenance
Source Code
Specifications
United States > US
Online AccessGet full text
ISSN0010-4841

Cover

More Information
Summary:For software maintenance, tools are available that help automate both reactive and active maintenance. Reactive maintenance involves responding to a problem, while active maintenance focuses on analyzing and updating applications in response to changing needs while the system is stable. Some static analysis tools use metrics formulas to analyze program complexity. These tools calculate the complexity metrics, point out areas of the source program that might be subject to error, and make recommendations for improving the program. Pathvu from XA Systems Corp. is one such analysis tool. Sometimes, the best way to understand how a program works is to use an interactive code analyzer to watch it in action. One example is Via/Insight from Viasoft Inc. This tool allows a programmer to trace program execution flow while looking at the source code on an ISPF screen.
Bibliography:ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 23
ISSN:0010-4841