软件质量量化指标及实现方法的探讨

在ISO软件质量模型的基础上,建立质量需求评价准则(SQRC)和质量设计评价准则(SQDC)之间的定量关系,将软件质量需求指标转化为软件质量的设计指标,为软件开发人员在设计和编码阶段实施软件质量保证提供指南。它将软件质量保证的任务向设计和编码人员进行分解,有利于软件项目工程化生产过程中的质量管理,从而降低软件生产的风险。     

基于模糊综合评估的嵌入式系统FMECA

为解决广泛应用于安全关键领域的嵌入式系统的可靠性分析问题,该文提出了一种基于模糊综合评估的嵌入式系统FMECA（失效模式、影响及危害性分析）方法。该力法分两步进行：首先根据嵌入式系统软硬件紧密结合的特点,对系统进行硬件FMEA（失效模式与影响分析）,软件详细FMEA以及接口FMEA;然后考虑到评估系统可靠性的失效模式影响因素具有模糊性和不确定性,常规分析方法难于给出有效而准确的评估结果,因此引入模糊综合评估法进行CA（危害性分析）。随后的实验结果证明了这种方法的有效性。     

任务空间概念模型执行机制初探

任务空间概念模型（CMMS）是建立作战模拟系统的根据,概念模型的错误,将直接导致作战模拟系统运行结果不可信.因此,任务空间概念模型的质量非常关键,如何对任务空间概念模型进行校核、验证与确认（VV＆A）是一个非常值得研究的问题.该文在建立任务空间概念模型的形式化描述的基础上,建立了任务空间概念模型的执行机制,并提出了通过概念执行来对模型进行检查的方法.结果表明,通过概念执行,可以挖掘概念模型在结构上和逻辑上的一些错误.     

基于RT-Linux防危保障机制的实验模型

随着嵌入式实时系统在安全关键系统中日益广泛的应用，其软件不但要保证嵌入式实时系统的功能性和时间限制，对其安全性、稳定性和可靠性的要求也大大提高。软件错误的比例大大高于硬件错误，软件错误可能引起硬件误操作，进而直接威胁系统安全。使用防危核可有效防止关键设备误操作。本以RT-Linux实时操作系统为平台，对十字路口交通灯控制建立安全实验模型，研讨防危核实现技术，为防危保障探索新的实现途径。     

软件研制的过程质量管理

软件的质量保证措施主要有2个方面：软件研制过程的质量保证和软件产品的质量评估。本文认为软件研制过程的质量管理是软件质量保证的关键,归纳了现阶段国内软件研制中影响软件质量的主要因素,详细分析了这些因素对于软件质量、软件研制及维护成本的影响,论述了软件研制的过程管理与软件质量的关系,结合长期软件研制工作经验,总结了面向软件质量保证的软件研制过程管理措施的主要内容。     

软件质量保证与软件质量控制

软件质量保证是软件开发流程中的一个重要环节,对软件项目开发中的产品质量控制有重要的作用。但是在项目开发中真正实施这个环节时,会有很多问题有待认识和商讨。本文结合在公司中的实践和体会,阐述关于在实际的软件开发过程中如何将项目的软件质量保证环节做的更好,从而真正提高软件产品的质量。     

软件质量控制的群体协同工作模型

当前软件的开发离不开协同工作。文章通过研究软件开发各个阶段中所存在的各种角色,着重引出了三组角色：质量保证组、开发组和测试组,并在详细分析它们在软件开发过程中的相互作用的基础上,提出了一个软件质量控制的群体协同工作模型。     

一个通用的软件质量评估指标体系

软件已成为人们工作和生活必不可少的助手和伴侣。软件的质量好坏直接影响了人们工作的效率和生活的水平。为确保软件的质量,需要一个系统的软件质量评估指标体系,本文参考了业内软件质量评估指标,并结合多年软件开发和运维经验,设计了一个通用的软件质量评估指标体系,根据此评估体系,我们可以对各种软件的质量进行较系统和全面地评估,从而有助于为软件开发和维护工作提供参照,有助于全面保证和提高软件的质量。     

AADL软件容错系统建模与评估

提出了一种解决软件客错系统的可靠性评估方法,该方法基于AADL,对嵌入式软件系统进行建模,详细分析了软件系统内部各种构件的各种错误状态和其之间的错误传播,构建了AADL软件系统错误模型,并根据基本的转换规则将其转化为广义随机Petri网模型,使用现有工具对其进行了计算,从而实现了软件客错系统的可靠性评估;以航空交通控制(ATC)为应用场景进行实验.根据经验数据适当的假设了部分构件的失效率,收到了较好效果.     

面向AADL模型的存储资源约束可调度性分析

嵌入式实时系统在安全关键领域变得越来越重要,其广泛应用于航空航天.汽车电子等具有严格时间约束的实时系统中.随着嵌入式系统的复杂度越来越高,在系统开发的早期设计阶段就需要对其可调度性进行分析评估.系统中的存储资源会对可调度性产生一定影响,在抢占式实时嵌入式系统引入缓存后,任务的最坏执行时间可能发生变化.因此,分析缓存相关...     

An industrial case study of classifier ensembles for locating software defects

As the application layer in embedded systems dominates over the hardware, ensuring software quality becomes a real challenge. Software testing is the most time-consuming and costly project phase, specifically in the embedded software domain. Misclassifying a safe code as defective increases the cost of projects, and hence leads to low margins. In this research, we present a defect prediction model based on an ensemble of classifiers. We have collaborated with an industrial partner from the embedded systems domain. We use our generic defect prediction models with data coming from embedded projects. The embedded systems domain is similar to mission critical software so that the goal is to catch as many defects as possible. Therefore, the expectation from a predictor is to get very high probability of detection (pd). On the other hand, most embedded systems in practice are commercial products, and companies would like to lower their costs to remain competitive in their market by keeping their false alarm (pf) rates as low as possible and improving their precision rates. In our experiments, we used data collected from our industry partners as well as publicly available data. Our results reveal that ensemble of classifiers significantly decreases pf down to 15% while increasing precision by 43% and hence, keeping balance rates at 74%. The cost-benefit analysis of the proposed model shows that it is enough to inspect 23% of the code on local datasets to detect around 70% of defects.     

