软件复用经济学模型比较分析

说明了软件复用经济学模型的主要目的和任务,对目前国际上提出的12个模型进行了比较分析。将复用经济学模型划分为两类：成本收益模型和投资分析模型,并举例介绍了相关类型的模型。对分析的所有模型列表比较,分析了它们的适用情况和异同点,并对领域存在的问题进行了讨论。     

化学信息学开源软件的集成与复用

软件集成与复用是提高开发效率和质量的重要途径,而开发标准是实现集成与复用的重要因素。通过分析InChI、Jmol和BALL等实例,提出了化学信息学开源软件开发的数据通信标准、界面标准和模块标准问题。在此基础上,以作者进行的分子相似性与差异性研究为例,展示了对开源科学计算软件SciLab的主成分分析(PCA)模块进行改进、集成和复用的情况,说明对开源软件应采取扬弃态度,保障集成、复用的成效。     

The software information base: A server for reuse

We present an experimental software repository system that provides organization, storage, management, and access facilities for reusable software components. The system, intended as part of an applications development environment, supports the representation of information about requirements, designs and implementations of software, and offers facilities for visual presentation of the soft-ware objects. This article details the features and architecture of the repository system, the technical challenges and the choices made for the system development along with a usage scenario that illustrates its functionality. The system has been developed and evaluated within the context of the ITHACA project, a technology integration/software engineering project sponsored by the European Communities through the ESPRIT program, aimed at developing an integrated reuse-centered application development and support environment based on object-oriented techniques.     

基于WebService的软件分布式重用的研究与实现

本文从时间、空间、与应用领域分析了软件重用的特征与重用粒度,针对传统软件不能跨平台、分布式用重等问题,提出了基于WebService的软件分布式重用模式,同时结合实例描述了基于WebService的软件分布式重用的实现;     

A domain-independent software reuse framework based on a hierarchical thesaurus

Software reuse is an effective way to improve software productivity and quality. Software libraries are getting bigger, while most of them, such as those for object-oriented languages, use simple but somewhat ineffective classification methods. These libraries typically provide search aids for novices, but not for experts. They are not flexible enough to adequately serve users with different abilities. In this paper, a Software Reuse Framework (SRF) for overcoming these drawbacks is proposed. Based on a built-in hierarchical thesaurus, the classification process can be made semi-automatic. SRF is a domain-independent framework that can be adapted to various libraries. SRF also provides four search levels to serve users with different skill levels. Two sample SRF systems are implemented, one for Smalltalk-80 and the other for MFC 4.0 (Microsoft® Foundation Class) libraries. © 1998 John Wiley & Sons, Ltd.     

A study of software reuse in NASA legacy systems

Software reuse is regarded as a highly important factor in reducing development overheads for new software projects; however, much of the literature is concerned with cost and labor savings that reuse brings to industrial software development and little is known about the inherent risks associated with reuse, particularly in the case of mission and safety-critical software systems. We present the preliminary findings of a research project geared toward assessing the impact of risk in National Aeronautics and Space Administration (NASA) legacy software in flight control systems. We introduce the concept of context variables and the impact they have on reuse within these legacy systems as well as the genealogy classification models, which provide a simple, concise method of mapping reuse between families of software projects. This research was conducted at Global Science and Technology, Inc. under NASA grant number NCC0NNG06GI57G.     

A case-based approach to software reuse

This software reuse system helps a user build programs by reusing modules stored in an existing library. The system, dubbed caesar (Case-basEd SoftwAre Reuse), is conceived in the case-based reasoning framework, where cases consist of program specifications and the corresponding C language code. The case base is initially seeded by decomposing relevant programs into functional slices using algorithms from dataflow analysis. caesar retrieves stored specifications from this base and specializes and/or generalizes them to match the user specification. Testing techniques are applied to the construct assembled by caesar through sequential composition to generate test data which exhibits the behavior of the code. For efficiency, inductive logic programming techniques are used to capture combinations of functions that frequently occur together in specifications. Such combinations may be stored as new functional slices.     

The impact of software evolution and reuse on software quality

