嵌入式软件开发过程中基于功能点的缺陷度量

运用软件度量的方法改进传统的嵌入式软件开发过程中的缺陷管理过程,论述了在缺陷管理过程中如何度量嵌入式软件的功能点,并且基于功能点来对缺陷数据进行度量,以度量结果作为指示器来分析项目的进展情况和开发人员的工作质量,为项目管理者的决策提供帮助,最终对传统的嵌入式软件缺陷管理模式进行改进。     

软件缺陷度量与软件过程管理方法研究

软件能力成熟度模型第4级中要求在项目中定量管理,建立组织级过程性能,构成完整的量化管理,采用统计或其它定量方法管理软件过程,并通过对过程中出现的方法,技术等问题进行因果分析和寻找解决方案。在仔细研究了现有的缺陷度量分类方法和分析指标后,提出了一个基于缺陷度量与分析的软件过程改进模型。应用该模型可以设计缺陷数据管理系统。     

软件过程度量技术的研究

软件度量是软件项目管理的关键技术。文章在介绍度量基本概念的基础上,重点分析对软件过程的度量,包括分析不同过程成熟度层次对度量的需求。研究系统化的问题驱动的度量过程ISPM（Issue－driven Software Process Measurement）,包括“剪裁”、“应用”、“实现”三个子过程。分析针对软件过程的三大类度量内容和它们子类及子类之间的结构关系,并结合软件过程的层次特性细化度量子类在各个层次的具体表现。最后探讨度量过程随着软件过程成熟度的提高而随之改善的方法。     

数据库应用软件交互复杂性度量研究

依据软件度量的思想和方法,提出数据库应用软件交互复杂性度量的概念。利用4个指标参量表征应用程序与数据库管理系统的交互过程,根据软件测试需要为指标指定权重向量,并通过指标向量与权重向量的乘积将4个指标归一化为一个复杂性度量值。通过实例验证表明,该方法能够客观、准确、灵活地度量数据库应用软件交互过程复杂性。     

软件缺陷度量与分析技术研究

软件能力成熟度模型第4级中要求在项目中定量管理,建立组织级过程,构成完整的量化管理,采用统计或其它定量方法管理软件过程,并通过对过程中出现的方法、技术等问题进行因果分析和寻找解决方案[1]。在仔细研究了现有的缺陷度量分类方法和分析指标后,通过运用缺陷数据分析方法,在开发过程中运用缺陷分析的结果,可以采取合适的对策尽早发现和消除存在的缺陷,以提高软件产品的开发质量和成功率。     

基于软件过程度量的正交缺陷分类技术

软件过程是否有效是评估软件产品质量和提高组织软件能力成熟度的重要依据。给出软件过程有效性量化测量的正交缺陷分类（ODC）技术。介绍ODC的概念、发展过程、总体结构和各种ODC缺陷属性的含义,阐述使用ODC度量开发和识别过程中的问题,对ODC的应用和实施进行分析与总结。     

基于度量的嵌入式软件缺陷风险分析研究

通过对COSMIC-FFP模型的扩展优化提出了嵌入式软件系统度量的方法,从而解决了COSMIC-FFP模型不支持对含有复杂数学算法的嵌入式实时系统度量的问题,基于软件规模度量提出了软件缺陷度量的方法。通过对软件规模的准确度量和对软件缺陷风险的分析,发现软件项目过程风险管理的不足,达到降低软件项目过程风险的目的。     

基于缺陷的软件可靠性度量方法研究

针对软件可靠性度量研究中的一些问题,提出了以缺陷度量为软件可靠性度量的一种方法。首先将缺陷度量方法按照软件度量的一般方法进行研究和探讨;其次,以正交缺陷为基础,提出了定量的缺陷统计方法,这种方法能够更好地描述缺陷的性质,对相关信息可进行分类统计、分析,为过程改进提供依据;最后,提出了一些定性的缺陷分析方法,可充分挖掘缺陷的潜在信息。按照软件度量的步骤,通过定性和定量相结合的方法,可以很好地度量软件可靠性,并实时提高软件可靠性。     

软件测试准则的有效性度量研究

测试准则的有效性是软件质量保障的一个重要问题,但至今仍没有一个有效的度量方法.已有的度量对于全面表示测试效果、提高软件质量的作用非常有限.潜在失效距离(pfd)将测试准则对软件的测试有效性视为以规范、程序、缺陷类型和测试准则为自变量的函数,从软件和测试准则交互的角度来度量测试的有效性.与已有的度量相比较,该度量反映了软件经过满足测试准则的充分测试后获得的可靠性,为比较测试准则的测试效果提供了可行的方法,为设计更易测试的软件提供了指标.     

基于信息模型的企业过程度量研究

