共查询到20条相似文献,搜索用时 171 毫秒
1.
面向对象软件度量学的研究 总被引:1,自引:0,他引:1
软件度量学是软件工程领域的一个重要研究方向。通过软件度量,可以降低软件开发的成本,提高软件开发的效率,保证软件能满足用户的需求,开发出高质量的软件。本文分析了面向对象软件度量的特点,在著名的C&K度量方法及其它度量方法的基础上,着重阐述了针对各种不同层次的面向对象的软件度量,包括面向OO项目的度量、面向OO系统的度量、面向类继承树的度量、面向类层的度量、面向方法(操作)的度量。 相似文献
2.
3.
软件体系结构度量工具的研究与实现* 总被引:1,自引:1,他引:0
在软件体系结构层次应用度量技术对于保证最终产品的质量有重要意义。但体系结构度量领域普遍存在对于度量扩展支持不足的问题。针对该问题,采用新的思路实现了一个可支持度量扩展的软件体系结构度量工具。该工具支持一组基本度量,并支持较为丰富的组合运算,使用户可定制度量,从而在一定程度内解决了体系结构度量领域存在的问题。 相似文献
4.
5.
6.
为了提高集成软件开发质量度量方法的度量效果,提出基于指标融合的集成软件开发质量度量方法。建立软件质量度量指标,采用指标融合的方法对指标进行处理,利用中介加权法确定真区域和假区域,求出评价矩阵的可靠度评价参数集,获取软件开发质量度量的综合评分集,并按照得分大小排序,得到可靠性的量化评分结果,以此完成集成软件开发质量度量。实验结果表明,所提方法的度量准确度较高,并在5 min之内就能够完成软件开发质量度量,并且减少了软件开发指标度量后软件发生故障的次数,从而提高了集成软件开发质量方法的度量效果。 相似文献
7.
张横云 《数字社区&智能家居》2008,(1):298-300
随着计算机技术的飞速发展,对软件质量的要求也更高了,软件质量度量就是衡量软件品质的一种手段。本文分析了软件质量度量模型,建立了软件质量度量框架,并给出了常用度量方法。 相似文献
8.
9.
文中根据GSQM软件度量思想和相关软件度量理论结合软件测试过程的特殊性要求,提出基于目标驱动的软件测试度量方法(GSTM)。在度量信息需求的基础上主要研究了适合于软件测试度量的基本度量方法、派生度量方法和设计指示器的方法。文中是专门针对软件测试度量进行的研究,与传统的软件度量理论相比较,具有很强的针对性、实用性和可操作性。 相似文献
10.
软件缺陷预测可帮助开发人员提前预测缺陷程序,合理分配有限的测试资源。软件缺陷预测的准确度不仅依赖于预测方法的选择,更依赖于软件的度量指标。因此,结合多元度量指标进行软件缺陷预测已成为当前的研究热点。从度量指标出发,对传统度量指标、多元度量指标以及结合多元度量指标的缺陷预测的研究进展进行了系统介绍。主要工作包含:介绍了传统的代码和过程度量指标、基于传统度量指标的软件缺陷预测模型以及影响数据质量的因素;阐述了语义结构度量指标;分析列举了当前用于软件缺陷预测的评价指标;结合预测粒度、传统度量指标、语义结构度量指标、跨项目软件缺陷预测对多元度量指标软件缺陷预测未来的研究趋势进行了展望。 相似文献
11.
12.
13.
利用软件度量工具对软件的各类质量属性度量,对于提高程序的质量有重要意义.在分析面向移动Agent的度量指标的基础上,设计并实现一种基于移动Agent的软件度量工具,该工具通过度量Agent与系统中其它Agent进行交互来获取度量所需信息并对其进行加工处理,用户可以通过度量Agent提供的接口查询度量的结果.最后给出度量指标与度量特征之间关系的实验结果. 相似文献
14.
面向对象软件度量是理解和保证面向对象软件质量的重要手段之一.通过将面向对象软件的度量值与其阈值比较,可简单直观评价其是否有可能包含缺陷.确定度量阈值方法主要有基于数据分布特征的无监督学习方法和基于缺陷相关性的有监督学习方法.两类方法各有利弊:无监督学习方法无需标签信息而易于实现,但所得阈值的缺陷预测性能通常较差;有监督学习方法通过机器学习算法提升所得阈值的缺陷预测性能,但标签信息在实际过程中不易获得且度量与缺陷链接技术复杂.近年来,两类方法的研究者不断探索并取得较大进展.同时,面向对象软件度量阈值确定方法研究仍存在一些亟待解决的挑战.对近年来国内外学者在该领域的研究成果进行系统性的总结.首先,阐述面向对象软件度量阈值确定方法的研究问题.其次,分别从无监督学习方法和有监督学习方法总结相关研究进展,并梳理具体的理论和实现的技术路径.然后,简要介绍面向对象软件度量阈值的其他相关技术.最后,总结当前该领域研究过程面临的挑战并给出建议的研究方向. 相似文献
15.
Acknowledging the intense requirement for low power operation in most portable computing systems, this paper introduces the notion of energy efficient software design and proposes metrics, for evaluating software systems in terms of their energy consumption. Considering the sources of power consumption in every digital circuit, and the fact that power is primarily dependent on the executing software, appropriate energy measures are derived, which can be extracted from the flowgraph of a program. The proposed measures are computed by applying rules common to the existing hierarchical measures of other internal software attributes, and form the basis for the definition of a software energy metric. This metric can be used in order to determine the level of energy consumption of any software system more efficiently than existing assembly-parsing techniques, with only a limited penalty in accuracy. Application to different implementations of algorithms, drawn from matrix algebra and multimedia, demonstrates the efficiency of the proposed energy metric for comparison purposes, and as an indicator for quality improvement. 相似文献
16.
James Kenneth Blundell Mary Lou Hines Jerrold Stach 《Annals of Software Engineering》1997,4(1):235-255
Software quality involves the conformance of a software product to some predefined set of functional requirements at a specified level of quality. The software is considered valid when it conforms to these “quality factors” at some acceptable level. There are a large number of quality factors against which software may be validated. This paper discusses the development of traditional software metrics in relation to the anticipated structure of a software system. The taxonomy of a software system primarily relies upon the dissection of the software system into modules. Modular design is the cornerstone of quality software, and metrics that can predict an optimum modular structure are critical. By examining the theoretical bases on quality metrics, a base set of common quantitative metrics can be devised and mapped to quality metrics in which they reside. This paper surveys existing metrics and suggests the derivation of software design metrics from software quality factors. Measurable software attributes are identified and suggested as potential design metrics. 相似文献
17.
This paper presents an empirical case study that predicted faults in modules based on the total information content of the operators. This metric is closely related to Harrison's average information content classification (AICC), which is the entropy of the operators. Most information theory-based metrics proposed in the literature have not been subjected to empirical predictive studies of real-world software systems. In contrast, this study shows that a simple information theory-based metric can be more useful for prediction of software quality than comparable metrics based on counts in the context of a commercial software development organization.Three models were considered, all based on operators as an abstraction of software. The model based on information content of the operators made more accurate predictions than two similar models based on the number of operators and the number of unique operators. The purpose of this paper is a fair comparison of the three metrics, rather than developing an optimal model. We have long advocated multivariate models for industrial use. The case study considered three large commercial systems, written in assembly language, and developed consecutively by professional programmers. The first system was used to estimate parameters of the models. The subsequent two were used to evaluate the accuracy of model predictions. 相似文献
18.
《IEEE transactions on pattern analysis and machine intelligence》1983,(6):652-663
The desire to predict the effort in developing or explain the quality of software has led to the proposal of several metrics in the literature. As a step toward validating these metrics, the Software Engineering Laboratory has analyzed the Software Science metrics, cyclomatic complexity, and various standard program measures for their relation to 1) effort (including design through acceptance testing), 2) development errors (both discrete and weighted according to the amount of time to locate and frix), and 3) one another. The data investigated are collected from a production Fortran environment and examined across several projects at once, within individual projects and by individual programmers across projects, with three effort reporting accuracy checks demonstrating the need to validate a database. When the data come from individual programmers or certain validated projects, the metrics' correlations with actual effort seem to be strongest. For modules developed entirely by individual programmers, the validity ratios induce a statistically significant ordering of several of the metrics' correlations. When comparing the strongest correlations, neither Software Science's E metric, cyclomatic complexity nor source lines of code appears to relate convincingly better with effort than the others 相似文献
19.
20.
软件度量研究方兴未艾,构建软件度量模型是其中一个重要的研究方向。度量模型从本质上说,是一组对软件进行评价的标准。这个标准并不是仅仅为了用来证明软件的好坏优劣,也用来反映不同软件系统或者软件模块的特点,从而为不同的需求服务。计算机科学中没有绝对的概念,它从诞生起就是紧密围绕应用服务的,计算机科学的研究一定要和现实需求相关联,因此作为一种评价标准,度量模型同样是从不同方面来综合评测软件的属性,从而在不同需求面前提供可参考的选择。 相似文献