现代质量管理理论在软件组织的应用

随着信息化技术的发展,软件在世界经济中越发占据重要的位置,成为国际竞争的战略性产业。如何保证软件的质量,提高软件产业的生产能力,发展和壮大软件产业,是我们必须面对和解决的重要问题。文章从现代质量管理理论和发展出发,探讨如何依据ISO9000和CMM这样比较成熟的质量管理标准和模型,进行软件组织的质量管理。     

ISO9000在软件组织的实施模型

在分析国际上影响最为深远的质量管理标准ISO9000的基础上，针对我国软件产业的现状，提出了一个在软件组织贯彻实施ISO9000标准，以达到软件质量和软件过程管理的实施模型。     

基于度量的软件过程改进研究

在软件开发的整个过程中,需要对各个阶段进行评估、分析、改进,它们是一个不断循环的过程.即软件过程改进贯穿于软件开发的始终.如何对软件过程进行度量、度量元是什么,已经成为当前国内外研究的热点.对当前国内许多机构开展的质量管理体系认证模型进行研究,提出了一种基于CMMI的6σ软件度量框架,在此基础上分析了软件过程改进和评估中的关键问题.通过对软件过程的改进,从而提高软件产品质量和提升软件开发效率.     

基于ISO9000的软件质量保证模型

软件危机出现了40多年依然未得到根本的解决,究其原因,业界人士已充分认识到缺乏规范有效的软件质量保障技术和手段是一个主要的原因.随着长期社会化生产的发展,全面质量管理已经形成了一整套理论和体系,并出现了一些国际标准和业界标准.旨在针对我国软件产业的现状,提出一个符合我国国情的软件质量保证模型和实现框架.     

基于CMM的软件开发与测试

软件开发包括需求、设计、编程和测试,而软件测试是软件质量保证的关键步骤,已经得到人们越来越多的重视.目前,CMM(Capability Maturity Model,能力成熟度模型)已经成为国际上最流行、最实用的一种软件生产过程标准,得到了国际软件产业界的认可,成为当今企业从事规模软件生产不可缺少的一项内容.在软件的开发和测试的过程中,针对企业自身的特点,采用CMM软件开发管理流程,能够提高软件开发的质量和效率.     

软件构件管理与重用方法探究

软构件技术是影响整个软件产业的关键技术之一,软件重用在提高软件生产率与质量、减少软件开发时间和成本等方面起到了关键的作用。从软构件的基本属性出发,讨论了软构件的分类原则、描述方法等软构件的管理技术,以及构件重用中的研究热点——构件检索方法,并对软件构件对软件产业造成的影响做了分析。     

论配置管理对软件产业的质量控制

本文论述了配置管理对软件生存周期中各个阶段的质量控制作用，阐明了配置管理是我国迅速发展软件产业、组织大型软件企业的唯一科学管理模式。     

Software quality assurance in Australia: an update

Three recent events are likely to have a significant impact on the future direction of software quality in Australia: the Kean Report, the redevelopment of Australian standard AS3563 and a review of Government purchasing policy as a result of a change of Commonwealth Government. These events, and their subsequent impacts, could have implications and could provide lessons for the software quality assurance industry internationally. These lessons concern: providing adequate education for purchasers, suppliers and auditors on what ISO9000 is all about; implementing appropriate ISO9000-compliant quality management systems, particularly for small and medium sized enterprises; defining an appropriate role for government; and utilizing effective guidance for adopting ISO9001 to software development.     

质量管理在软件开发中的应用

随着软件行业高速的发展,软件开发的超期和超预算都成为软件行业中的重要问题。为了有效地管理软件开发,一些公司增设了质量管理岗位。在软件开发过程中及时地管理和反馈项目信息,把所有重要问题都控制在项目初期,节约大量的人力、物力和财力。     

Open source versus closed source: software quality in monopoly and competitive markets

The open source model of software development has received substantial attention in the industry and popular media; nevertheless, critics frequently contend that open source softwares are inferior in quality compared to closed source software because of lack of incentives and project management, while proponents argue the opposite. This paper examines this quality debate by modeling and analyzing software quality, demand, profitability, and welfare under open and closed source environments in monopoly and competitive markets. The results show no dominant quality advantage of one method over another under all circumstances. Both open source and closed source qualities decrease in a competitive market. Conditions under which each method can generate higher quality software are examined.     

