Transferring re-engineering technology to a software development and maintenance organization: an experience report
- 1 January 1994
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 100-108
- https://doi.org/10.1109/icsm.1994.336785
Abstract
Technology transfer does not happen spontaneously after research results and prototypes have been demonstrated. Researchers need to get more actively involved in "pushing technology out of the door." This paper describes an experiment that we conducted in 1993 to facilitate technology transfer. There are two aspects of this experiment: the integration of a re-engineering process into an existing software development and maintenance organization; and the evaluation of a research prototype in a "real world" situation. The experiment resulted in recommendations on adaptation of the tool functionality and on a configuration for use by different teams within the target organization.Keywords
This publication has 9 references indexed in Scilit:
- SRE: A Knowledge-based Environment For Large-scale Software Re-engineering ActivitiesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2005
- COBOL/SRE: A COBOL System Renovation EnvironmentPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software-engineering research revisitedIEEE Software, 1993
- High-pressure steam engines and computer softwarePublished by Institute of Electrical and Electronics Engineers (IEEE) ,1992
- BAL/SRW: Assembler re-engineering workbenchInformation and Software Technology, 1991
- Reverse engineering and design recovery: a taxonomyIEEE Software, 1990
- A micro/macro measure of software complexityJournal of Systems and Software, 1987
- The magic number eighteen plus or minus threeACM SIGSOFT Software Engineering Notes, 1984
- A Complexity MeasureIEEE Transactions on Software Engineering, 1976