Interrelations between Software Quality Metrics, Performance and Energy Consumption in Embedded Applications

Aims: Software quality assurance is a formal process for evaluating and documenting the quality of the work products during each stage of the software development lifecycle.The practice of applying software metrics to operational factors and to maintain factors is a complex task.Successful software quality assurance is highly dependent on software metrics.It needs linkage the software quality model and software metrics through quality factors in order to offer measure method for software quality assurance.The contributions of this paper build an appropriate method of Software quality metrics application in quality life cycle with software quality assurance.Design: The purpose approach defines some software metrics in the factors and discussed several software quality assurance model and some quality factors measure method.Methodology: This paper solves customer value evaluation problem are: Build a framework of combination of software quality criteria.Describes software metrics.Build Software quality metrics application in quality life cycle with software quality assurance.Results: From the appropriate method of Software quality metrics application in quality life cycle with software quality assurance, each activity in the software life cycle, there is one or more QA quality measure metrics focus on ensuring the quality of the process and the resulting product.Future research is need to extend and improve the methodology to extend metrics that have been validated on one project, using our criteria, valid measures of quality on future software project.

Numerous virtual environments with automatic program evaluation have emerged to assist the teaching-learning process, allowing timely feedback. In a review of these environments, we find few studies that focus on an approach centered on refactoring: where students are strongly encouraged to refactor, improving the submitted code to also meet quality criteria. In a traditional environment, the student submits the answer and if it is dynamically correct, he goes to the next question. In this work, we propose a complementary approach based on software engineering metrics, which allow a finer evaluation of the code where the programmer, after having his dynamically correct answer, is invited and encouraged to refactor his solution towards an optimal code that also meets the software quality metrics. The work is based on source code in the Python language and shows which software quality metrics can be used with the purpose of encouraging students to refactor their code in programming fundamentals disciplines.

Software quality indicates how effective and efficient a software is. Various standards need to be used to evaluate software quality. One of the most important internationally accepted standards for measuring software quality is the ISO/IEC 25010 software quality standard. With this standard, the quality of a software product is evaluated with eight different metrics. These are functional suitability, performance, compatibility, usability, reliability, security, maintainability and portability metrics. In this study, we tried to determine the relationship between user feedback and the metrics of the ISO/IEC 25010 software quality standard. Machine learning (ML) and natural language processing (NLP) techniques were used to classify user comments. After the data preprocessing phase, vectors of user comments were extracted with the Tf-Idf method for NLP. As a machine learning method, classification was made using five different models: Extra Trees Classifier (ETC), Gaussian Process Classifier (GPC), MLP Classifier (MLPC), Bernoulli Naive Bayes Classifier (BNBC) and Support Vector Classifier (SVC). Our goal is to show how quality metrics can be classified into multiple classes using user notifications. The data set used has an unbalanced structure, containing 1681 user comments classified by software experts. Synthetic Minority Oversampling Technique (SMOTE) was used to address the imbalance in the dataset. The results were compared by applying the same classification models to unbalanced and balanced data sets. According to the results obtained, the best classification model is the Extra Trees Classifier model, which provides the highest accuracy rate of 87% according to the SMOTE applied data set. The results show that ML and NLP methods can be used effectively in the classification process of software quality metrics.

Leveraging and acting on the results of static analysis is a well-known best practice. Static analysis also is an integral part of software quality assurance which is highlighted by the inclusion of static analysis results in software quality models like ColumbusQM and Quamoco. Although there are studies that explore if tools for static analysis are used and how they are configured, few publications explore the longitudinal effects of acting on static analysis results on software and on the evolution of software. Especially effects on quality criteria, e.g., software quality metrics, defects, or readability are missing. With our research, we will bridge this gap and measure the effects of static analysis on software quality evolution. We will measure the effect the removal of code that generates static analysis warnings has on software quality metrics. Furthermore, we will measure long term effects on external quality attributes, e.g., reported issues and defects. Finally, we want to predict false positives of static analysis warnings by training predictive models on our collected data.

