Any response to the software maintenance challenge must address the underlying problem of program understanding. One way of doing this is through reverse engineering. A successful approach to reverse engineering must be both flexible and scalable. Most rev
Domain-Retargetable Reverse Engineeringy Scott R. Tilley Hausi A. Muller Michael J. Whitney Kenny Wong Department of Computer Science, University of Victoria P.O. Box 3055, Victoria, BC, Canada V8W 3P6 Tel: (604) 721-7294, Fax: (604) 721-7292 E-mail: fstilley, hausi, mwhitney, kenwg@csr.uvic.ca
Abstract Any response to the software maintenance challenge must address the underlying problem of program understanding. One way of doing this is through reverse engineering. A successful approach to reverse engineering must be both exible and scalable. Most reverse engineering tools provide a xed palette of analysis, extraction, organization, representation, and selection techniques. This paper describes a userprogrammable approach to reverse engineering. The approach uses a scripting language that enables users to write their own routines for these activities, making the system domain-retargetable. The environment supported by this programmable approach subsumes existing reverse engineering systems by being able to simulate facets of each one, and provides a smooth transition from semi-automatic to automatic reverse engineering.
Keywords: domain-retargetable, program understanding, reverse engineering, software maintenance
1 Introduction The primary business of software engineering has historically been new development; now it is maintenance 1]. This fundamental shift was inevitable: the software profession has reached a turning point, y This work was supported in part by the British Columbia Advanced Systems Institute, IBM Canada Ltd., the IRIS Federal Centres of Excellence, the Natural Sciences and Engineering Research Council of Canada, the Science Council of British Columbia, and the University of Victoria.
Copyright c 1993 IEEE. Reprinted, with permission, from CSM '93: The 1993 Conference on Software Maintenance, (Montreal, Quebec; September 27-30, 1993), pages 142-151. IEEE Computer Society Press (Order Number 4600-02).
one where more people are employed to maintain existing applications than to develop new systems from scratch. Traditional approaches to the software process have placed too much emphasis on the arti cial distinction between development and maintenance. A better term is software evolution, which refers to the on-going enhancements of existing software systems, involving both development and maintenance. Since evolution begins early in the development phase, the distinction between development and maintenance should be abandoned in favor of an evolutionary process 2, 3]. In fact, learning to master evolving systems was recently identi ed as paramount for future software engineering research 4]. Central to the software evolution challenge is program understanding. For large legacy systems,1 this is a very di cult task. Unless one has been with a project since its inception, there is little chance of understanding a multi-million line program without considerable e ort|if at all. Perhaps if the overall structure and maintenance
history of the subject system had been better documented, program understanding would be easier. Unfortunately, systems that fall into this category are the exception rather than the rule. Without such information, a maintainer must rely on disparate and informalsources of information as an aid in program understanding. Ultimately, it is the source code that is the sole objective arbiter 5]. Maintenance personnel are forced to spend an inordinate amount of time attempting to create an abstract representation of the system's high-level architecture by exploring its low-level source code|not an easy task for large systems. One way of augmenting this understanding process is through reverse engineering.2 Our approach to reverse engineering involves extracting system abstractions and design information from existing software systems. This information can 1 Legacy software systems are those that are 10-25 years old and often in poor condition because of prolonged maintenance. 2 Speci cally, authorized reverse engineering of one's own code. We do not advocate improper reverse engineering of source code when one does not have the right to do so.
Hibernate Reverse Engineering详细描述_IT/计算机_专业资料。Hibernate Reverse ... Programmable reverse e... 163页 免费 Learning Reverse Engin... 263页 ...
Programmable reverse eng... 163页 免费 Learning Reverse Enginee... 263页 免费 Hibernate Reverse Engine... 2页 1财富值 Reverse Engineering Patt... 52...
Programmable reverse eng... 163页 免费 Learning Reverse Enginee... 263页 免费 Reverse Engineering Patt... 52页 免费 Hibernate Reverse Engine... 2页 ...
Programmable reverse eng... 163页 免费 Learning Reverse Enginee... 263页 免费 Reverse Engineering Patt... 52页 免费 Reverse engineering garm... 12页 ...
//www.rigi.csc.uvic.ca/ – a research prototype that represents an open and public domain reverse engineering tool – user programmable – analysis for:...
Aspect-oriented software reverse engineering_专业资料。维普资讯 http://www.cqvip.com JunlfSaga nvri(nlhEio)20,05:048ora hn ...
【江苏省自然科学基金】_reverse engineering_期刊发文热词逐年推荐_20140815_数学_自然科学_专业资料。2009年 序号 1 2 3 4 5 6 7 8 9 科研热词 量子点 ...
Reverse engineering mode... 8页 2财富值 The Law and Economics of... 89页 10财富值 Reverse_Engineering 5页 2财富值 Programmable reverse eng... 10...
proe逆向工程_REX_ 28页 免费 Reverse Engineering is R... 12页 10财富值 数据处理点云处理 3页 1财富值 Programmable reverse eng... 10页 免费...
热门文档