软件再工程浅谈

本文介绍了软件再工程的概念，分析了为什么要实施软件再工程的原因，简单叙述了实施软件再工程的策略和步骤。     

“软件再工程”的应用研究

软件再工程是针对现阶段软件系统更新换代加剧而提出的,当前用户需求不断变化、软件系统复杂性不断提高和软件维护日趋困难促进了软件再工程的发展。     

基于Java的软件再工程支持工具研究

Internet的发展和构件化的软件开发为再工程指明了新的方向。面向对象软件再工程将以构件库为中心,并关注于将遗产系统改造为B/S结构的Internet应用。论文提出了一个面向对象软件再工程模型,分析了面向对象软件再工程支持工具的特性,然后介绍了基于Java的再工程支持工具原型。     

基于软件体系结构的再生工程的设计与实现

如何把旧的系统再生为新系统已经成为目前软件工程领域所关注的问题。本文基于软件复用技术,提出一种切实可行的方法———基于软件体系结构,将旧的系统转化成满足新需求并有良好扩展性的系统,并在通信网络规划软件的开发中实践并验证了这一方法。实践表明:通过该方法大大缩短了软件再工程过程的时间,节约了成本,并能够在最大限度上满足用户的需求,实现了高速度、高质量的开发。     

Agent在系统仿真软件再工程中的应用

基于Agent的建模和仿真技术在复杂系统和复杂性研究中得到广泛的应用,并且由此产生了许多的系统仿真软件,这些软件的维护将会成为问题.为解决这个问题并利用Agent技术在建模和仿真领域的优势,理想的方法是将Agent技术和思想也应用于系统仿真软件再工程中的各个阶段.提出基于Agent的系统仿真软件再工程方法,旨在降低维护的难度,提高再工程效率和建模的准确性,并提高软件的可维护性.该方法应用在森林植被仿真系统的第二次再工程实践,与第一次的传统的实现方法进行对比,可以证明其可行性和优势,并为相似系统的再工程提供了参考.     

软件再工程助手

随着越来越多成功的软件系统成为遗留系统,软件再工程已日益显现其重要性。但对原系统理解的难度影响了软件工程师对原系统进行再工程的效率,特别是从源代码获取设计规约。在软件维护和软件再工程中大量的工作是围绕着源代码的变换,这种变换将程序代码文本或规约文本从一种形式转变成另一种形式,从而使其具有更好的可读性和可理解性。论文介绍了作者与英国DeMontfort大学的研究人员开发的一个非常方便的用于从程序抽取规约(也就是从源代码文本到规约文本的变换)的再工程助手(RA)工具,并使用RA进行一个实例研究。     

逆向工程和再工程在软件预防性维护中的应用

过去在进行软件开发的时候，没有采用科学合理的方法，尤其没有重视原始文档的保存与整理，从而导致了软件危机的产生。为了更好地维护现行软件，有必要理解其内部的逻辑结构，进而根据新的要求，做出相应的维护。这就是软件维护的逆向工程和再工程．本文时此进行了讨论．     

逆向工程和再工程在软件预防性维护中的应用

过去在进行软件开发的时候,没有采用科学合理的方法,尤其没有重视原始文档的保存与整理,从而导致了软件危机的产生。为了更好地维护现行软件,有必要理解其内部的逻辑结构,进而根据新的要求,做出相应的维护。这就是软件维护的逆向工程和再工程,本文对此进行了讨论。     

浅议软件再工程

软件再工程概念是针对现阶段软件系统更新换代加剧而提出的,当前用户需求不断变化、软件系统复杂性不断提高和软件维护日趋困难促进了软件再工程的发展。侧重于软件再工程的概念、目标、类型而提出了相应可供参考的模型,针对结构化思想和面向对象思想设计的软件系统提出了一般的软件再工程实施模型。     

采用形式化技术的软件再工程

形式化技术为软件再工程提供了完备的理论基础,该文对基于软件再工程的形式化方法进行了探讨,提出了一个统一的面向软件再工程的形式化方法。     

On the Automatic Recovery of Style-Specific Architectural Relations in Software Systems

The cost of maintaining a software system over a long period of time far exceeds its initial development cost. Much of the maintenance cost is attributed to the time required by new developers to understand legacy systems. High-level structural information helps maintainers navigate through the numerous low-level components and relations present in the source code. Modularization tools can be used to produce subsystem decompositions from the source code but do not typically produce high-level architectural relations between the newly found subsystems. Controlling subsystem interactions is one important way in which the overall complexity of software maintenance can be reduced.We have developed a tool, called ARIS (Architecture Relation Inference System), that enables software engineers to define rules and relations for regulating subsystem interactions. These rules and relations are called Interconnection Styles and are definedusing a visual notation. The style definition is used by our tool to infer subsystem-level relations in designs being reverse engineered from source code.In this paper we describe our tool and its underlying techniques and algorithms. Using a case study, we describe how ARIS is used to reverse engineer high-level structural information from a real application.     