Although many improvements for software development are proposed by software engineers, the embedded system community faces a hard task in applying these improvements to software development, due to the strong dependence between software and hardware in embedded systems, which raises a trade-off between software quality, measured by traditional metrics, and optimization for a specific platform. Traditional software quality concerns reuse, abstraction, coupling, and coherence. Such concepts are usually in conflict with performance, memory footprint, and other physical metrics used for design evaluation in embedded systems. The purpose of this work is to evaluate the relationship between quality metrics for software products and physical metrics for embedded systems, in order to guide an embedded designer in selecting the best alternative design during design space exploration already at the model level. After the experiments, we could analyze the correlation between these metrics and highlight the behavior for quality and physical metrics, which help us to better understand the trade-off between reuse and optimization.

Virtual Reality (VR) Software is becoming more mainstream in recent years. It has provided an opportunity for VR practitioners to explore new domains and deliver cutting edge products. The success of the VR products depends primarily on the product contextual relevance and qualities exhibited. However, it is unclear how VR practitioners curb software quality challenges and improve the essence of the VR product over every release. In this paper, we present a Systematic Mapping Study of the software quality metrics adopted by VR practitioners for assessing the quality of their VR products. The study showed that practitioners used unique metrics to measure the quality of their VR products in addition to adopting some of existing enterprise software metrics. Further, we consolidate these metrics into different themes that future practitioners may use for developing VR products.

PurposeThe purpose of this paper is to evaluate and compare open source and proprietary discovery tools and find out how much discovery tools have achieved towards becoming the next generation catalog.Design/methodology/approachThe paper summarizes characteristics of the next generation catalog into a check‐list of 12 features. This list was checked against each of seven open source and ten proprietary discovery tools to determine if those features were present or absent in those tools.FindingsDiscovery tools have many next generation catalog features, but only a few can be called real next generation catalogs. Federated searching and relevancy based on circulation statistics are the two areas that both open source and proprietary discovery tools are missing. Open source discovery tools seem to be bolder and more innovative than proprietary tools in embracing advanced features of the next generation catalog. Vendors of discovery tools may need to quicken their steps in catching up.Originality/valueIt is the first evaluation and comparison of open source and proprietary discovery tools on a large scale. It will provide information as to exactly where discovery tools stand in light of the much desired next generation catalog.

: The Rome Air Development Center has developed the Software Quality Framework as a means to specify software quality goals and measure software quality. Much of the work to date has focused on metrics applicable to software code. This report describes an effort undertaken to measure the quality of software products earlier in the software development life cycle, during the design phase, and to automate the capture of metric data from design media. Metrics of software quality, primarily those related to the criterion simplicity (or conversely, complexity), were reviewed. This review includes those metrics previously developed in the Software Quality Framework. Two metrics, Halstead's Software Science and McCabe's Cyclomatic Complexity were chosen for their amenability to measurement during design and their potential for automation. Two design media were used: Design Aids for Real-Time Systems, an experimental automated design tool developed at the Charles Stark Draper Laboratory; and Ada as a program design language.

One of the first steps towards the effective Technical Debt (TD) management is the quantification and continuous monitoring of the TD principal. In the current state-ofresearch and practice the most common ways to assess TD principal are the use of: (a) structural proxies—i.e., most commonly through quality metrics; and (b) monetized proxies—i.e., most commonly through the use of the SQALE (Software Quality Assessment based on Lifecycle Expectations) method. Although both approaches have merit, they seem to rely on different viewpoints of TD and their levels of agreement have not been evaluated so far. Therefore, in this paper, we empirically explore this relation by analyzing data obtained from 20 open source software projects and build a regression model that establishes a relationship between them. The results of the study suggest that a model of seven structural metrics, quantifying different aspects of quality (i.e., coupling, cohesion, complexity, size, and inheritance) can accurately estimate TD principal as appraised by SonarQube. The results of this case study are useful to both academia and industry. In particular, academia can gain knowledge on: (a) the reliability and agreement of TD principal assessment methods and (b) the structural characteristics of software that contribute to the accumulation of TD, whereas practitioners are provided with an alternative evaluation model with reduced number of parameters that can accurately assess TD, through traditional software quality metrics and tools.

