软件复用度量综述

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

A Model-Based Approach to Object-Oriented Software Metrics

The need to improve software productivity and software quality has put forward the research on software metrics technology and the development of software metrics tool to support related activities.To support object-oriented software metrics practice efectively,a model-absed approach to object-oriented software metrics is proposed in this paper.This approach guides the metrics users to adopt the quality metrics model to measure the object-oriented software products .The development of the model can be achieved by using a top-down approach.This approach explicitly proposes the conception of absolute normalization computation and relative normalization computation for a metrics model.Moreover,a generic software metrics tool-Jade Bird Object-Oriented Metrics Tool(JBOOMT)is designed to implement this approach.The parser-based approach adopted by the tool makes the information of the source program accurate and complete for measurement.It supports various customizable hierarchical metrics models and provides a flexible user interface for users to manipulate the models.It also supports absolute and relative normalization mechanisms in different situations.     

Automated object-oriented reusable component identification

An automated tool to assist in the understanding of legacy code can be useful both in the areas of software reuse and software maintenance. Most previous work in this area has concentrated on functionally-oriented code. Whereas object-oriented code has been shown to be inherently more reusable than functionally-oriented code, in many cases the eventual reuse of the object-oriented code was not considered during development. This paper describes an approach that makes preparing existing object-oriented code for reuse easier and more quantifiable. This problem includes two primary sub-problems: understanding the function of components, and applying an appropriate set of metrics to the components to quantify reusability.The research described in this paper addresses an approach to the automated understanding of object-oriented code. A knowledge-based system that implements the approach is described. This paper also briefly discusses the formulation of reusability metrics for object-oriented code.     

Supporting search for reusable software objects

Prior research has shown that achieving high levels of software reuse in the presence of repository and object-based computer-aided software engineering (CASE) development methods presents interesting human, managerial and technical challenges. This article presents research that seeks to enhanced software development performance through reuse. We propose automated support for developers who search large repositories for the appropriate reusable software objects. We characterize search for repository objects in terms of a multistage model involving screening, identification, and the subsequent choice between new object construction or reusable object implementation. We propose automated support tools, including ORCA, a software Object Reuse Classification Analyzer, and AMHYRST, an Automated HYpertext-based Reuse Search Tool, that are based on this model. ORCA utilizes a faceted classification approach that can be implemented using hypertext. We also describe an aspect of AMHYRST's architecture which can automatically create hypertext networks that represent and link objects in terms of a number of distinguishing features. We illustrate our approach with an example drawn from a real world object repository     

A framework for developing measurement systems and its industrial evaluation

As in every engineering discipline, metrics play an important role in software development, with the difference that almost all software projects need the customization of metrics used. In other engineering disciplines, the notion of a measurement system (i.e. a tool used to collect, calculate, and report quantitative data) is well known and defined, whereas it is not as widely used in software engineering. In this paper we present a framework for developing custom measurement systems and its industrial evaluation in a software development unit within Ericsson. The results include the framework for designing measurement systems and its evaluation in real life projects at the company. The results show that with the help of ISO/IEC standards, measurement systems can be effectively used in software industry and that the presented framework improves the way of working with metrics. This paper contributes with the presentation of how automation of metrics collection and processing can be successfully introduced into a large organization and shows the benefits of it: increased efficiency of metrics collection, increased adoption of metrics in the organization, independence from individuals and standardized nomenclature for metrics in the organization.     

Reusing software: issues and research directions

Software productivity has been steadily increasing over the past 30 years, but not enough to close the gap between the demands placed on the software industry and what the state of the practice can deliver; nothing short of an order of magnitude increase in productivity will extricate the software industry from its perennial crisis. Several decades of intensive research in software engineering and artificial intelligence left few alternatives but software reuse as the (only) realistic approach to bring about the gains of productivity and quality that the software industry needs. In this paper, we discuss the implications of reuse on the production, with an emphasis on the technical challenges. Software reuse involves building software that is reusable by design and building with reusable software. Software reuse includes reusing both the products of previous software projects and the processes deployed to produce them, leading to a wide spectrum of reuse approaches, from the building blocks (reusing products) approach, on one hand, to the generative or reusable processor (reusing processes), on the other. We discuss the implication of such approaches on the organization, control, and method of software development and discuss proposed models for their economic analysis. Software reuse benefits from methodologies and tools to: (1) build more readily reusable software and (2) locate, evaluate, and tailor reusable software, the last being critical for the building blocks approach. Both sets of issues are discussed in this paper, with a focus on application generators and OO development for the first and a thorough discussion of retrieval techniques for software components, component composition (or bottom-up design), and transformational systems for the second. We conclude by highlighting areas that, in our opinion, are worthy of further investigation     