Going soft on quality?:Process management in the Scottish software industry

Despite their proliferation within the industry, quality assurance standards are insufficient to ensure effective software development. Scottish software companies are now highly sensitive to limitations imposed by the standards movement, flagging the need for more explicit attention to work organization and human resource issues. This article examines efforts to broaden the focus of quality management within the software industry, charting the impact of theoretical and practical initiatives and identifying the mediating role of commercial pressures, the consultancy marketplace and, crucially, staff reactions.     

Applying a selection method to choose Quality Attribute Techniques

ContextSoftware products have requirements on software quality attributes such as safety and performance. Development teams use various specific techniques to achieve these quality requirements. We call these “Quality Attribute Techniques” (QATs). QATs are used to identify, analyse and control potential product quality problems. Although QATs are widely used in practice, there is no systematic approach to represent, select, and integrate them in existing approaches to software process modelling and tailoring.ObjectiveThis research aims to provide a systematic approach to better select and integrate QATs into tailored software process models for projects that develop products with specific product quality requirements.MethodA selection method is developed to support the choice of appropriate techniques for any quality attribute, across the lifecycle. The selection method is based on three perspectives: (1) risk management; (2) process integration; and (3) cost/benefit using Analytic Hierarchy Process (AHP). An industry case study is used to validate the feasibility and effectiveness of applying the selection method.ResultsThe case study demonstrates that the selection method provides a more methodological and effective approach to choose QATs for projects that target a specific quality attribute, compared to the ad hoc selection performed by development teams.ConclusionThe proposed selection method can be used to systematically choose QATs for projects to target specific product qualities throughout the software development lifecycle.     

基于RUP开发过程UCM的应用研究

在软件产业中，人们深刻意识到要按时开发出高质量的软件，须在软件开发过程中引人工程化的思想．即全面实现软件工程。Rational的统一开发过程(RUP)生命周期的4个阶段、9个核心过程工作流及其迭代思想，无论是在技术方面，还是在管理方面，给出了完整的开发过程的理论和方法框架；其统一变更管理(UCM)给出全面软件配置管理方案，从而提高软件开发组织团队的软件开发能力。实践表明，应用UCM使配置管理工作变得简单而有效，提高了软件开发的效率，提升了产品的质量。     

Quality,productivity and economic benefits of software reuse: a review of industrial studies

Systematic software reuse is proposed to increase productivity and software quality and lead to economic benefits. Reports of successful software reuse programs in industry have been published. However, there has been little effort to organize the evidence systematically and appraise it. This review aims to assess the effects of software reuse in industrial contexts. Journals and major conferences between 1994 and 2005 were searched to find observational studies and experiments conducted in industry, returning eleven papers of observational type. Systematic software reuse is significantly related to lower problem (defect, fault or error) density in five studies and to decreased effort spent on correcting problems in three studies. The review found evidence for significant gains in apparent productivity in three studies. Other significant benefits of software reuse were reported in single studies or the results were inconsistent. Evidence from industry is sparse and combining results was done by vote-counting. Researchers should pay more attention to using comparable metrics, performing longitudinal studies, and explaining the results and impact on industry. For industry, evaluating reuse of COTS or OSS components, integrating reuse activities in software processes, better data collection and evaluating return on investment are major challenges.

面向地勘行业软件开发过程管理信息系统研究与开发

针对目前地勘行业软件开发过程信息管理缺乏规范化手段和软件运维措施落后等现状,在分析地勘行业软件开发过程管理现状和需求的基础上提出建立面向地勘行业软件开发过程管理信息系统。通过建立管理信息系统,在缩短地勘行业软件开发周期、提升开发过程资料回溯性以及提高行业软件开发过程管理和运维效率等方面取得明显进步,并通过实例验证了系统的实用性和有效性。     

An instrument for the measurement of customer perceptions of quality management in the software industry: An empirical study in India

