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

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

Body of knowledge for software quality measurement

Measuring quality is the key to developing high-quality software. The author describes two approaches that help to identify the body of knowledge software engineers need to achieve this goal. The first approach derives knowledge requirements from a set of issues identified during two standards efforts: the IEEE Std. 1061-1998 for a Software Quality Metrics Methodology and the American National Standard Recommended Practice for Software Reliability (ANSI/AIAA R-013-1992). The second approach ties these knowledge requirements to phases in the software development life cycle. Together, these approaches define a body of knowledge that shows software engineers why and when to measure quality. Focusing on the entire software development life cycle, rather than just the coding phase, gives software engineers the comprehensive knowledge they need to enhance software quality and supports early detection and resolution of quality problems. The integration of product and process measurements lets engineers assess the interactions between them throughout the life cycle. Software engineers can apply this body of knowledge as a guideline for incorporating quality measurement in their projects. Professional licensing and training programs will also find it useful     

Victor R. Basili's contributions to software quality

This article deals with Victor R. Basili's contributions to software quality. Basili's contributions cover three broad areas: research in the 1970s and early 1980s on software measurement and the Goal Question Metric (GQM) model, research in the 1980s and 1990s on these measurement ideas' maturation into a software engineering model of empirical studies, including the development of the Quality Improvement Paradigm (QIP) and the influence of the NASA Goddard Space Flight Center Software Engineering Laboratory, and research since 1990 in the Experience Factory as a model for creating learning organizations for continuous software process improvement. Some of Basili's most important contributions are in measuring software development processes and products and gifted the community with an invaluable tool: the GQM approach. The GQM approach is based on the assumption that for an organization to measure its products and processes usefully, it must first specify goals for itself and its projects.     

如何更好地保证软件项目的质量

软件企业更多的时候是在为客户提供服务而不是像买卖一件商品那么简单,改善客户满意度应该是一个着眼于未来的软件企业不断追求的目标。那么软件企业如何才能为用户提供高质量的产品呢?本文将从质量策略、质量管理过程、质量管理常用技术和工具、QA的工作等几个方面探讨如何更好地保证软件的质量。     

Computational intelligence and visual computing: an emerging technology for software engineering

 The discipline of Software Engineering is abstract and complex with all its endeavors being cast in a knowledge-intensive environment. It is not surprising that there have been a number of important initiatives that have attempted to address a burning need for solid development tools and comprehensive environments supporting an in-depth analysis. The objective of this study is to discuss a role of Computational Intelligence (CI) and visual computing being viewed as a sound methodological and algorithmic environment for knowledge-oriented Software Engineering. The CI itself is regarded as a synergistic consortium of granular computing (including fuzzy sets) promoting abstraction, neurocomputing supporting various learning schemes and evolutionary computing providing important faculties of global optimization. By its very nature, CI embraces a diversity of design paradigms; in particular it promotes a top-down approach (when exploiting fuzzy sets first and afterwards working in the neural network environment) or bottom-up style (where these two technologies are used in a reverse order). Visual computing is inherently associated with CI: it is human-centric where fuzzy sets make visualization activities feasible. Fuzzy sets are treated as a graphic means of accepting information from users. They are regarded as a vehicle used to visualize results in a linguistic manner. Software Engineering and CI are highly compatible: they are knowledge-intensive, human-oriented, and have to deal with various manifestations of the abstract world of software constructs and thought processes. This multifaceted conceptual compatibility is a prerequisite for the development of vital synergistic links that bring the technology of CI into Software Engineering. The symbiosis accrues considerable benefits for both technologies by posing new categories of challenging and highly stimulating problems. The facet of visual computing is essential in handling of software processes and software products. The intent of this study is to provide a general overview of this new development in Software Engineering. In particular, we highlight a number of selected and most visible trends occurring at the junction of CI and Software Engineering. Furthermore we discuss several specific applications of the technology of CI to software cost estimation, analysis of software measures and neural models of software quality. Support from the Natural Sciences and Engineering Research Council of Canada (NSERC) and the Alberta Software Engineering Research Consortium (ASERC) is gratefully acknowledged.     

An empirical study of predicting software faults with case-based reasoning

