case study on software quality metrics

Abstract. This paper aims at analyzing empirically the quality evolution of an open source software using metrics. We used a control flow based metric (Quality Assurance Indicator-Qi) which we ...

Empirical results provide evidence that the Qi metric reflects properly the quality evolution of the subject system, and addressed software quality from an internal perspective. This paper aims at analyzing empirically the quality evolution of an open source software using metrics. We used a control flow based metric (Quality Assurance Indicator - Qi) which we proposed in a previous work. We ...

This paper presented an explorative case study on how we can optimize the presentation of software metrics indicators in industrial measurement systems. In the course of this case study we identified and evaluated 4 different ways of presenting indicators: dashboards, tables with colors, arcs, and thermometers.

part of the paper, we focus on one specific code quality metric— LCOM as a case study to explore opportunities towards improved metrics. ... Index Terms—metrics, code quality, software metrics I. BACKGROUND A software metric quantifies a characteristic or an attribute of a software product, process, or project [1]-[3] that could

Murgia et al. [18] address software quality evolution in open source projects using agile practices. The authors used a set of OO metrics to study software evolution and its relationship with bug distribution. According to the achieved results, Murgia et al. concluded that there is no a single metric that is

measured by means of internal quality metrics [9]. According to Lanza and Marinescu [10] software metrics are created by mapping a particular characteristic of a measured entity to a numerical value or by assigning it a categorical value. Over the last past 40 years, a significant number of software metrics have been proposed in order to

We propose a spiral process model for case studies, and present a study conducted according to the proposed process. In the study, metrics collected from three software development projects are analysed to investigate which characteristics are stable across projects and feature groups of the product.

In the context of an EU H2020 Project, we conducted a multiple case study to investigate how two software-intensive Agile companies utilized a metrics program in their software development. We invited practitioners from the two case companies to report on the actual use of the metrics program, the underlying rationale, and any benefits they may ...

In this paper, we propose a SQuaRE-based software quality evaluation framework, which successfully concretized many product metrics and quality in use metrics originally defined in the SQuaRE series 1. Through a case study targeting a commercial software product, we confirmed that our framework is concretely applicable to the software package ...

Abstract: As the software industry transitions from a license-based model to a subscription-based Software-as-a-Service (SaaS) model, many software development organizations are transforming to a hybrid development model using agile and CI/CD practices for some products while continuing to use waterfall methods for other products. The traditional metrics used for measuring software quality in ...

A categorisation of value-oriented quality metrics, whose necessity was identified through empirical case studies and the lack of the same criticised by several authors [5, 18, 19]. Empirical findings regarding the practical relevance of value-oriented quality metrics from the perspectives of software engineering practitioners. The authors of Refs.

The source code is analyzed using cloc [13], a tool to compute basic metrics about source code (size, expressed in lines of code and comments). A database (Local DB, in Fig. 1), which we use to locally integrate and store all the information we need. The database is then queried by users to perform analyses. Figure 1.

For this reason, we decided to focus our study on two measurement aspects: (a) QR metrics, defined as metrics used to measure QRs, and (b) Quality Management Indicators (QMIs), defined as indicators used in the context of quality management, usually as input for some decision-making processes at a strategic level.

A spiral process model for case studies on software quality monitoring—method and metrics . × ... In the study, metrics collected from three software development projects are analysed to investigate which characteristics are stable across projects and feature groups of the product. The contribution of the article is multi-fold, detailing the ...

Software metrics play an essential part in understanding and controlling the overall software engineering process [2]. Software metrics can, particularly, be used to analyze the evolution of the quality of software systems [10]. Metrics have, in fact, a number of interesting characteristics for providing evolution support [11].

Quality model is regarded as a well-accepted approach for assessing, managing and improving software product quality. There are three categories of quality models for software products, i.e., definition model, assessment model, and prediction model. Quality assessment model (QAM) is a metric-based approach to assess the software quality. It is typically regarded as of high importance for its ...

Now let's understand each quality metric in detail -. 1. Code Quality - Code quality metrics measure the quality of code used for software project development. Maintaining the software code quality by writing Bug-free and semantically correct code is very important for good software project development. In code quality, both Quantitative ...

The National Security Agency's (NSA) mission is to provide support for the security of the United States. Over the years, the Agency has become extremely dependent on the software that makes up its information technology infrastructure. NSA has come to view software as a critical resource upon which much of the world's security, prosperity, and economic competitiveness increasingly rests. To ...

Software quality metrics evolve with advancements in development, the rising role of AI and ML in QA, and the effort to balance quantitative and qualitative elements. Challenges include metric overload, data accuracy, and resistance to change. Ethical concerns and potential misuse must be responsibly addressed. ‍.

In this paper we first introduce the theoretical concept of object oriented metrics, specifically of CK metrics suite. Then a case study of analyzing Java based open source software using CK metrics to evaluate quality is presented. The results are interpreted to help the software developers and researchers in improving the quality of the ...

In this paper we present a metric scheme to quantify organizational complexity, in relation to the product development process to identify if the metrics impact failure-proneness. In our case study, the organizational metrics when applied to data from Windows Vista were statistically significant predictors of failure-proneness.

Measuring Software Quality: A Case Study. Thomas Drake. National Security Agency. To ensure cost-effective delivery of high-quality software, NSA has analyzed effective quality measures applied to a sample code base of 25 million lines. This case study dramatically illustrates the benefits of code-level measurement activities.