基于PXI总线的可重塑虚拟仪器测控平台设计与实现

在仪器测控领域,快速搭建自动化检测系统对于工业应用有着重要的意义;文章提出了一种基于PXI总线硬件平台的可重塑虚拟仪器测控系统结构,利用成熟的PXI总线技术,以及分层抽象的软件结构体系;可以最大限度地实现软件、硬件模块的重用,大大缩短开发周期,同时便于产品未来的升级维护;采用该技术,通过搭建数种机载设备自动化测试平台的实验结果表明,对比传统测试手段,能够实现测试时间十倍数量级以上的提高,极大地提高了生产效率。     

青鸟构件库的构件度量

对软件产业发展所需要的软件生产率和软件质量的重视引起了对软件复用技术的研究,同时,有关复用度量的研究和应用也引起了广泛的重视.青鸟构件库系统可以对可复用构件进行描述、管理、存储和检索,用以满足基于“构件-构架”复用的软件开发过程的需要.该文介绍了青鸟构件库中的构件度量模型,并阐述了利用青鸟程序分析系统中的面向对象度量工具和青鸟构件库后期度量系统(包括反馈信息的收集、处理和分析工具)来实现模型的方法.     

A critique of the methods for measuring the impact of CASE software

There is a common belief that CASE software enhances developer productivity and the quality of applications software. However, though the few empirical studies of the impact of CASE have produced inconclusive findings, they do indicate an absence of appreciable productivity gains. There is a need to determine the extent to which CASE products are worth their cost, and this paper focuses on the key methodological issues involved in assessing the cost-effectiveness of CASE products. Existing studies of the impact of CASE software have considered developers' perceptions, but have not considered system users' perceptions nor used software metrics to assess applications software. It is also rare for the characteristics of the development environments and other factors that have an important bearing on the productivity and quality of software to be investigated. In this paper, perceptual and objective measurement, and the different ways of designing the research and of accessing the population of CASE users, are outlined and evaluated. While the aim is to establish the most appropriate research design and measurement approaches for determining the value of CASE tools, the conclusions are also relevant to the assessment of the impact of other new software technologies.     

Measurement modeling technology

Although rigorous measurement has become a necessity in the software industry, many measurement programs fail to deliver real benefit to software managers. The required data is often missing, invalid, or late. But a properly automated measurement system can deliver timely reports that enable proactive management. The measurement modeling technology introduced here supports such automation. It also establishes standard measurements and metrics that organizations can share and combine across projects, departments, and companies.     

An empirical study of software reuse with special attention to Ada

Over the past several decades, numerous software technologies have been developed for overcoming the software crisis. Among these technologies, reuse has been recognized as one of the most important software technologies. Recently, it has gained substantial attention as a possible solution to the software crisis in Ada and other software communities. The purpose of this empirical study is to examine how organizations actually exploit reuse technologies and evaluates how reuse factors affect the rate of reuse in an organization. This study is an attempt to enhance the measurement of the rate of reuse and the effectiveness of reuse by establishing conceptual foundations in the literature for reuse and conducting an empirical investigation of organizations using Ada technology. This study differentiated software reuse into six criteria: domain, human, tool, organization, software metrics, and environment. The results of this study show that the rate of reuse significantly depends upon reuse capability, software development effort, object-oriented design capability, repository development effort, Ada technology capability, and domain capability     

Software reuse: An empirical approach

Software reuse is widely believed to be the most promising technology for significantly improving software quality and productivity. In this paper, we discuss software reuse from an empirical perspective. We examine factors that affect reuse, reuse measurement, and techniques for tailoring a reuse program to a given organization via a failure modes model.     

Complexity assessment: A design and management tool for information system development

Information system complexity is related to many software engineering metrics. Design, construction and maintenance difficulty can be associated with their respective complexity metrics. Complexity measurement algorithms for information system schemas are considered. A set of properties is proposed that serve as a basis for complexity assessment throughout the life cycle. Heretofore, an emphasis in system engineering has been the analysis of software program complexity. Current work, as well as new alternative measures, in software complexity are discussed. Complexity measurement is extended to include other major phases of the system life cycle. Benefits include the evaluation of complexity propagation between system development life cycle phases. Complexity projection provides for improved management of the development process. The implementation of the Dynamic Complexity Monitor (DYCOM) is discussed. DYCOM is comprised of analyzers and models useful in both research and industrial environments. DYCOM supports complexity assessment for requirement definitions, logical and physical design schemata, and implementation and maintenance. The system determines complexity projection functions between life cycle phases. Further, projection functions are automatically updated as the system is used. DYCOM “learns” from system development experience. Also, proposed complexity models can easily be added to DYCOM in order to evaluate their utility. DYCOM serves as a laboratory for examination of alternative complexity metrics.     

