this article was given at ECOOP '93.

This paper describes work performed for the IDENT project which is concerned with the identification and encapsulation of reusable modules. The aim of the project is to look at the integration of two methods for supporting maintenance; RE 2 and RECAST. In this paper we describe a case study where we try to extract reusable modules from a 21,000 line COBOL program. We approach this through the use of some of the basic methods addressed by the RE 2 reuse reengineering paradigm and some of the stages of the reverse engineering RECAST method. We have found that the identification of modules is very difficult because of high connectivity between data items. In order to deal with this problem we identify a number of strategies for removing particular data items using some of the RECAST stages and steps. These include the logical data model and system processing steps. However, in most cases we have found that such approaches were insufficient and that expert domain knowledge is also required...

This paper describes the process whereby we investigate the implementation of non-functional requirements and their implications on the reengineering process. Our work has so far concentrated on the identification of reusable units from existing legacy systems. However, the results from our approaches so far have found that the functionality is difficult to separate into separate units. We have found that certain aspects of the code tend to hold the units together. In this paper, we propose that these aspects be the implementation of non-functional requirements, and, that if these aspects can be filtered out, larger and more reusable object would be obtained through the use of reuse reengineering approaches. This paper describes the process by which we identify the non-functional requirements and evaluates the usefulness of the process through a number of case studies. 1. Introduction Support for software maintenance is of great significance because of the high cost of maintaining exi...

In this paper, we discuss the general area of software development for reuse and reuse guidelines. We identify, in detail, language-oriented and domain-oriented guidelines whose effective use affects component reusability. This paper also proposes a tool support which can provide advise and can generate reusable components automatically and it is based on domain knowledge (reuse guidelines represented as domain knowledge).