Assessing Software Quality Using the Markov Decision Processes

Quality of software is one of the most critical concerns in software system development, and many products fail to meet the quality objectives when constructed initially. Software quality is highly affected by the development process's actual dynamics. This article proposes the use of the Markov decision process (MDP) for the assessment of software quality because MDP is a useful technique to abstract the model of dynamics of the development process and to test its impact on quality. Additionally, the MDP modeling of the dynamics leads to early prediction of the quality, from the design phases all the way through the different stages of development. The proposed approach is based on the stochastic nature of the software development process, including project architecture, construction strategy of Software Quality Assurance system, its qualification actions, and team assignment strategy. It accepts these factors as inputs, generating a relative quality degree as an output. The proposed approach has been demonstrated for the design phase with a case study taken from the literature. The results prove its robustness and capability to identify appropriate policies in terms of quality, cost, and time. © 2011 Wiley Periodicals, Inc.     

PDCA循环在软件质量管理中的应用

为了加强软件产品的质量,提高软件质量管理的水平;在软件质量管理活动中应用PDCA（Plan,Do,Check,Action）循环理论,并建立软件质量管理的PDCA循环模型,在此基础上根据软件产品的特点提出了具体的PDCA循环步骤;实际应用效果表明,软件质量管理的PDCA循环模型不仅可以提升软件产品的质量以及软件企业的质量管理水平,还可以降低软件开发成本、提高软件开发效率。     

基于CMM的软件质量保障平台定义框架

随着计算机软件产业的形成和发展 ,软件质量保证受到越来越多的重视 .于是 ,一种专门针对软件开发组织的软件质量保证模型 CMM逐渐成为研究热点 .本文介绍了 CMM的思想 ,提出了基于 CMM的软件质量保障平台定义框架 ,最后给出了基于定义部分结果构筑的在分布式协同环境下实现的系统结构框图 .     

Information and Quality Assurance: An Unsolved, Perpetual Problem for Past and Future Generations

Quality assurance is well understood in the hardware/manufacturing community but not necessarily within the software community. The meaning of Information assurance depends on who you ask; those in the computer security field interpret information assurance as the need to protect the information, those in quality assurance relate information assurance to the quality of the information. Software assurance ranks even poorer in understanding; although most would agree that it relates to quality, they would be unsure what that means. System assurance is well understood due to its basis on known systems-engineering principles, tending to emphasize the dichotomy of hardware and software concept understanding. In this issue, three articles address parts of the assurance puzzle, which includes: quality assurance, information assurance, software assurance, and system assurance. The combination of these four builds the argument for trust, which is the sole reason for building assurances. To help avoid costly mismatches, consider looking at which part of the assurance puzzle you need solved first before looking at supposed assurance solutions.     

Software Quality Management from a Cross-Cultural Viewpoint

This paper describes our attempts to look at how different cultures influence Software Quality Management (Siakas 1996; Mohamed Walaa-Eldeen and Siakas 1996). Quality of the software product cannot be determined until late in the development cycle. It is widely accepted that reliance has to be placed on process quality as a means of achieving product quality. In recent years software organisations have been making efforts concentrating on improving the process in order to improve software quality. Hofstede (Hofstede 1994) had defined four dimensions of work-related value differences for classifying cultural influences in different countries. These are: power distance, collectivism/individualism, femininity/masculinity and uncertainty avoidance. In this paper software development organisations are being assessed for their awareness and acceptance of Software Quality. These results will be correlated with the work-related values identified by Hofstede. The intention is to identify cultural factors, which may have a bearing on successful adoption and implementation of Software Quality Management. This revised version was published online in August 2006 with corrections to the Cover Date.     

基于面向对象系统的质量度量模型PMMSQ的设计和实现

本文首先从软件质量度量的角度出发,阐述了软件质量度量的理论与方法,介绍了ISO9126模型;针对已有软件质量度量模型中存在的问题,提出了一个适合于软件质量度量实践的实用软件质量度量模型（PMMSQ）,并详细介绍了面向对象系统软件质量度量的步骤;最后,根据PMMSQ模型完成了软件度量活动的核心工作--对象特征集存储库的设
计和实现。     

Architecture for embedded open software ecosystems

Software is prevalent in embedded products and may be critical for the success of the products, but manufacturers may view software as a necessary evil rather than as a key strategic opportunity and business differentiator. One of the reasons for this can be extensive supplier and subcontractor relationships and the cost, effort or unpredictability of the deliverables from the subcontractors are experienced as a major problem.The paper proposes open software ecosystem as an alternative approach to develop software for embedded systems, and elaborates on the necessary quality attributes of an embedded platform underlying such an ecosystem. The paper then defines a reference architecture consisting of 17 key decisions together with four architectural patterns, and provides the rationale why they are essential for an open software ecosystem platform for embedded systems in general and automotive systems in particular.The reference architecture is validated through a prototypical platform implementation in an industrial setting, providing a deeper understanding of how the architecture could be realised in the automotive domain.Four potential existing platforms, all targeted at the embedded domain (Android, OKL4, AUTOSAR and Robocop), are evaluated against the identified quality attributes to see how they could serve as a basis for an open software ecosystem platform with the conclusion that while none of them is a perfect fit they all have fundamental mechanisms necessary for an open software ecosystem approach.