The resources allocated for software quality assurance and improvement have not increased with the ever-increasing need for better software quality. A targeted software quality inspection can detect faulty modules and reduce the number of faults occurring during operations. We present a software fault prediction modeling approach with case-based reasoning (CBR), a part of the computational intelligence field focusing on automated reasoning processes. A CBR system functions as a software fault prediction model by quantifying, for a module under development, the expected number of faults based on similar modules that were previously developed. Such a system is composed of a similarity function, the number of nearest neighbor cases used for fault prediction, and a solution algorithm. The selection of a particular similarity function and solution algorithm may affect the performance accuracy of a CBR-based software fault prediction system. This paper presents an empirical study investigating the effects of using three different similarity functions and two different solution algorithms on the prediction accuracy of our CBR system. The influence of varying the number of nearest neighbor cases on the performance accuracy is also explored. Moreover, the benefits of using metric-selection procedures for our CBR system is also evaluated. Case studies of a large legacy telecommunications system are used for our analysis. It is observed that the CBR system using the Mahalanobis distance similarity function and the inverse distance weighted solution algorithm yielded the best fault prediction. In addition, the CBR models have better performance than models based on multiple linear regression. Taghi M. Khoshgoftaar is a professor of the Department of Computer Science and Engineering, Florida Atlantic University and the Director of the Empirical Software Engineering Laboratory. His research interests are in software engineering, software metrics, software reliability and quality engineering, computational intelligence, computer performance evaluation, data mining, and statistical modeling. He has published more than 200 refereed papers in these areas. He has been a principal investigator and project leader in a number of projects with industry, government, and other research-sponsoring agencies. He is a member of the Association for Computing Machinery, the IEEE Computer Society, and IEEE Reliability Society. He served as the general chair of the 1999 International Symposium on Software Reliability Engineering (ISSRE’99), and the general chair of the 2001 International Conference on Engineering of Computer Based Systems. Also, he has served on technical program committees of various international conferences, symposia, and workshops. He has served as North American editor of the Software Quality Journal, and is on the editorial boards of the journals Empirical Software Engineering, Software Quality, and Fuzzy Systems. Naeem Seliya received the M.S. degree in Computer Science from Florida Atlantic University, Boca Raton, FL, USA, in 2001. He is currently a Ph.D. candidate in the Department of Computer Science and Engineering at Florida Atlantic University. His research interests include software engineering, computational intelligence, data mining, software measurement, software reliability and quality engineering, software architecture, computer data security, and network intrusion detection. He is a student member of the IEEE Computer Society and the Association for Computing Machinery.     

PEM: The small company-dedicated software process quality evaluation method combining CMMISM and ISO/IEC 14598

Many small software organizations have recognized the need to improve their software product. Evaluating the software product alone seems insufficient since it is known that its quality is largely dependant on the process that is used to create it. Thus, small organizations are asking for evaluation of their software processes and products. The ISO/IEC 14598-5 standard is already used as a methodology basis for evaluating software products. This article explores how it can be combined with the CMMI to produce a methodology that can be tailored for process evaluation in order to improve their software processes. ^SM: CMMI is a service mark of Carnegie-Mellon University. Sylvie Trudel has over 20 years of experience in software. She worked for more than 10 years in development and implementation of management information systems and embedded real-time systems. Since 1996, she works as a process improvement specialist, implementing best practices into organizations processes from CMM and CMMI models. She performed several CMM and CMMI assessments and participated in many other CMM assessments such as CBA IPI, SCE, and other proprietary methods. She obtained a bachelors degree in computer science in 1986 from Laval University in Québec City and a Masters degree in Software Engineering at école de Technologie Supérieure (éTS) in Montréal. Sylvie is currently working as a software engineering advisor at the Centre de Recherche Informatique de Montréal (CRIM). Jean-Marc Lavoie has been working in software development for over 10 years. He performed and published a comparative study between the guide to the SWEBOK and the CMMI in 2003. Jean-Marc obtained a bachelor degree in Electrical Engineering. He is pursuing a Masters degree in Software Engineering at école de Technologie Supérieure (éTS) in Montréal while working as a software architect at Trisotech. Marie-Claude Pare has been working in software development for 7 years. Marie-Claude obtained a bachelor degree in Software Engineering from école Polytechnique in Montréal. She is pursuing a Masters degree in Software Engineering at école de Technologie Supérieure (éTS) in Montréal while working as a software engineer at Motorola GSG Canada. Dr Witold Suryn is a Professor at the école de technologie supérieure, Montreal, Canada (engineering school of the Université du Québec network of institutions) where he teaches graduate and undergraduate software engineering courses and conducts research in the domain of software quality engineering, software engineering body of knowledge and software engineering fundamental principles. Dr Suryn is also the principal researcher and the director of GELOG : IQUAL, the Software Quality Engineering Research Group at école de technologie supérieure. From October 2003 Dr. Suryn holds the position of the International Secretary of ISO/IEC SC7 – System and Software Engineering.     

