非基于软件复用的成本估算模型的复用改造模型及模型系数修正策略

作为软件成本控制管理的重要措施,软件开发成本的估算技术已经成为软件工程领域的一个重要课题。当前基于复用的软件开发正在成为软件工程的主流,但将软件复用考虑进成本估算的模型较少。提出一个基于软件复用的成本估算模型,并应用该模型对COCOMO模型进行复用改造,之后通过实例进行验证。给出了使用存储过程技术对模型参数进行修正的策略,以为各类基于复用的软件开发成本估算提供依据。     

基于软件复用的信息系统开发模型

在简要地介绍软件复用的概念和关键技术的基础上,结合领域工程、应用工程、组件化开发、原型开发方法以及面向对象开发方法等技术的优势,提出了一种基于软件复用的信息系统开发模型。     

软件复用

本总结了软件复用技术的基本概念,介绍了有关软件复用的理论研究和实践活动,指出研究软件复用技术存在的关键问题,并给出了可选解决方案,最后,说明了软件复用与ＣＡＳＥ环境的关系。     

基于软件复用的开发模型的研究

介绍了软件复用技术的基本概念,分析了软件复用的过程;以江苏校园招聘网为例对软件复用技术的开发模型进行了详细的研究．     

基于构件的软件复用在软件企业中的实现模型

阐述了基于构件的软件复用技术，利用其成熟的构件设计标准提出了一种比较实用的实现模型，并尝试此技术在公务网项目中的实践应用，极大地方便了软件复用，对提高软件开放效率有着重要意义。     

软件复用度量综述

软件复用度量是软件复用技术中不可分割的一部分,在软件复用开发中占据重要地位。软件复用开发与传统的软件开发方式不同,从而影响到软件度量,因此需要新的软件复用度量方法,软件复用度量的研究已经引起学术界的广泛重视。本文是一篇软件复用度量综述,阐述了软件复用对度量的影响以及有关软件复用的度量。     

基于软件复用的开发模型的研究

介绍了软件复用技术的基本概念,分析了软件复用的过程;以江苏校园招聘网为例对软件复用技术的开发模型进行了详细的研究。     

基于软件复用模型的稳定分析模式的研究

对于构造高效可复用的通用软件组件的研究已成为软件工程领域非常有研究价值的工作.软件的分析模式是可复用的组件模型,然而一般的分析模式中都存在一些不足,这些不足使得分析模式很难成为高效可复用的组件模型.本文将提出八个重要分析模式属性来评价模式的可复用性,另外提出一种稳定的分析模式的概念,最后将稳定的分析模式与其他模式进行比较.     

软件复用机会的识别

软件危机的出现制约了软件规模的进一步发展.软件复用技术成为解决软件危机的一个途径,构件复用是软件复用的一个重要的组成部分.对软件开发者来说,如何着手进行复用,是一个急需解决的问题.文中通过对可复用构件理论的研究,结合在软件开发中的实践经验,总结了识别软件可复用机会的方法和策略,提出了多领域再分析法.给出了该方法的实施步骤、相应技术及策略,建立了相应模型.     

软件复用及相关技术

一、关于软件复用通常情况下,应用软件系统的开发过程包含以下几个阶段:需求分析、设计、编码、测试、维护等。当每个应用系统的开发都从头开始时,其中必然存在大量的重复劳动,如:用户需求获取、需求分析和设计、编码、测试和文档工作等方面都会有重复。应用系统的本质通常包含三类成分:①通用基本构件:是特定于计算机系统的构成成分,如基本的数据结构、用户界面元素等,可以存在于各种应用系统中;②领域共性构件:是应用系统所属领域的共性构成成分,存在于该领域的各个应用系统中;③应用专用构件:是每个应用系统的特有构成成分。其中的重复劳动主要存在于前两类构成成分的重复开发。     

A model for software reuse

Software reusability is widely believed to be a key to help overcome the ongoing software crisis by improving software productivity and quality. New computer technology and the demands of an advancing society require new and more complicated software. It is unrealistic to expect that every software system can be developed solely reusing existing software; however, software reusability has proven to be a way of enhancing software productivity and quality in different organizations. It is also believed that reuse of code segments alone does not significantly reduce software development effort.By creating reuse support information while software is being developed (when the software is best known to software developers), the reuse effort for both software development and maintenance can be potentially reduced.In this paper, five types of RSI are presented: Semantic Web, Horizontal Web, Vertical Web, Syntactic Web, and Alternative Web. We collectively call these five webs a Quintet Web. The Semantic Web enables software developers to locate a software segment. The Horizontal Web provides a means to reuse a block of soflware along with other types of software from other phases of a development process. The inter-phase integration of software can be performed through this Web. The Vertical Web identifies the vertical relationship of a software block to its operational environment. The Syntactic Web locates all statements in which a variable is used. The Alternative Web provides alternative software blocks that perform an identical operation.A prototype of the Quintet Web is presented.     

产品线成本模型的比较与分析

为给软件产品线决策者应用软件产品线模型提供理论上的参考,综合分析比较了近年来的20种软件产品线模型,在对软件产品线模型的投资循环、重用方式、货币时间价值、经济函数、成本因子和重用成本等方面因素进行细致分析的基础上提出了软件产品线模型的比较框架,在该框架内着重分析了其中5种典型的软件产品线模型,对应用软件产品线开发方式的成本估算和投资分析做了细致分析,并对当前软件产品线模型时存在的问题和发展方向进行了探讨.     

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.     

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

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

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.     

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

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

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.     

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

将一个软件企业或开发团队实现有组织的软件复用分为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     

Aligning the economic modeling of software reuse with reuse practices

In contrast to current practices where software reuse is applied recursively and reusable assets are tailored trough parameterization or specialization, existing reuse economic models assume that (i) the cost of reusing a software asset depends on its size and (ii) reusable assets are developed from scratch. The contribution of this paper is that it provides modeling elements and an economic model that is better aligned with current practices. The functioning of the model is illustrated in an example. The example also shows how the model can support practitioners in deciding whether it is economically feasible to apply software reuse recursively.