一种优化的面向对象软件复杂性度量方法

首先结合面向对象技术特性,对面向对象软件类级别的CK度量方法和系统级别的MOOD度量方法进行了分析,并就CK度量提出了优化的度量方法OCK。然后结合OCK度量和MOOD度量的优点提出了较优化的面向对象软件复杂性度量方法OSCM。OSCM度量可以有效地弥补CK度量和MOOD度量的不足,优化度量结果。     

面向对象软件度量方法

度量技术是保证软件质量的重要方法。随着面向对象技术的发展，传统的软件度量技术不再适用于面向对象软件。文中分析了软件度量理论，讨论了目前流行的两种面向对象软件度量方法，指出其不足和进一步的工作。     

时态实体依赖关系与度量方法研究

实体间存在各种各样的依赖关系,尤其是在软件开发过程中,软件实体间的依赖关系对软件的变更影响分析以及风险分析等都具有重大影响。依赖图作为最常用的依赖关系表示方法,其节点与边的定义与属性计算不尽相同,且大部分方法中并没有考虑到节点与边的时态属性。针对时态实体依赖图,文中系统地提出了时态实体依赖关系的形式化定义并分析了其特性,然后分析了时态实体依赖图的节点中心性、节点重要性、节点依赖度和边的重要性等4个度量指标,同时,针对MAVEN数据集分析了上述各个指标随时间变化的规律。     

面向对象软件度量的3D可视化方法

软件可视化是指利用印刷、图形、动画以及其它图形或摄影技术提高人们对软件的理解的技术.度量可视化是软件可视化研究的分支之一,它是把度量数据与可视化的图形结合来表示软件的结构.现有的度量可视化方法存在的不足是所能表示的度量指标等属性太少,表示出来的信息不够全面.为了表示更多的属性信息,提出了一种新的面向对象软件度量的3D可视化方法,利用组合图形表示软件实体(如类、方法等),使得所表示的属性数量加倍,从而更有利于对软件的理解和分析.开发出可视化工具M3DTool证明了该方法的有效性.     

一组基于三级度量模型的面向对象度量准则

1 引言软件是信息技术的核心,软件的质量则是人们最关心的因素。软件度量作为刻画、评估和预示软件质量的一个必要和重要的方面,在70年代就开始被研究工作者所关注。从传统的结构化设计到面向对象理论的产生,一方面不断出现新的软件度量指标,如著名的     

面向对象软件度量的研究

软件度量是提高和保证软件质量的关键。在给出的面向对象软件度量的结构模型基础上,讨论了实现该模型要解决的关键问题。通过度量结果的分析和评价,能够有效地对面向对象软件的测试和提高软件质量提供科学的依据。     

面向对象度量综述

软件是信息技术的核心,因而管理人员对软件质量控制越来越重视。这种重视引起了两种效果:(1)要求新的、更好的软件开发方法和技术;(2)在软件开发过程中,进行软件度量。软件度量可以帮助管理人员控制、安排软件开发并利用反馈信息对软件进行改善,从而提高软件质量。软件度量的必要性和重要性已为软件界所认同。作为90年代的领先技术,面向对象的技术已经在软件产业中得到了广泛的运用,面向对象产品也得到了迅猛的发展。面向对象度量是对象技术不可分割的一部分,其在面向对象软件开发中的应用具有以下的功用:     

一种面向对象多态复杂性的度量方法

提出了一种类级多态复杂性和系统级多态复杂性的度量方法。该方法对强制多态、重载多态、类型参数化多态和包含多态这四种类型的多态进行分析,得出反映类的多态复杂性的量度,即强制多态复杂性（CCPP）、重载复杂性（CMC）、参数多态复杂性（CPMP）、包含多态复杂性（CCTP）;然后通过整合得到度量系统级的多态复杂性。实验证明,该方法能够正确有效地度量面向对象软件的多态复杂性。     

面向对象度量—MOOD算法集及其应用分析

面向对象软件的主要特性包括抽象性、封装性、继承性和多态性等。本文在分析这些特性的基础上,介绍了一种能对这些特性进行全面度量的算法集,并对这种算法集在实际应用中可能出现的问题进行了分析,提出了一些新的观点。     