Most of the available literature on quality management is based on management’s perception; few studies examine critical issues of quality management from the customer’s perspective, especially in the software industry. In order to gain an insight into what customers expect from a product/service, an analysis of quality management from customer’s point of view is essential. Such an understanding would help the managers to adopt strategies that can enhance the satisfaction level of their customers. The present study highlights the critical factors of quality management in the software industry from the customer’s perspective. Six critical factors are identified: and an instrument, comprising these factors, is developed and validated so as to measure the customer’s perception of quality management in the software industry. George Issac is an Assistant Professor in Mar Athanasius College of Engineering, Kothamangalam, India. He holds a B.Sc (Engg.) degree in Mechanical Engineering from Kerala University, and M.Tech and Ph.D degrees in Management from IIT Madras. His research areas are TQM and Organizational Behavior. He has published articles in the area of quality management in journals such as Total Quality Management and Business Excellence, and Quality Management Journal of American Society for Quality. Chandrasekharan Rajendran is a Professor of Operations Management in the Indian Institute of Technology Madras. His research interests are in TQM, Scheduling and Simulation. He has published several articles in international journals. He has publications in the area of TQM in journals such as Total Quality Management, International Journal of Production Research, International Journal of Service Industry Management, International Journal of Bank Marketing, and Journal of Services Marketing. He serves as referee for many journals. He is a recipient of the Alexander von Humboldt Fellowship of Germany. R.N. Anantharaman is a Professor of Management in the Indian Institute of Technology, Madras. His research interests are in TQM, Organizational Behavior and Industrial Psychology. He has published several articles in international journals. He has published research articles in the area of TQM, HRM Practices, Change Management, etc., in Journals such as Total Quality Management, International Journal of Production Research, International Journal of Bank Marketing, International Journal of Service Industry Management, Journal of Services Marketing, International Journal of Human Resource Management, and Journal of Transnational Management Development.     

An approach to the software quality management

This article is devoted to an engineering approach to software quality management. The approach is oriented toward the attainment of the software maturity, which is a key software quality characteristic. A model of quality and a conceptual model for making decisions on software quality management are developed. They are based on methods of specification of quality requirements to the maturity of software components, defect prediction, and systematic quantitative reliability control during software development. A graphical defect prediction model (a Bayesian Belief Network) is presented. __________ Translated from Kibernetika i Sistemnyi Analiz, No. 5, pp. 174–185, September–October 2006.     

Quality management metrics for software development

It can be argued that the quality of software management has an effect on the degree of success or failure of a software development program. We have developed a metric for measuring the quality of software management along four dimensions: requirements management, estimation/planning management, people management, and risk management. The quality management metric (QMM) for a software development program manager is a composite score obtained using a questionnaire administered to both the program manager and a sample of his or her peers. The QMM is intended to both characterize the quality of software management and serve as a template for improving software management performance. We administered the questionnaire to measure the performance of managers responsible for large software development programs within the US Department of Defense (DOD). Informal verification and validation of the metric compared the QMM score to an overall program-success score for the entire program; this resulted in a positive correlation.     

Software quality management: an Australian experience

Since the release ofAustralian Standard 3563 — Software Quality Management System in late 1988 there has been great interest in the application of formal quality management systems to the development of software. Consequently, the standard has been rewritten to conform to the International Standard (ISO) 9001 for the highest level of quality management and to incorporate some lessons learned from the first edition (which was in a slightly different format). This article discusses some experiences of both implementors of the standard and of assessors of the systems. There is also a summary of the clauses of the standard and discussion of some changes made between the two editions of the documents. Published with the 1991 edition is another document that is an implementation guide to help the smaller companies in the industry to implement their quality management systems. Some contents of this guide are also discussed.     

Software challenges: the weakest link in the software engineeringchain

The author compares the performance of software project managers and software technical personnel for five basic activities. Automation does not guarantee success in performing project management functions, but the absence of any automation often correlates with missed or delayed schedules, poor or marginal quality, cost overruns, cancelled projects and the other classical trauma situations of the software industry. The author presents a table of results from a study which gives the percentage of projects applying automation to software management tasks