Applicability of Process Capability Analysis in Metrifying Quality of Software (original) (raw)
Related papers
Proposed Metrics for Process Capability Analysis in Improving Software Quality: An Empirical Study
International Journal of Software Engineering and Technologies (IJSET), 2016
A software project faces its top expense on defect removal; thereby delaying the schedules. There has been increasing demand for high quality software. Here, high quality software means, delivering defect free software and meeting the predictable results within time and cost constraints. Software defect prediction strives to improve software quality and testing efficiency. The research work presented here is an empirical study and analyzes importance of different metrics used in the organization. The paper examines the impact of LSL and USL, known as organization baselines, on various projects and proposes four metrics for capability analysis metrics. These can prove beneficial for categorizing the process of software development. These metrics aim to improve the ongoing software development process and are helpful in determining the quality of these processes in terms of their specification limits. Also, the paper attempts to justify the probability of the values related to the dat...
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 Process Improvement, Quality Assurance and Measurement
13th IEEE International Workshop on Software Technology and Engineering Practice (STEP'05), 2005
The article focuses on a problem software companies often face: the need to choose a software quality model that, besides being auditable, ensures the connection of quality goals to the business goals of that company. A good solution seems to be to quit relying exclusively on one quality model and use more models in a synergic way instead. We explain a possibility to handle this problem by using a framework that helps positioning the existing software quality approaches and standards according to the basic elements of software production they address, and gives guidance in the sequence of possible steps to do really efficient software process improvement. We present the elements of the framework and a possibility to use it to implement certain CMMI requirements.
A survey of software quality metrics for software measurement process
Journal of Software Engineering & Intelligent Systems, 2017
Software measurement process is a process that measures, adjusts, evaluates, and improves the software development process. Software metrics may be used in different models to improve software quality. This paper aims to identify software metrics to increase knowledge of the reasons and effects of using metrics and to evaluate their applicability in software development. Therefore, we use previous studies in the literature in order to describe the fundamental aspects of the software quality metrics. We discuss several metrics of software quality metrics: product quality, inprocess quality, testing quality, and customer satisfaction quality. Process metrics have been seemed more successful in discovering faults as compared to complexity metrics and traditional size.
Software quality assurance-concepts and misconceptions
Proceedings. 24th EUROMICRO Conference (Cat. No.98EX204), 1998
Software quality engineering is concerned with building software products with required quality and assessing the level of quality. Software processes are important assets in achieving and assessing the software quality. Furthermore the adherence to defined processes is a key issue to having the software engineering under control and to enable process improvement. In this paper, the Software Quality Assurance (SQA) key process area in the Capability Maturity Model (CMM) is elaborated, i.e. activities for monitoring adherence to the processes. The term SQA creates some misconceptions and confusions with the general quality management concept. The SQA concept is compared to quality management and the differences and similarities are elaborated in order to eliminate the misconceptions. Furthermore, some experiences from supporting the implementation of the SQA concepts in two different software companies are briefly reported.
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.
Improvement and Implementation of Software Quality by Using Software Metrics
Without the software development and software product knowledge it's very complicated to understand, keep away from improvement in the quality of software. There should be some dimension process to forecast the software development, and to appraise software products and its quality. In This paper provides a brief view on Software Metrics, Software Quality and Software Metrics techniques that will forecast and evaluate the specified superiority factors of software which will relate to quality. It additional discusses regarding the Quality as given through the principles like ISO, principal elements necessary for the Software Metrics and Software Quality as the measurement method to forecast the Quality in the Software. Java source code evolution are using for Software Metrics, like Defect Metrics, Size Metrics, and Complexity Metrics. Presented experiments are proving that, the software quality can be analyzed, observed, and enhanced through software metrics usage.
DEFECT PREVENTION AND CHANGE MANAGEMENT, KEYS TO SOFTWARE PROCESS OPTIMIZATION
Defect Prevention, Technology Change Management, and Process Change Management have been identified as the key process areas in software process optimization. The Optimizing Level is the peak in the scale of Software Process ranking. This paper reviews the performance of these key process areas by some selected software industries. Emphasis is made on the results obtained from a recent study carried out on the Nigerian software industry. The findings of the study are presented and discussed. Discussions include comparing practices in the Nigerian software industry at the optimizing level, with results obtained from other software industries. Defect Prevention involves analyzing defects that were encountered in the past and taking specific actions to prevent the occurrence of those types of defects in the future. Technology Change Management involves identifying, selecting, and evaluating new technologies, and incorporating effective technologies into the organization. Process Change Management involves defining process improvement goals and, with senior management sponsorship, proactively and systematically identifying, evaluating, and implementing improvements to the organization’s standard software process on a continuous basis.
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.
Effective defect prevention approach in software process for achieving better quality levels
arXiv preprint arXiv:1001.3552, 2010
Defect prevention is the most vital but habitually neglected facet of software quality assurance in any project. If functional at all stages of software development, it can condense the time, overheads and wherewithal entailed to engineer a high quality product. The key challenge of an IT industry is to engineer a software product with minimum post deployment defects.