This paper presents a case study of a software project in the maintenance phase. The case study was based on a sample of modules, representing about 1.3 million lines of code, from a very large telecommunications system. Software quality models were developed to predict the number of faults expected from the coding through operations phases. Since modules from the prior release were often reused to develop a new release, one model incorporated reuse data as additional independent variables. We compare this model's performance to a similar model without reuse data.Software quality models often have product metrics as the only input data for predicting quality. There is an implicit assumption that all the modules have had a similar development history, so that product attributes are the primary drivers of different quality levels. Reuse of software as components and software evolution do not fit this assumption very well, and consequently, traditional models for such environments may not have adequate accuracy. Focusing on the software maintenance phase, this study demonstrated that reuse data can significantly improve the predictive accuracy of software quality models.     

A Knowledge-Based Software Engineering Environment for reusable software requirements and architectures

This paper describes a prototype Knowledge-Based Software Engineering Environment used to demonstrate the concepts of reuse of software requirements and software architectures. The prototype environment, which is application-domain independent, is used to support the development of domain models and to generate target system specifications from them. The prototype environment consists of an integrated set of commercial-off-the-shelf software tools and custom developed software tools.The concept of reuse is prevalent at several levels of the domain modeling method and prototype environment. The environment itself is domain-independent thereby supporting the specification of diverse application domain models. The domain modeling method specifies a family of systems rather than a single system; features characterize the variations in functional requirements supported by the family and individual family members are specified by the features they are to support. The knowledge-based approach to target system generation provides the rules for generating target system specifications from the domain model; target system specifications, themselves, may be stored in an object repository for subsequent retrieval and reuse.     

基于XML的软件总线设计的研究与实现

随着软件工程的不断发展,以及面向对象技术、软件组件技术和软件复用技术的开发与利用,软件总线的研究与开发已逐步成为关注的重点。软件总线也像计算机硬件总线一样,只要符合总线标准的软件组件均可以插接到软件总线上去,以实现组件的即插即用(plug-and-play)。在此,基于对软件总线技术的研究,介绍了一种基于XML的软件总线设计方案,通过使用软件总线技术开发和集成软件,不但可以大大地缩短开发周期,还可以进一步提高软件的开发效率和质量。     

Analogy-based domain analysis approach to software reuse

Domain analysis is an expansion of conventional requirements analysis. Domain analysis can support effective software reuse. However, domain analysis is time consuming and is limited to a particular application area. Analogical approaches to software reuse, on the other hand, often occur across domains. Analogical problem solving is a process of transferring knowledge from a well-understood base domain to a new target problem area. Analogy can facilitate software reuse for poorly understood problems or new application areas. Analogy shares similar concepts with reuse and some analogy theories have been applied to software reuse. However, current research on software analogy often overlooks the importance of analysis for the base domain and does not consider some critical aspects of analogy concepts. Reuse must be based on high quality artifacts, especially reuse across domains. This paper presents an approach to integrate domain analysis and analogy methods. In our view, domain analysis and software analogy have complementary roles. Domain analysis is regarded as a process to identify and supply necessary information for analogical transfer. Software analogy can provide the analyst with similar problems and solutions to reuse previous domain analysis knowledge or artifacts for a new domain. This paper presents case studies to demonstrate the increase of efficiency in applying the approach. Evaluation of the approach from various perspectives is also reported.     

航天型号软件生存周期模型选择指南

文中首先阐述了有关生存周期模型的基本概念,简要介绍4个已在国内外航天界得到成功应用的典型生存周期模型：瀑布模型、增量模型、进化模型和基于软件包的生存周期模型,分别给出了这4个生存周期模型的优点、缺点、适用情况以及各生存周期阶段的主要产品和里程碑评审,最后给出选择航天型号软件生存周期模型的基本原则。     

Building enterprise reuse program

Reuse is viewed as a realistically effective approach to solving software crisis. For an organization that wants to build a reuse program, technical and non-technical issues must be considered in parallel. In this paper, a model-based approach to building systematic reuse program is presented. Component-based reuse is currently a dominant approach to software reuse. In this approach, building the right reusable component model is the first important step. In order to achieve systematic reuse, a set of component models should be built from different perspectives. Each of these models will give a specific view of the components so as to satisfy different needs of different persons involved in the enterprise reuse program. There already exist some component models for reuse from technical perspectives. But less attention is paid to the reusable components from a non-technical view, especially from the view of process and management. In our approach, a reusable component model—FLP model for reusable component—is introduced. This model describes components from three dimensions (Form, Level, and Presentation) and views components and their relationships from the perspective of process and management. It determines the sphere of reusable components, the time points of reusing components in the development process, and the needed means to present components in terms of the abstraction level, logic granularity and presentation media. Being the basis on which the management and technical decisions are made, our model will be used as the kernel model to initialize and normalize a systematic enterprise reuse program.     