A Case Study of Maintenance of a Commercially Fielded Case-Based Reasoning System

This article is a case study of the maintenance required to the case base of a commercially fielded case-based reasoning (CBR) system that provides support for HVAC engineers enabling them to better specify HVAC installations. The article briefly describes the system and details how the case base grew rapidly, causing a problem of case redundancy. A simple algorithm to identify and remove redundant cases is described, along with the results of applying it to the case base. Case obsolescence also was encountered and partially remedied using DBMS techniques. The article analyzes the case-base maintenance (CBM) required by the system in terms of Richter's knowledge containers and Leake and Wilson's CBM framework and contrasts this case study with experience from NEC and DaimlerChrysler. The article observes that had maintenance of the case base been considered more explicitly during system design and implementation, some of the resulting maintenance would have been unnecessary. The article concludes by identifying lessons learned and highlighting the relationship between the sophistication of the case-representation and similarity metrics and the ease with which CBM can be undertaken by nontechnical staff. This relationship does not always work in favor of the maintainer.     

A Case Study in Software Reuse

We report on a term project to conduct domain engineering followed by application engineering for a specific set of applications. We discuss some of the observations we have made on this project, as well some of the lessons we have learned.     

关键控制软件逆向工程技术研究

随着软件工程技术的发展和软件遗产系统(legacysystem)的增多,在上世纪80年代,出现了程序理解(ProgramCompre-hension),在上世纪90年代,过渡到逆向工程。本文就开展关键控制软件逆向工程的经验以及一些技术问题进行讨论,希望起到抛砖引玉的作用,引起同行对逆向工程工作的关注,促进逆向工程工作的进一步发展。     

Restructuring Software: A Case Study

We use knot count and path count metrics to identify which routines in the Level 1 basic linear algebra subroutines (BLAS) might benefit from code restructuring. We then consider how logical restructuring and the improvements in the facilities available from successive versions of Fortran have allowed us to improve the complexity of the code as measured by knot count, path count and cyclomatic complexity, and the user interface of one of the identified routines which computes the Euclidean norm of a vector. With these reductions in complexity we hope that we have contributed to improvements in the maintainability and clarity of the code. Software complexity metrics and the control graph are used to quantify and provide a visual guide to the quality of the software, and the performance of two Fortran code restructuring tools is reported. Finally, we give some indication of the cost of the extra numerical robustness offered by the BLAS routine over the use of new Fortran 90 intrinsic functions.     

营造个体软件工程规程

软件产品的开发都是由个体软件工程师完成的,因此能否具有有效的个体软件工程规程会直接影响到产品开发的效率、费用和最终产品的质量。文章从自我意识、过程规程和开发规程三个层次描述了个体软件工程规程应该包含的基本内容,给出了构建个体软件工程规程的基本步骤,并进一步讨论了个体软件开发过程中的工具支持、个体软件工程规程同软件企业能力成熟度之间的关系等问题。     

面向对象软件的逆向工程

在现代软件工程中，逆向工程是软件维护、软件重工程、软件重用和软件重结构中的起点，它本身是一个设计知识发现、知识抽象的过程，而面向对象软件和传统软件相比有着自己的语言特点和不同的设计知识内容．通过对面向对象程序中知识类别和逆向工程过程的分析，总结出了面向对象软件逆向工程的基本知识内容，并以此为分类线索，综述了目前此领域中具有代表性的技术、工具和研究方向．最后指出了本领域将来发展的方向．     

A System for Generating Reverse Engineering Tools: A Case Study of Software Modularisation

The paper presents a case study in the development of software modularisation tools. The tools are produced by using a system for developing code analysers that uses a database to store both a no-loss fine-grained intermediate representation and the analyses' results. The analysers are automatically generated from a high-level specification of the desired analyses expressed in a domain-oriented language. We use a program intermediate representation, called F(p), as the user-visible data base conceptual model. Analysers are specified in a declarative language, called F(p) – , which allows the specification of an analysis in the form of a traversal of an algebraic expression, with accesses to, and stores of, the database information the algebraic expression indexes. A foreign language interface allows the analysers to be embedded into C programs. This is useful, for example, to implement the user interface of an analyser or to facilitate interoperation of the generated analysers with pre-existing tools.     

用于软件维护阶段的实现方案

用户工作要求的改变，会对所使用的软件提出新需求，因此软件维护不仅仅是纠正原设计中的错误，还要对用户提出的新功能和性能进行修改或再开发，本文提供了几种用于软件维护的实现方案。     

智能软件:由面向对象到面向Agent

文章对照了面向Agent与面向对象的概念、基本思想和运行机制,分析了面向对象的不足和面向Agent在封装、通信、运行等方面的优势,说明了由面向对象到面向Agent将是分布和智能化软件的必然选择。