Reengineering Technology Report. Volume 1.
Abstract
The purpose of this report is to increase contact, awareness, and understanding of software reengineering tools. Use of this report should be the first step in transferring effective software reengineering processes, methods, and tools into practical use. The targets of this report are organizations responsible for the development and maintenance of computer software. This report defines the ideas of software reengineering and identifies their value in improving software quality for embedded, MCCR, and MIS applications. It explains how the features of current reengineering tools can improve software development and maintenance. It includes information about specific products in the marketplace. The information is aimed at those who must make the decisions about acquiring advanced technology and prepare their organizations to use it effectively. Also, this report attempts to identify the future directions of the field to help in planning long-range strategies. Because a reengineering effort involves large amounts of code and a significant percentage of a system (if not the entire system), it may be necessary to move to Ada. The official Air Force policy states 'Ada is required when more than one-third of the existing code is altered (excluding COTS) at any one time. Under one-third waiver not required System managers are encouraged to move to Ada with any software or hardware upgrade. Programming Languages Policy 5.c, 7 Aug 90 The STSC supports this policy and believes that converting to Ada during the reengineering process is the opportune time to comply with the Ada mandate.
Document Details
- Document Type
- Technical Report
- Publication Date
- Oct 01, 1995
- Accession Number
- ADA324749
Entities
People
- Michael R. Olsem