Software Quality Metrics

Restoran merupakan salah satu jenis usaha yang mementingkan kualitas pelayanannya. Namun dalam kegiatan operasionalnya, masalah keterlambatan pelayanan sering muncul karena kurangnya koordinasi yang baik antar bagian. Salah satu faktornya adalah jarak antara dapur dan ruang makan. Sistem pengelolaan restoran terintegrasi dapat dibangun untuk mengurangi masalah tersebut. Namun pada penggunaannya, sistem harus memiliki kualitas yang baik agar dapat mendukung jalannya kegiatan operasional restoran. Sebab kualitas yang buruk pada sistem dapat berpotensi mengakibatkan error sehingga pihak yang menggunakannya dapat mengalami kerugian finansial. Penelitian ini membahas tentang pembangunan sistem pengelolaan restoran terintegrasi yang memenuhi standar karakteristik utama model kualitas ISO 9126. ISO 9126 memiliki enam karakteristik utama yaitu functionality, reliability, usability, efficiency, maintainability, dan portability. Functionality diuji dengan menggunakan pengujian validasi terhad...

Complexity measures can be used to predict critical information about testability, reliability and maintainability of the software systems from automatic analysis of the source code. In this paper different software complexity metrics were applied to searching algorithms. Our intention is to match vigorous object oriented applications (Visual Basic, C#, C++, Java and Python languages) of linear and binary search algorithms using software complexity metrics such as (Line of Codes (LOC), McCabe cylomatic complexity metrics and Halstead complexity metrics) and measured the sample program using LOC, McCabe method, the program difficulty using Halstead method and degree of relationship using Pearson correlation Coefficient and Statistical Analysis of Variance (ANOVA) for these three metrics. The five (5) languages correlate and do not differ significantly, then any of the five (5) programming languages is good to code linear and binary search algorithms.

Any software generally goes roughly through following phases in its life 1. Birth 2. Learning 3. Earning 4. Retiring From the business perspective, the software that stays in earning phase for longer time, can roughly be considered as a successful software (well, there can be some exceptions). Keeping this in mind, everyone who works with the software at any point of time in the life of software (irrespective of the role and responsibilities) should focus on working in such a way that software will stay in earning phase as long as possible. Even though we accept the fact that no software can stay in earning phase forever, it can certainly be tried to manage to provide optimum result. Everyone who works with the software at any point of time in any role leaves a mark on the software and contributes to increase or decrease in the overall life expectancy of the software. Therefore, this paper tries to study the software life expectancy, factors affecting it, its relation with different software quality attributes and processes to improve the software life.

This work presents an investigation of three different industrial
projects of software development by a Brazilian enterprise. During projects’
execution, the company has changed its approach on software processes from
RUP based process to agile like processes. To assess software product quality
metrics evolution, an investigation of product metrics history was conducted in
those three projects. This paper characterizes the use of eXtreme
Programming practices within the analyzed projects and the observed
measures of quality metrics in the developed software products

In this author's opinion, following are the most important software quality attributes - Reliability, Usability, Performance and Availability. As said wisely, "Things that count most, can not be counted mostly." This paper tries to suggest how 'Reliability' can be measured from end user's perspective.
For any software system, end user is the most important actor. Measuring ‘Reliability’ is a way to quantify the usefulness of the software for and end user. Therefore, measuring Reliability from an end user's perspective is very important. Unfortunately, there doesn't seem to be much discussion about how much reliable the software is for end user

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.

Developers continuously maintain software systems to adapt to new requirements and to fix bugs. Due to the complexity of maintenance tasks and the time-to-market, developers make poor implementation choices, also known as code smells. Studies indicate that code smells hinder comprehensibility, and possibly increase change-and fault-proneness. Therefore, they must be identified to enable the application of corrections. The challenge is that the inaccurate definitions of code smells make developers disagree whether a piece of code is a smell or not, consequently, making difficult creation of a universal detection solution able to recognize smells in different software projects. Several works have been proposed to identify code smells but they still report inaccurate results and use techniques that do not present to developers a comprehensive explanation how these results have been obtained. In this experimental report we study the effectiveness of the Decision Tree algorithm to recognize code smells. For this, it was applied in a dataset containing 4 open source projects and the results were compared with the manual oracle, with existing detection approaches and with other machine learning algorithms. The results showed that the approach was able to effectively learn rules for the detection of the code smells studied. The results were even better when genetic algorithms are used to pre-select the metrics to use.

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.

This paper aims to provide a basis for software quality model research, through a systematic study of papers. It identifies nearly seventy software quality research papers from journals and classifies paper as per research topic, estimation approach, study context and data set. The paper results combined with other knowledge provides support for recommendations in future software quality model research, to increase the area of search for relevant studies, carefully select the papers within a set of journals, and conduct more studies on methods used by software industry and researchers.

Diverse types of software are used in almost all sectors of businesses in the modern world. They provide mechanisms that enable buyers and sellers to interact virtually, reduce manual work in businesses and institutions as well as make work a lot easier. Increased demand for software has led to the increased investment that has subsequently attracted numerous security attacks. Millions of resources are held in various software worldwide, cyber-attack criminals have made a career in breaching software security for selfish gains, thus necessitating the development and  establishment of secure software. Through a literature review, the work introduces concepts and terms used in secure software development, presents the best practices and provides a review of the models that could be used. Confidentiality, integrity, availability, and non-repudiation are secure software terms that mean it should be secret, safe, and accessible and keeps a record of every activity undertaken.

In software development life cycle, software maintenance is among the critical phases. It is a postimplementation activity that requires rigorous human efforts. For any software developer, maintaining software for a longer period is the primary objective. This objective can be accomplished if good quality software is developed. Maintainability is one of the vital characteristics of software maintenance. Maintainability enables developers to keep the system alive for a longer period of time at a limited cost. Software Maintainability can be enhanced using reengineering. The proposed research validates improvement in the quality of the reengineered software system. The quality of the software is analyzed using a coupling, cohesion, inheritance, and other essential design metrics. The observed improvement in the software design is 62.1%. The execution time of the software is also reduced by 6.5%. Reduction in the cost of maintenance is also another important outcome of this research. The observed reduction in the maintenance cost is 36.8%. Thus, the main objective of the proposed research is to analyze and validate the quality improvement in the reengineered software. Agile Scrum methodology has been used to perform software reengineering. Design Metrics are measured using the Chidamber and Kemerer Java metric (CKJM) version-9.0 tool. For reengineering implementation, Net Beans 7.3 has been used.
Keywords: Software quality, Software metric, Software Engineering, Reengineering, Software maintainability

— To estimation testability of an object oriented software Modifiability represents itself as a highly accepted factor especially at an early stage of development. Testability of Software is an association of quality attributes that can bear the effort needed for validating the modified software. To develop and produce quality products under the specified time and budget, in it modifiability plays a essential role. Earlier researches has created many approaches to deal and address the testability of design and code when executed on basic structural testing; yet to date, no work has considered methodologies for assessing and predicting testability of early requirements to help testing. This paper, addresses the requirement testability from the point of view of requirement modifiability and quality using a statistical approach, and focuses on the need and importance of modifiability at an early requirement phase and the statistical inference establishes modifiability as an influencing factor for software testability. In this paper an endeavour has been made to establish a hierarchal correlation between object oriented characteristics and testability factors. Later on a model has been proposed for Requirement Modifiability Quantification Model of Object Oriented Software-RMM OOS by set up a multiple linear regressions. Finally the proposed model has been validated experimentally.

Measurements are fundamental any engineering discipline. They indicate the amount, extent, dimension or capacity of an attribute or a product, in a quantitative manner. The analyzed results of the measured data can be given as the basic idea of metrics. It is a quantitative representation of the measurements of the degree to which a system, component, or process possesses a given attribute. When it comes to software, the metrics are a wide scope of measurements of computer programming. The size oriented metrics takes a main role in it since they can be used as the key for better estimations, to improve trust and confidence, and to have a better control over the software products. Software professionals traditionally have been measuring the size of software applications by using several methods. In this paper the researchers discuss about the software size metrics for identifying software size and it is mainly focused on the software development projects in today’s Information Technology (IT) industry.

Modern software development sees code review as a crucial part of the process, because not only does it facilitate the sharing of knowledge about the system at hand, but it may also lead to the early detection of defects, ultimately improving the quality of the produced software. Although supported by numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of shortcomings in the state of the art.

We present a critical analysis of the state of the art of code review tools and techniques, extracting a set of desired features that code review tools should possess. We then present our vision and initial implementation of a novel code review approach named Visual Design Inspection (ViDI), illustrated through a set of usage scenarios. ViDI is based on a combination of visualization techniques, design heuristics, and static code analysis techniques.

The purpose of this research paper is to investigate and demonstrate the success and failure of the Y2K testing efforts. The different strategies implemented in order  to minimize the impact of the Y2K bug on the government, federal, embedded systems, business and all of the business that run on computerized calculation especially those involving of date.

Maintaining the quality of the software is the major challenge in the process of software development. Software inspections which use the methods like structured walkthroughs and formal code reviews involve careful examination of each and every aspect/stage of software development. In Agile software development, refactoring helps to improve software quality. This refactoring is a technique to improve software internal structure without changing its behaviour. After much study regarding the ways to improve software quality, our research proposes an object oriented software metric tool called " MetricAnalyzer ". This tool is tested on different codebases and is proven to be much useful.

Search for improvement opportunities in the software acquisition process, especially in public procurement process in governmental organizations, can lead to the Functional Size Measurement (FSM) methods. A review of the FSM methods and the relevant research findings considering their application, with focus on the most recent ones, is presented in this paper. The findings are analyzed in the context of the software acquisition process and modern software development in order to identify the relevant pros and cons. On this basis, the general guidelines considering the potential software acquisition improvement are provided. The paper can be helpful not only to acquirers, but also to suppliers facing the request to reconsider some of the FSM approaches.

Restoran merupakan salah satu jenis usaha yang mementingkan kualitas pelayanannya. Namun dalam kegiatan operasionalnya, masalah keterlambatan pelayanan sering muncul karena kurangnya koordinasi yang baik antar bagian. Salah satu faktornya adalah jarak antara dapur dan ruang makan. Sistem pengelolaan restoran terintegrasi dapat dibangun untuk mengurangi masalah tersebut. Namun pada penggunaannya, sistem harus memiliki kualitas yang baik agar dapat mendukung jalannya kegiatan operasional restoran. Sebab kualitas yang buruk pada sistem dapat berpotensi mengakibatkan error sehingga pihak yang menggunakannya dapat mengalami kerugian finansial. Penelitian ini membahas tentang pembangunan sistem pengelolaan restoran terintegrasi yang memenuhi standar karakteristik utama model kualitas ISO 9126. ISO 9126 memiliki enam karakteristik utama yaitu functionality, reliability, usability, efficiency, maintainability, dan portability. Functionality diuji dengan menggunakan pengujian validasi terhadap seluruh kebutuhan fungsional, reliability diuji dengan menggunakan tool WAPT (Web Application Performance Tools) yang fokus pada ketersediaan server dengan sessions, pages, dan hits sebagai parameternya, usability diuji dengan menggunakan model kuesioner SUS (System Usability Scale) yang disebar kepada lima belas responden, efficiency juga diuji dengan menggunakan tool WAPT namun fokus pada waktu respon server, maintainability diuji dengan menggunakan persamaan MI (Maintainability Index), dan portability diuji dengan menggunakan tool BrowseEmAll yang fokus pada kemampuan sistem untuk dapat dioperasikan di web browser yang berbeda. Berdasarkan hasil pengujian, sistem telah memenuhi standar karakteristik utama ISO 9126 yaitu dengan functionality sebesar 1, reliability sebesar 100%, usability sebesar 68,5, efficiency sebesar 0,78 detik, maintainability sebesar 66,62597, dan hasil portability menunjukkan tidak ditemukannya error maupun warning di tujuh jenis desktop browser dan lima jenis mobile browser. Selain itu, hasil pengujian integrasi menunjukkan bahwa seluruh proses yang melibatkan interaksi antar kelas telah terintegrasi dengan baik.

The Dynamic Scalability of resources, a problem in Infrastructure as a Service (IaaS) has been the hotspot for research and industry communities. The heterogeneous and dynamic nature of the Cloud workloads depends on the Quality of Service (QoS) allocation of appropriate workloads to appropriate resources. A workload is an abstraction of work that instance or set of instances that are going to perform. Running a web service or being a Hadoop data node is valid workloads. The efficient management of dynamic nature resources can be done with the help of workloads. Until workload is considered a fundamental capability, the Cloud resources cannot be utilized in an efficient manner. In this paper, different workloads have been identified and categorized along with their characteristics and constraints. The metrics based on Quality of Service (QoS) requirements have been identified for each workload and have been analyzed for creating better application design.

Understandability has significant role in development of quality software; it incredibly impacts cost, quality and unwavering quality at the time software development (especially at early stages of development). Wrong interpretation prompts ambiguities, misconception and thus the misinterpretations of further development process and the related records, which frequently results to defective development. Notwithstanding the way that understandability is essential and very critical viewpoint for software development process. Understandability is considered as basic building block for delivering high quality and reliable software. It greatly influences cost, quality and reliability at the time of software evolution. In this paper, author highlights the importance of understandability early at requirement phase in general and as a factor of software testability. The paper quickly portrays the proposed model for understandability quantification of object oriented software [RUM OOS ] by establishing multiple linear regressions. Finally the proposed model has been validated using experimental tryout.

Functional testing is a quality assurance process that could be automated. Functions are tested by feeding them input and examining the output expecting concrete results. However, the performance measurement and execution times of these tests are rarely considered when executing functional tests. Adding simple timestamps for every functional test execution when such a test is started or stopped could bring a valuable benchmarking data for analysis, save a significant amount of time for executing performance tests separately from functional tests, and increase defect removal efficiency.

Class cohesion is considered as one of most important object-oriented software attributes.  It is defined as the degree of the relatedness of the members in a class. Based on instance variables usage criteria the major existing class cohesion metrics are measured. It is only a special and a restricted way of capturing class cohesion. We believe, as stated in many papers, that class cohesion should not exclusively be based on common instance variables usage criteria. We introduce, in this paper, a new criterion, which focuses on interactions between class methods and class instances . We developed a cohesion measurement tool for Java programs and performed a case study on several systems. This paper provides an account of new measures of cohesion developed to assess the reusability of Java classes. The obtained results demonstrate that our new class cohesion metric, based on the proposed cohesion criteria, captures several pairs of related methods, which are not captured by the existing cohesion metrics

Abstract—Modern software development sees code review as a crucial part of the process, because not only does it facilitate the sharing of knowledge about the system at hand, but it may also lead to the early detection of defects, ultimately improving the quality of the produced software. Although supported by numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of shortcomings in the state of the art. We present a critical analysis of the state of the art of code review tools and techniques, extracting a set of desired features that code review tools should possess. We then present our vision and initial implementation of a novel code review approach named Visual Design Inspection (ViDI), illustrated through a set of usage scenarios. ViDI is based on a combination of visualization techniques, design heuristics, and static code analysis techniques. I.

Modern day computing constitutes software elements that are very expensive. Hence it is very essential to handle these elements with care. These elements are so fragile that a slight variation in rating analysis may lead to high degree of unexpected losses. The above stated scenario holds good for object – oriented systems. Many estimation techniques have been proposed for traditional systems. The technique that first incorporated the characteristics of the OO systems in its model was COCOMO model developed by Dr. Barry Boehm in 1981. Its variation namely the Post-Architectural model has 17 cost drivers to rate the system inclusive of an eminent characteristic of OO systems such as " Reusability ". Boehm has proposed a set of equations that estimate cost as a factor of SLOC and effort. This paper proposes an empirical model that estimates cost as a factor of Effort Adjustment Factors(EAF). Post-Architectural model of COCOMO II being the baseline of this study, suggests that cost can also be computed from EAF that exhibit distinctly the characteristics of OO systems namely Reusability, Understandability, Maintainability etc. Studies have been carried out on several JAVA projects by collecting metrics through a new object-oriented metric tool called " JAVA CODE ANALYZER''. The rating of the cost drivers is strictly based on the metrics. An incremental analysis of projects led to a constant which is an average of the " Cost/EAF " factor. The findings of this study proposes a derived constant, " Cost/EAF ''which could be used to estimate the cost of the future OO systems at an early phase by obtaining the EAF of the system to be developed. Since this kind of estimation is not purely based on SLOC or effort and on the contrary it is computed through EAF of the system to be developed it would be a closer approximation of the actual cost after its development.

Technical debt (TD) is a metaphor of bad software
design or immature artifacts of a software system. The metaphor has been quite intensively researched especially on how to identify the TD symptoms, (e.g., system deficiencies or architecture violations) explicitly. Although the TD identification is quite important in the TD management process, a systematic management of TD and how to reduce it should also be considered important in each release of the development project. Otherwise, the software becomes more and more unmaintainable. In this paper, we introduce a framework to manage and reduce the TD of software systems. As it is based on quantification and a cost-benefit analysis, it is called Cost-Benefit based Technical Debt Management (CoBeTDM). CoBeTDM defines explicit phases focusing on the most important aspects of TD management: identification, monitoring, and prioritization. Overall, CoBeTDM should support managers to take the right decisions regarding the software evolution and the reduction of the collected TD at the right time.

We present ViDI (Visual Design Inspector), a novel code review tool which focuses on quality concerns and design inspection as its cornerstones. It leverages visualization techniques to represent the reviewed software and augments the visualization with the results of quality analysis tools. To effectively understand the contribution of a reviewer in terms of the impact of her changes on the overall system quality, ViDI supports the recording and further inspection of reviewing sessions. ViDI is an advanced prototype which we will soon release to the Pharo open-source community.
Video URL: http://youtu.be/EtdkcNBJAec

The validation of software quality metrics lacks statistical significance. One reason for this is that the data collection requires quite some effort. To help solve this problem, we develop tools for metrics analysis of a large number of software projects (146 projects with ca. 70.000 classes and interfaces and over 11 million lines of code). Moreover, validation of software quality metrics should focus on relevant metrics, i.e., correlated metrics need not to be validated independently. Based on our statistical basis, we identify correlation between several metrics from well-known objectoriented metrics suites. Besides, we present early results of typical metrics values and possible thresholds. 1.

To assess quality of the denoised image is one of the important task in image denoising application. Numerous quality metrics are proposed by researchers with their particular characteristics till today. In practice, image acquisition system is different for natural and medical images. Hence noise introduced in these images is also different in nature. Considering this fact, authors in this paper tried to identify the suited quality metrics for Gaussian, speckle and Poisson corrupted natural, ultrasound and X-ray images respectively. In this paper, sixteen different quality metrics from full reference category are evaluated with respect to noise variance and suited quality metric for particular type of noise is identified. Strong need to develop noise dependent quality metric is also identified in this work.

Web Services technology has the potential to cater an enterprise's needs, providing the ability to integrate different systems and application types regardless of their platform, operating system, programming language, or location. Web Services could be deployed in traditional, centralized or brokered client server approach or they could be in peer to peer manner. Web Services could act as a server providing functionality to a requester or act as a client, receiving functionality from any service. From the performance perspective the availability of Web Services plays an important role among many parameters.

To build large scale software systems, Component Based Software Engineering (CBSE) has played a vital role. The current practices of software industry demands more development of a software within time and budget which is highly productive to them. It became so necessary to achieve how effectively the software component is reusable. In order to meet this, the component level reuse, in terms of both class and method level can be possibly done. The traditional approaches are presented in the literature upto the level of extent of achievement of reuse. Any how still effective reuse is a challenging issue as a part. In this paper, a methodology has proposed for the identification of reuse level which has been considered by the using reuse metrics such as the Class Template Factor(CTF) and Method Template Factor(MTF). By considering these measures makes easy to identify the level of reuse so that helps in the growth the productivity in the organization.