探讨了企业过程度量的作用和意义,分析了企业信息模型能够支持企业过程度量的原因和需要进行改进的地方;提出了一个度量信息模型,将企业过程模型中的信息需要映射到企业信息模型,在基本上不改变现有信息模型的情况下,实现对企业过程度量的支持;简单阐述了实现度量信息模型的实现方法;为企业过程模型与信息模型的集成提供一种方法和机制。     

A case study of tracking software development using quality metrics

This paper presents a case history of Mentor Graphics using a set of quality metrics to track development progress for a recent major software release. It provides background on how Mentor Graphics originally began using software metrics to measure product quality, how this became accepted, and how these metrics later fell out of favour. To restore these metrics to effective use, process changes were required for setting quality and metric targets, and for the way the metrics are used for tracking development progress. With these process changes in place, and the addition of a new metric, the case history demonstrates that the metric set could be used effectively to indicate problems in this release and help manage changes to the plan for completion of the release. The lessons learned in this case history are presented, along with subsequent data that further validates these metrics.     

Derivation of local software quality metrics (software quality circles)

Software is a product in serious need of quality control technology. Major effort notwithstanding, software engineering has produced few metrics for aspects of software quality that have the potential of being universally applicable. The present paper suggests that, although universal metrics are elusive, metrics that are applicable and useful in a fully defined setting are readily available. A theory is presented that a well-defined software work group can articulate their operational concept of quality and derive useful metrics for that concept and their environment.     

Applying review and product metrics to the software engineering process: a case study

This paper describes the creation and initial implementation of a measurement programme to Eastman Kodak's Printer Products Division software engineering process. This measurement strategy is being applied to all appropriate programmes within the division. This case study describes one project where a simple set of metrics have improved the quality of our software products and the process used to develop the software. It describes the steps taken to create and implement, and the successes and problems encountered during software development.     

Evaluation of software testing metrics for NASA's Mission Control Center

Software metrics are used to evaluate the software developmentprocess and the quality of the resultingproduct. We used five metrics during the testing phase of the Shuttle Mission Control Center (MCC) Upgrade (MCCU) at the National Aeronautics and Space Administration's (NASA) Johnson Space Center. All but one metric provided useful information. Based on our experience we recommend using metrics during the test phase of software development and propose additional candidate metrics for further study.     

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.     

Controlling and predicting the quality of space shuttle software using metrics

Software quality metrics have potential for helping to assure the quality of software on large projects such as the Space Shuttle flight software. It is feasible to validate metrics for controlling and predicting software quality during design by validating metrics against a quality factor. Quality factors, like reliability, are of more interest to customers than metrics, like complexity. However quality factors cannot be collected until late in a project. Therefore the need arises to validate metrics, which developers can collect early in a project, against a quality factor. We investigate the feasibility of validating metrics for controlling and predicting quality on the Space Shuttle. The key to the approach is the use of validated metrics for early identification and resolution of quality problems.     

COTS软构件测试的信用度量及决策模型

给出了COTS构件可信度度量的概念及构件测试的若干决策模型。该模型可以指导用户在COTS构件交易过程中对构件进行何种程度的测试做出选择并对风险管理和控制提供支持,从而帮助用户在能较好地进行风险管理和控制的前提下尽量减少测试的时间和成本。     

A set of complexity metrics for guiding the software test process

Software verification and validation is a domain which is covered by many dynamic test, static analysis, and formal verification techniques. This presents a problem to practitioners with respect to selecting those suitable techniques which can be used successfully. The basic idea of the methodology presented here is to select test techniques which fit the software under test. A dynamic test technique requires that certain program elements are covered, will be sensitive to errors associated with these elements, because executing an error location is a precondition for revealing the error. Furthermore, it is likely that the probability of errors increases with complexity. Complexity can be characterized in terms of several properties which can be used to suggest various testing strategies. The complexity of the various software properties can be measured using appropriate complexity metrics. Properties with unusual high complexity measures should be tested very throughly. The approach described in this paper permits the selection of test techniques based on the values of the metrics with respect to a particular software product.     

The evaluation of software systems' structure using quantitative software metrics

The design and analysis of the structure of software systems has typically been based on purely qualitative grounds. In this paper we report on our positive experience with a set of quantitative measures of software structure. These metrics, based on the number of possible paths of information flow through a given component, were used to evaluate the design and implementation of a software system (the UNIX operating system kernel) which exhibits the interconnectivity of components typical of large-scale software systems. Several examples are presented which show the power of this technique in locating a variety of both design and implementation defects. Suggested repairs, which agree with the commonly accepted principles of structured design and programming, are presented. The effect of these alterations on the structure of the system and the quantitative measurements of that structure lead to a convincing validation of the utility of information flow metrics.     

On statistics in software engineering measurement

This paper is a brief account of contemporary statistical activity in software engineering measurement, with particular reference to the CEC ESPRIT, programme. The report is intended to be of interest to technical and non-technical managerials staff and assumes little prior knowledge of statistics. It is based on work done for the COSMOS project.

---