面向对象软件度量技术研究

度量技术是保证软件质量的重要方法。随着面向对象技术的发展,传统的软件度量技术已不再适用于面向对象软件。首先分析了面向对象软件的主要特征,然后讨论了目前流行的两种面向对象软件度量方法,最后指出其不足和进一步的工作。     

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.     

面向对象软件的技术度量

软件度量学是软件工程领域的一个重要研究方向。通过软件度量,可以改进软件的体系结构,采用合适的软件开发过程,从而降低软件开发的成本,提高软件开发的效率,保证软件能满足用户的需求,开发出高质量的软件。分析了面向对象软件度量的特点,阐述了常用的面向对象软件度量方法,并在此基础上提出了以切片为中心的度量方法。     

Measurement and defect modeling for a legacy software system

This paper analyzes the quality of a large-scale legacy software system using selected metrics. Quality measurements include defect information collected during product development and in-field operation. Other software metrics include measurements on various product and process attributes, including design, size, change, and complexity. Preliminary analyses revealed the high degree of skew in our data and a weak correlation between defects and software metrics. Tree-based models were then used to uncover relationships between defects and software metrics, and to identify high-defect modules together with their associated measurement characteristics. As results presented in tree forms are natural to the decision process and are easy to understand, tree-based modeling is shown to be suitable for change solicitation and useful in guiding remedial actions for quality improvement.The following are trademarks or service marks in the United States and/or other countries: IBM is a trademark of International Business Machines Corporation. REFINE and Software Refinery are trademarks of Reasoning Systems Inc. SAS is a trademark of the SAS Institute Inc. S-PLUS is a trademark of the Statistical Sciences, Inc.     

Investigating ARIMA models of software system quality

In this paper, we investigate how to incorporate program complexity measures with a software quality model. We collect software complexity metrics and fault counts from each build during the testing phase of a large commercial software system. Though the data are limited in quantity, we are able to predict the number of faults in the next build. The technique we used is called times series analysis and forecasting. The methodology assumes that future predictions are based on the history of past observations. We will show that the combined complexity quality model is an improvement over the simpler quality only model. Finally, we explore how the testing process used in this development may be improved by using these predictions and suggest areas for future research.     

A new reusability metric for object-oriented software

Software Quality Journal - Software reuse is big business. Managers of software houses know that reuse can bring financial rewards to their company, so long as effective reuse procedures are in...     

面向对象数值软件Trilinos及其线性代数包剖析

分析研究了美国Sandia国家实验室Trilinos项目的设计思想、组织结构,该项目受到ASC计划等的资助.Trilinos框架中定义了一个线性代数对象模型,作为各种软件包的构建基础和沟通载体,此模型当前较成熟的实现为Epetra.详细地阐述了Epetra的组织设计和主要类的层次结构,通过两个数值实验考察该软件当前的性能.可以看到,以Trilinos为代表的众多数值计算项目,为各种数值软件的有效协作、集成和扩展所进行的努力和一些有价值的经验.     

A software complexity model of object-oriented systems

A model for the emerging area of software complexity measurement of OO systems is required for the integration of measures defined by various researchers and to provide a framework for continued investigation. We present a model, based in the literature of OO systems and software complexity for structured systems. The model defines the software complexity of OO systems at the variable, method, object, and system levels. At each level, measures are identified that account for the cohesion and coupling aspects of the system. Users of OO techniques perceptions of complexity provide support for the levels and measures.     

Measuring complexity in C++ application software

This paper concerns the use of design/source-code complexity metrics in analysing C++ software. It describes the use of one suite of object-oriented metrics published by Chidamber and Kemerer¹ to evaluate a commercial C++ application. It provides an interpretation and critique of these metrics, including the use of two traditional metrics (Cyclomatic Complexity² and Software Science³) in association with these object-oriented metrics. The evolution, over a two and a half year period, of one commercial grade C++ application comprising 114 classes with 25,000 lines of code is studied. The efforts consumed in bug fixes and enhancements are correlated with the complexity measures on a per class basis, and results are presented. These results are compared to those from other workers. The paper provides a detailed analysis of the practical strengths and weaknesses of the metrics suite in the light of experiences with its use. © 1998 John Wiley & Sons, Ltd.