Proposed Metrics for Process Capability Analysis in Improving Software Quality: An Empirical Study (original) (raw)
Related papers
Applicability of Process Capability Analysis in Metrifying Quality of Software
2016
Defects occurrence during software development process is a common phenomenon and its consequences in software organizations are inevitable. This can result in software failure or delayed delivery of product. Defect removal procedure is obviously an option but on the other hand it, it can affect the budget of organization. Organizations are demanding timely delivery of defect free and high quality software. Besides defect removal, defect prevention techniques must be encouraged during development. It should be considered as an ongoing process during development to enhance quality and testing efficiency. The paper is an empirical work enhancing the relevance of some of process enhancing metrics. These metrics are useful in monitoring the on-going software development and meeting the quality standards. The paper explores the applicability of capability analysis metrics for defect prevention and how it can be used as technique for upgrading software quality.
SOFTWARE QUALITY IMPROVEMENT THROUGH STATISTICAL ANALYSIS ON PROCESS METRICS
Software Quality can be considered as totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs. The Quality of any software can be achieved by following by well-defined software process. These software process results into various metrics like Project metrics, Process metrics and Product metrics. Process metrics are very useful from management point of view. Process metrics can be used for improving the software development and maintenance process for defect removal and also for reducing the response time. This paper describes on importance of capturing the Process metrics during the quality audit process and also attempts to categorize them based on the nature. To reduce such defect, corrective actions are recommended.
Software Quality Journal, 2007
This paper reports on a survey amongst software groups in a multinational organization. The survey was initiated by the Software Process Improvement (SPI) Steering Committee of Philips, a committee that monitors the status and quality of software process improvement in the global organization. The paper presents and discusses improvement targets, improvement drivers, and metrics, and the degree to that they are being recognized in the software groups. The improvement targets ‘increase predictability’ and ‘reduce defects’ are being recognized as specifically important, joined for Capability Maturity Model (CMM) level three groups by ‘increase productivity’ and ‘reduce lead time’. The set of improvement drivers that was used in the survey appears to be valid. Three improvement drivers that were rated highest were: ‘commitment of engineering management’, ‘commitment of development staff, and ‘sense of urgency’. Finally, it could be seen that metrics activity, both in size and in quality, increases significantly for CMM level three groups. However, no consensus regarding what metrics should be used can be seen.
International Journal of Advanced Research in Computer Science and Software Engineering, 2017
Software quality assurance is a process for guesstimating and documenting the quality of the software products during each phase of the software development lifecycle. Measurement provides a way to assess the status of any program to determine if it is in trouble or in need of corrective action and process of improvement. This assessment helps to diagnose the status in terms of time, completion, risks and also the quality and thus ensures to take meaningful, effective remedial action (e.g., controlling requirements changes, improving response time to the developer, relaxing performance requirements, extending your schedule, adding money, or any number of options). Successful software quality assurance is highly dependent on software metrics. The purpose of this paper is to give a clear picture about the application of Software Quality Metrics (SQM) in quality life cycle and to focus on the significance of SQM in the role of external factors, mainly concentrating on time, which will influence the quality of the final product and plays a vital role in the software quality.
Software process improvement and capability determination: selected articles from SPICE 2009
Journal of Software Maintenance and Evolution: Research and Practice, 2000
The Appraisal Assistant process assessment tool has been developed to support the assessment or appraisal of process capability and/or organizational maturity, following approaches consistent with the requirements of ISO/IEC 15504 and the Appraisal Requirements for the Capability Maturity Model ® Integration (CMMI ® ). In the course of an assessment a workload data file is captured containing information on the volume and usage of collected evidence in the assessment. This paper presents an analysis of evidence usage data from a total of 20 assessments employing a range of Process Assessment Models and Assessment Methods. Key differences between ISO/IEC 15504-based and CMMI-based assessments are identified, and some explanations of the differences are offered.
Software industries require reliability prediction for quality evaluation and resource planning. In early phase of software development, failure data is not accessible to conclude the reliability of software. However, early software fault prediction procedure provides a flexibility to predict the faults in early stage. In this paper, a software faults prediction model is proposed using BBN that focus on the structure of the software development process explicitly representing complex relationship of five influencing parameters (Techno-complexity, Practitioner Level, Creation Effort, Review Effort, and Urgency). In order to assess the constructed model, an empirical experiment has been performed, based on the data collected from software development projects used by an organization. The predicted fault ware found very near to the actual fault detected during testing.
Case studies of software-process-improvement measurement
Computer, 1994
Siemens softwaredevelopment organizations are casestudy sites in a research project with the Software Engineering Institute. The effort has yielded suggestions for promoting softwareprocess improvement. oftware measurement is becoming integral to improving software development. The approach begins with a documented software-development process. A business enterpriseon the basis of its strategic objectivesestablishes goals to improve the process over a specified period of time. Then it defines measures to periodically gauge progress in achieving the improvement goals. When the data collected indicates development-process problems, the enterprise can formulate corrective actions and compare them to determine the best return on investment for software-process improvement. Figure 1 shows how measures play a key role in a closed-loop feedback mechanism for incremental improvements to the software-development process over time.' These process improvements result in higher quality products, thus increasing the business enterprise's competitiveness. In this article, we describe an ongoing research project conducted jointly by Siemens and the Software Engineering Institute. Siemens software-development organizations in Germany and the United States are case-study sites at which we measure the effect of methods to improve the software-development process. To observe and quantify the impact of software-process improvement, we must measure the performance of a software-development organization over time. Comparison of performance across organizations is very difficult, since organizations define measures and collect performance data in different ways. However, we can separately track performance improvement in each organization if it defines measures consistently and develops similar products. We have defined basic measures for performance of a software-development organization. We limited ourselves to a small number of simple measures to reduce the complexity of collecting, analyzing, and maintaining the performance data. Improving the software-development process improves the quality of software products and the overall performance of the software-development organization? However, as Figure 2 shows? process is only one of several controllable factors in improving software quality and organization performance. Others include the skills and experience of the people developing the software, the technology used (for example, CASE tools), product complexity, and environmental characteristics such as schedule pressure and communications.
Modelling the Likelihood of Software Process Improvement: An Exploratory Study
Empirical Software Engineering, 2001
Software process assessments have become big business worldwide. They can be a powerful tool for initiating and sustaining software process improvement (SPI). However, SPI programs sometimes fail. Moreover there still are very few systematic empirical investigations about the conditions under which SPI initiatives vary in their outcomes. In this paper we present the results of a study of factors that influence the success of SPI. The data come from a sample survey of organizations that have performed assessments based on the capability maturity model for software, and was conducted from 1 to 3 years after the assessments (sufficient time had passed for changes to have taken place). The results consist of a multivariate model of the conditions (e.g., how the improvement efforts are organized and funded) that can explain the successes and failures of SPI efforts. The model is constructed using a classification tree algorithm. It identifies the most important factors that affect the outcome of SPI efforts, and describes how those factors interact with each other to influence success or failure.