基于构件的软件复用技术研究及在MIS中的应用

阐述了基于构件的软件复用技术,并就基于构件软件开发技术在管理信息系统（MIS）中的应用作了探讨,对提高软件开发效率有着重要意义。     

A dynamic software release model

The determination of optimal software release times constitutes an interesting decision making problem which involves the stochastic structure of the underlying software reliability model, as well as various cost parameters. There is an apparent tradeoff between testing the software further to improve its reliability, and releasing it for operational use to decrease the costs. We propose and analyze in depth a new dynamic model with sufficient generality. After each failure, a debugging activity, possibly imperfect, is undertaken and a decision is made regarding the duration of additional testing. If no failure is observed during this time, then the software is released. Otherwise, the failure is debugged and the decision process is repeated in a dynamic fashion. The problem is formulated using dynamic programming and interesting characterizations of the optimal release policy are presented. The dynamic solution procedure is demonstrated by some numerical illustrations.     

基于复用的构件开发模型的研究与应用

提出了一种基于复用的构件开发模型,该模型解决了构件内部结构和组织问题,保证良好的功能职责划分和关注点分离;保证构件以规范化的方式提供对外服务接口和扩展接口;保证构件具有良好的扩展性以及随需应变的能力.通过应用该模型开发了面向金融领域的客户管理构件,并将该构件复用于具体的金融项目.实践表明,该模型能提高软件复用率,降低开发难度,加快开发速度.     

非成熟领域软件复用过程模型

将一个软件企业或开发团队实现有组织的软件复用分为4个阶段,针对可复用资源积累阶段的特点,提出了非成熟领域软件复用过程模型,应用系统分析设计与领域分析适当结合,经数次迭代,逐步积累领域知识,使面向提交的应用系统开发平滑过渡到基于复用地开发,使该领域尽快成熟.该过程模型还考虑了应用系统开发时效和软件开发团队运营成本问题,此阶段软件复用不强调领域工程,应用系统开发是面向提交的,但需要使用基于构件的软件开发.     

Building enterprise reuse program——A model-based approach

Reuse is viewed as a realistically effective approach to solving software crisis. For an organization that wants to build a reuse program, technical and non-technical issues must be considered in parallel. In this paper, a model-based approach to building systematic reuse program is presented. Component-based reuse is currently a dominant approach to software reuse. In this approach, building the right reusable component model is the first important step. In order to achieve systematic reuse, a set of component models should be built from different perspectives. Each of these models will give a specific view of the components so as to satisfy different needs of different persons involved in the enterprise reuse program. There already exist some component models for reuse from technical perspectives. But less attention is paid to the reusable components from a non-technical view, especially fromthe view of process and management. In our approach, a reusable component model--FLP modelfor reusable component     

Reuse-based software production technology

Software reuse is viewed as a key technology to improve software product quality and productivity. This paper discusses a series of technologies related with software reuse and software component technology: component model, which describes component's essential characteristics; component acquisition technology, of which domain engineering is the main approach; component management technology, of which component library is the kernel; application integration and composition technology, of which application engineering is the main approach; software evolution technology, of which software reengineering is the main approach, etc. This paper introduces the software development environment: JadeBird Software Production Line System, which effectively integrates the above-mentioned technologies.     

Selection of third party software in Off-The-Shelf-based software development—An interview study with industrial practitioners

The success of software development using third party components highly depends on the ability to select a suitable component for the intended application. The evidence shows that there is limited knowledge about current industrial OTS selection practices. As a result, there is often a gap between theory and practice, and the proposed methods for supporting selection are rarely adopted in the industrial practice. This paper's goal is to investigate the actual industrial practice of component selection in order to provide an initial empirical basis that allows the reconciliation of research and industrial endeavors. The study consisted of semi-structured interviews with 23 employees from 20 different software-intensive companies that mostly develop web information system applications. It provides qualitative information that help to further understand these practices, and emphasize some aspects that have been overlooked by researchers. For instance, although the literature claims that component repositories are important for locating reusable components; these are hardly used in industrial practice. Instead, other resources that have not received considerable attention are used with this aim. Practices and potential market niches for software-intensive companies have been also identified. The results are valuable from both the research and the industrial perspectives as they provide a basis for formulating well-substantiated hypotheses and more effective improvement strategies.