In spite of the significant body of research on traditional source code metrics, there has been a general failure to produce conclusive evidence as to their effectiveness for measuring software quality. We describe and recommend a potentially much more powerful and sensitive quality assessment alternative, software quality guidelines. Software quality guidelines are presented as “designer metrics”, that is, user-defined rules or constraints relating to measurable features of a program's structure, semantics, and syntax that affect its quality. To provide a methodology for designing, applying, and validating software quality guidelines, we recommend and briefly summarize IEEE standard 1061. This standard gives a process for constructing and implementing a software quality metrics framework that can be tailor-made to meet quality requirements for a particular project and/or organization. Our paper then demonstrates how software quality guidelines fit within the IEEE framework and gives an example illustrating how user-defined guidelines can be applied to evaluate or assess the quality of an Ada source unit. This guideline-based assessment of quality is then compared with an analysis based on traditional McCabe and Halstead metrics. Finally, we introduce a tool being developed by SAIC, called AdaReVu, as an effective mechanism for implementing and applying user-defined quality guidelines for Ada source code.

Software is a product in serious need of quality control technology. Major effort notwithstanding, software engineering has produced few metrics for aspects of software quality that have the potential of being universally applicable. The present paper suggests that, although universal metrics are elusive, metrics that are applicable and useful in a fully defined setting are readily available. A theory is presented that a well‐defined software work group can articulate their operational concept of quality and derive useful metrics for that concept and their environment.

: Software metrics (or measurements) which predict software quality have been refined and enhanced. Metrics were classified as anomaly-detecting metrics which identify deficiencies in documentation or source code, predictive metrics which measure the logic of the design and implementation, and acceptance metrics which are applied to the end product to assess compliance with requirements. A Software Quality Measurement Manual was produced which contained procedures and guidelines for assisting software system developers in setting quality goals, applying metrics and making quality assessments.

: The objective of this study was to conduct applied research directed toward understanding the relationship between the complexity or efficiency of algorithms and the overall quality of computer software. The final report is presented in a two volume series consisting of a total of eight parts. This volume, containing Parts 1 and 2, comprises a general introduction to the entire series and a research plan. Part 1 begins with a description of the goals of the overall contract effort. This is followed by a discussion of previous RADC work on software quality metrics, emphasizing measures concerned with the time and storage efficiency of programs. Next, an overview of the field of algorithm analysis and computational complexity is given. A final section contains an introduction to the particular research investigations pursued in the other portions of this study. Part 2 presents a research plan for advancing the state-of-the-art in the area of algorithm performance. An Appendix contains an outline of the major topics and issues addressed in the area of algorithm analysis and computational complexity, together with an annotated select bibliography.

Abstract---Taguchi-based software metrics (numerical software measurements) define software quality in terms of imparted to society after a software product is delivered to the end user. Previous work has focused on nominal-the-best and larger-the-best loss functions for estimating the loss to society. This paper focuses on the smaller-the-best loss function for estimating the loss to society. The smaller-the-best loss function is for a property whose value should be as small as possible. It is shown that the smaller-the-best loss function can be obtained from the nominal-the-best loss function by substituting zero for t, the target value in the nominal-the-best loss function. This derivation is illustrated and a case study utilizing the derivation is presented. Taguchi-based metrics are in line with six-sigma statistical quality control techniques that have been used with software products for several years. Experiences with Taguchi-based metrics have shown good correlation with existing popularly known software quality metrics.

Several studies have been proposed in the literature on software clones from different points of view and covering many correlated features and areas, which are particularly relevant to software maintenance and evolution. In this paper, we describe our experience on clone detection through three different tools and investigate the impact of clone refactoring on different software quality metrics.