On specifying software quality

Quality is recognized as a pre-eminently important characteristic of software, yet an understanding of how to usefully define it, and how to achieve it remains illusive. A constructive definition of quality is investigated and an approach to the construction of software of quality is suggested. The definition focusses on how well the solution fits the problem, the inherent quality of the design independent of the problem, and the quality of the design process that creates the solution. A constructive specification of software quality then follows based on the use of programming language syntax, design principles and strategies, post-construction program quality analysis systems, and computer-assisted program construction tools. Only by addressing the problem on much broader methodological, technical, and managerial fronts will it be possible to make significant gains in software quality.Professor of Computing and Information Technology and Director of the Australian Software Quality Research Institute at Griffith University, Brisbane.Head of Department of the Computer Science Department at Strathclyde University, Glasgow from 1984–90.     

A model for software product quality

A model for software product quality is defined, it has been formulated by associating a set of quality-carrying properties with each of the structural forms that are used to define the statements and statement components of a programming language. These quality-carrying properties are in turn linked to the high-level quality attributes of the International Standard for Software Product Evaluation ISO-9126. The model supports building quality into software, definition of language-specific coding standards, systematically classifying quality defects, and the development of automated code auditors for detecting defects in software     

The EMISQ method and its tool support-expert-based evaluation of internal software quality

There is empirical evidence that internal software quality, e.g., the quality of source code, has great impact on the overall quality of software. Besides well-known manual inspection and review techniques for source code, more recent approaches utilize tool-based static code analysis for the evaluation of internal software quality. Despite the high potential of code analyzers the application of tools alone cannot replace well-founded expert opinion. Knowledge, experience and fair judgment are indispensable for a valid, reliable quality assessment, which is accepted by software developers and managers. The EMISQ method (Evaluation Method for Internal Software Quality), guides the assessment process for all stakeholders of an evaluation project. The method is supported by the Software Product Quality Reporter (SPQR), a tool which assists evaluators with their analysis and rating tasks and provides support for generating code quality reports. The application of SPQR has already proved its usefulness in various code assessment projects around the world. This paper introduces the EMISQ method and describes the tool support needed for an efficient and effective evaluation of internal software quality.     

The impact of software evolution and reuse on software quality

This paper presents a case study of a software project in the maintenance phase. The case study was based on a sample of modules, representing about 1.3 million lines of code, from a very large telecommunications system. Software quality models were developed to predict the number of faults expected from the coding through operations phases. Since modules from the prior release were often reused to develop a new release, one model incorporated reuse data as additional independent variables. We compare this model's performance to a similar model without reuse data.Software quality models often have product metrics as the only input data for predicting quality. There is an implicit assumption that all the modules have had a similar development history, so that product attributes are the primary drivers of different quality levels. Reuse of software as components and software evolution do not fit this assumption very well, and consequently, traditional models for such environments may not have adequate accuracy. Focusing on the software maintenance phase, this study demonstrated that reuse data can significantly improve the predictive accuracy of software quality models.     

Software quality management in turbulent times – are there alternatives to process oriented software quality management?

Software Quality Journal - There is a widely accepted paradigm of successful software development, called process oriented software quality management (PSQM). The proponents of PSQM claim that it...     

A fuzzy regression and optimization approach for setting target levels in software quality function deployment

With the rapid development of the software industry, improving the quality of software development has gained increasing importance. Software manufacturers have recently applied quality improvement techniques to software development to respond to the needs for software quality. Software quality function deployment (SQFD), as a technique for improving the quality of the software development process to create products responsive to customer expectations, is used to maximize customer satisfaction. This paper presents a fuzzy regression and optimization approach to determine target levels in SQFD. The inherent fuzziness of relationships in SQFD modeling justifies the use of fuzzy regression. Fuzzy regression is used to identify the functional relationships between customer requirements and technical attributes, and among technical attributes. Then, a mathematical programming model is developed to determine target levels of technical attributes using the functional relationships obtained by fuzzy regression. A search engine quality improvement problem is presented to illustrate the application of the proposed approach.     

Design of Characteristic Curriculum on Software Engineering Major for Undergraduate-Graduate Education