An expert system for the selection of software design patterns

Abstract: This paper describes the development of a prototype expert system for the selection of design patterns that are used in object-oriented software. Design patterns provide one method of software reuse, which supports the goal of improved software development productivity. The prototype system represents an initial step towards providing an automated solution regarding the design pattern application problem, i.e. leading a designer to a suitable design pattern which is applicable to the problem at hand. The feasibility of using expert system technology to aid in the selection problem is demonstrated.     

Toward a discipline of software engineering

Despite rapid changes in computing and software development, some fundamental ideas have remained constant. This article describes eight such concepts that together constitute a viable foundation for a software engineering discipline: abstraction, analysis and design methods and notations, user interface prototyping, modularity and architecture, software life cycle and process, reuse, metrics, and automated support     

A metrics suite for object oriented design

Given the central role that software development plays in the delivery and application of information technology, managers are increasingly focusing on process improvement in the software development area. This demand has spurred the provision of a number of new and/or improved approaches to software development, with perhaps the most prominent being object-orientation (OO). In addition, the focus on process improvement has increased the demand for software measures, or metrics with which to manage the process. The need for such metrics is particularly acute when an organization is adopting a new technology for which established practices have yet to be developed. This research addresses these needs through the development and implementation of a new suite of metrics for OO design. Metrics developed in previous research, while contributing to the field's understanding of software development processes, have generally been subject to serious criticisms, including the lack of a theoretical base. Following Wand and Weber (1989), the theoretical base chosen for the metrics was the ontology of Bunge (1977). Six design metrics are developed, and then analytically evaluated against Weyuker's (1988) proposed set of measurement principles. An automated data collection tool was then developed and implemented to collect an empirical sample of these metrics at two field sites in order to demonstrate their feasibility and suggest ways in which managers may use these metrics for process improvement     

项目过程自动化建立方法的研究与实现

现有的软件过程复用方法往往采用形式化的过程模型和过程实例,由于其复杂性而在业界应用较少。提出的项目过程自动化建立的方法是软件过程复用的一种实现方式。该方法对软件过程进行结构化的定义和存储,并通过一组规则将过程描述映射为软件组织所熟悉的项目管理方式——甘特图,以实现项目过程的自动化建立,进而实现软件过程的复用。最后给出了该方法的一个实现．     

Automated measurement of models of requirements

On way to formalize system requirements is to express them using the object-oriented paradigm. In this case, the class model representing the structure of requirements is called a requirements metamodel, and requirements themselves are object-based models of natural language requirements. In this paper, we show that such object-oriented requirements are well suited to support a large class of requirements metrics. We define a requirements metamodel and use an automated measurement approach proposed in our previous work to specify requirements metrics. We show that it is possible to integrate 78 metrics from 11 different papers in the proposed framework. The software that computes the requirements metric values is fully generated from the specification of metrics.     

Managing object oriented framework reuse

Reusing frameworks instead of libraries can cause subtle architectural changes in an application, calling for innovative management solutions. We relate our experience in managing the Knowledge-Based Software Assistant project and offer tips for buying, building and using frameworks. One of the promises of object-oriented software development is that organizations can get a significant return on development investment because the code is easier to reuse. Software project managers are often eager to take the OO plunge for that reason, but are uncertain about the management issues they will face. There is also the problem of choosing the best form of reuse. Library-based reuse, the traditional reuse form, is more popular than framework-based reuse, but we have found that framework-based reuse offers many more benefits with the right management approach. We describe the lessons we learned when building the Knowledge-Based Software Assistant/Advanced Development Model     

基于多层复用的工控软件设计

本文根据领域的不同层次，通过领域分析，提出了基于多层复用的工控软件设计方法。首先,我们研究了工业控制系统的领域特点，从工控软件要解决的功能和算法入手，建立工控软件的标准构件库；再结合特定应用领域。提炼抽象出面向某领域的应用功能构件库；然后在此基础上抽象出某一应用领域的构架库，并以轧钢领域为例作简要说明。最后给出了基于多层复用的工控软件设计过程。