Research papers on software quality metrics

Software Project Quality Management. Quality Management is very important in Software Projects. Paper discusses about Life Cycle approach to Software Quality Management process and its principles, activities, factors, methods, benefits, and also Principles of Quality Risk Management. Using ethnography and discourse analysis to study software engineering practices. At that time, various quality initiatives existed including At that time, various quality initiatives existed including standards, codes of best However, this establishment considers an organization, which have been working in a Quality Management structure within the concepts of TQM - Total Quality Management environments.

The paper also presents the relation with activities of SQM and Organizational Quality Management, with advantages and contribution of each other in the Continuous Improvement Process. The 1 st Workshop on Quality in Modeling. Kuzniarz bt. Kuzniarz bth. Staron ituniv. A measurement based software quality framework. Course Quality Professional. The Courseware has four basic This allows that particular needs and learning objectives can be met at European level according the harmonised scheme.

What has culture to do with SPI? Cultural factors, which may have a bearing on successful adoption and implementation of Software Quality Management Systems, were identified during a Cultural factors, which may have a bearing on successful adoption and implementation of Software Quality Management Systems, were identified during a field - study i n five countries. A self - assessment model, called CODES, has been developed for use by organisations developing software in different parts of.

This paper describes our attempts to look at how different cultures influence Software Quality Management Siakas ; Mohamed Walaa-Eldeen and Siakas Quality of the software product cannot be determined until late in the Quality of the software product cannot be determined until late in the development cycle. It is widely accepted that reliance has to be placed on process quality as a means of achieving product quality.

In recent years software. Learning in a changing society and the importance of cultural awareness. Empirical measurement of the effects of cultural diversity on software quality management. Towards management of software as assets: A literature review with additional sources. How should and how can software be managed? What is the management concept or paradigm? Software professionals, if they think about management of software at all, think in terms of Configuration Management.

This is not a method for This is much too fine a level of granularity. Management begins with accurate and timely information. Managers tend to view software as something unfortunately very necessary but troubling because, they have very little real information about it and control is still nebulous, at best.

Accountants view software as an incomprehensible intangible, neither wholly an expense nor really an asset. They do not have, nor do they produce information concerning it. Their data concerning software barely touches on direct outlays and contains no element of effort. This article shows a direction how such clarity may be achieved. Related Topics. Software Quality Metrics. Follow Following. Many fault prediction models have been developed using several internal attributes and different machine learning techniques.

However, the open-source community still lacks a concise knowledge about what types of internal attributes affect the software quality the most. In this work, an empirical investigation is conducted to explore the relationships between internal attributes of open-source systems and their fault-proneness.

The results of the empirical analysis showed that by selecting only nine internal attributes, the fault prediction models accuracy did not decrease significantly. This indicates that only a subset of these internal attributes is worth collection and investigation. By focusing on a small set of internal attributes, the quality assurance team can save time and resour This work presents an investigation of three different industrial projects of software development by a Brazilian enterprise.

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. This paper now presents preliminary, but encouraging results from a This paper now presents preliminary, but encouraging results from a subsequent study that shows six different ways in which CommJ can improve the reusability and maintainability of applications requiring network communications.

We begin by defining a reuse and maintenance quality model as an extension to an existing quality model. We then identify six hypotheses that can be measured using metrics from the quality model.

Finally, to test the hypotheses, we compare implementations of different sample applications across two study groups: one for CommJ and another for AspectJ. Results from the study show improvement. Software quality metrics and their impact on embedded software. Software quality prediction models compared. A framework for software quality measurement.

Experience report: Evaluating the effectiveness of decision trees for detecting code smells. 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 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.

Availability metrics: under controlled environments for web services. Case study: a maintenance practice used with real-time telecommunications software. Essential Activities for Secure Software Development. 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 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.

A survey of software quality metrics for software measurement process. 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.