The concept of "New Engineering" has put forward new challenges to the talents cultivation of universities. Due to some problems of the traditional Software Engineering curriculum, e.g. separated design at undergraduate-level and graduate-level courses, poor curriculum structure, lacking of industry characteristics. This paper proposes an integrated undergraduate-graduate education curriculum for Software Engineering Major, which is based on Software Engineering specialty knowledge system (C-SWEBOK) and focuses on the current national strategic demands. Additionally, the curriculum combines with the University's transportation characteristics, and fuses the discipline of Software Engineering and Intelligent Transportation. The multi-level curriculum designed in this paper is with reasonable structure, complete system, progressive content, and salient feature, which provides the strong support for cultivating high-qualified software talents in line with national strategies and industry needs.     

Evaluating the service quality of software providers appraised in CMM/CMMI

Recently, several companies have decided to adopt maturity models such as the CMM/CMMI to ensure quality software processes. The state year report of the Software Engineering Institute (SEI) showed that more than three thousand CMMI appraisals have been conducted since 2002. Many of these were performed at software providers, i.e. companies that develop software for other companies. Although the costs of the implementation and appraisal of CMM/CMMI are high for the software providers, there is no formal study investigating whether this investment pays off or, in other words, whether their customers are measurably satisfied with the quality of the service provided. This article presents the results of a formal evaluation of customer perception of the service quality offered by the software providers appraised in CMM/CMMI. We developed an instrument based on a widely used service quality evaluation model (SERVQUAL) and applied this instrument to several customers of software providers appraised in CMM/CMMI. The results show a considerable discrepancy between customers’ expectations and their perceptions of the services provided.     

A framework for software process deployment and evaluation

ContextSoftware Process Engineering promotes the systematic production of software by following a set of well-defined technical and management processes. A comprehensive management of these processes involves the accomplishment of a number of activities such as model design, verification, validation, deployment and evaluation. However, the deployment and evaluation activities need more research efforts in order to achieve greater automation.ObjectiveWith the aim of minimizing the required time to adapt the tools at the beginning of each new project and reducing the complexity of the construction of mechanisms for automated evaluation, the Software Process Deployment & Evaluation Framework (SPDEF) has been elaborated and is described in this paper.MethodThe proposed framework is based on the application of well-known techniques in Software Engineering, such as Model Driven Engineering and Information Integration through Linked Open Data. It comprises a systematic method for the deployment and evaluation, a number of models and relationships between models, and some software tools.ResultsAutomated deployment of the OpenUP methodology is tested through the application of the SPDEF framework and support tools to enable the automated quality assessment of software development or maintenance projects.ConclusionsMaking use of the method and the software components developed in the context of the proposed framework, the alignment between the definition of the processes and the supporting tools is improved, while the existing complexity is reduced when it comes to automating the quality evaluation of software processes.     

Increasing testing productivity and software quality: A comparison of software testing methodologies within NASA

Pressure to compress the development life cycle and reduce the duration and resources committed to testing lead to experimentation in testing at the NASA Goddard Space Flight Centerís Software Engineering Laboratory. This study investigates the trend to reduce developer testing and increasingly rely upon inspection techniques and independent functional testing to shorten the development life cycle, improve testing productivity, and improve software quality.An approach is developed to conduct this comparison. In particular, the problem faced by software researchers, having a comprehensive characterization of software projects so similar types may be identified for comparative studies, is addressed using expert opinion.     

高素质软件工程人才培养模式

为培养适应软件产业需求的人才,示范性软件学院制定了"多层次、实用型、复合型、国际化"的办学目标。文章以分析示范性软件学院的办学目标为切入点,提炼软件工程人才的能力模型——"三角塔"能力模型,并结合重庆大学软件学院的实际,提出系统化地建立科学有效的培养体系,即以"根基(逻辑推理、语言能力、专业基础)+三个面(实践操作面、非技术专业素质面、综合素质面)"为导向,构建"实基础+三主线(技术实践主线、工程实践主线、学生工作主线)"的人才能力培养体系。     

How ISO 9001 fits into the software world

ISO 9001, together with its companion guide, ISO 9000-3, is a key standard for many suppliers, but its focus is on the control of manufacturing processes. The author considers how this fits into software development and how ISO 9001 stacks up to the US National Institute of Standards and Technology's Malcolm Baldridge Quality Award and the Software Engineering Institutes's Capability Maturity Model     

TQM implementation factors for software development: an empirical study

Software Quality Journal - There is a need for methodologies which can enhance the quality of software and improve software developmental efficiencies. One such approach commonly used by software...