Assessing the Quality of your Software with MoQam

The computing technologies and IT platforms are in exponential continuous growth. This growth generated several problems; hence, the necessity of following an approach of software quality for needs and requirements, avoiding the problems engendered in the conception, and the development and the use of the software. In the last years, several approaches of software quality were proposed (IEEE, PDCA, CMMI,…), these approach differ from their vision to quality, the level of intervention in the life cycle of software and the nature of activities are required to be ensured and control software quality. So, the things that they are common between them are: its processes are completely repeated for each software without exploiting the cumulative experiments during the cycles of previous projects. For this one, which is based on the architecture driven model (MDA).We propose in this article, a process based on software quality models, named SQUAM (software quality model based ). Moreover, we propose the framework QMGenerator that a model generator of software quality dedicates to our process SQUAM.

Lecture Notes in Computer Science, 2001

Quality Function Deployment (QFD) technique has been developed in the context of Total Quality Management, and it has been experimented in the software engineering domain. This paper illustrated how key constructs from QFD contributed to an development of a second version of a Quality Factor (QF) for a qualitative software evaluation, considering three distinctive but connected areas of interest, each of them representing dimension of performance: • economic dimension, the perspective is the managers' viewpoint; • social dimension, the perspective is the users' viewpoint; • technical dimension, the perspective is the developers' viewpoint. This new version of the original QF technique, referred to as QF 2 D (Quality Factor through QFD), has the following features: it can be used for both a priori and a posteriori evaluations of the software product; it makes usage of the set of quality sub-characteristics proposed in the new upcoming ISO/IEC 9126:2000 standard it has a variable number of elements taken into account the three viewpoints for the evaluation; it offers the visual clarity from QFD for external and internal benchmarking. An implementation of this new version of this technique in quality models is also discussed.

2018

Background and Objectives: One of the major challenges in software engineering is how to respond to the desolate state of high-quality software development in a timely and cost-effective manner. Many studies have been conducted in an attempt to formalize the quality of software. However, according to the recent researches, the lack of comprehensive quality model is rooted in neglecting all quality aspects. Methods: In this study, we review nineteen quality models and classify them from three different perspectives, including structural, behavioral, and basic and derived aspects. The main aim is to specify and extract the more comprehensive set of quality factors to evaluate software quality. Results: This paper compares the different quality models and analyzes the factors to draw the necessary aspects in comprehensive quality models. Since the software quality involves several engineering tasks and several players who deal with quality concepts during software life cycle according ...

2009

Our long term research goal is to validate a standard-and metric-based software quality model. Today, ambiguous metric definitions lead to incomparable implementation variants in tools. Therefore, large scale empirical experiments, spanning different independent research groups, evaluating software quality models are not possible, since the generalization of the results of individual software measurements is impossible. We propose a public and extensible knowledge base-a compendium-for the unambiguous definition of software quality metrics and their connection to a standard-based software quality model. This constitutes the basis for the measurement and prediction of software quality in current and legacy systems. This compendium is published as specification for the metrics implementation. In order to provide well-defined metrics an unambiguous description framework for software metrics had to be developed. It includes formal definitions based on an extensible language-independent meta-model and language mapping definitions. We formalize an existing and well-defined meta-model for reverse engineering. Then, we define some software quality metrics based on this meta-model, as well as language mappings for Java and UML/XMI. A full set of metric definitions together with a quality model is provided in the compendium. Since we want our compendium to be a "living document", we need to maintain the provided knowledge base, the meta-models, language mappings, and metrics. Therefore, we design a maintenance process assuring the safe evolution of the common meta-model. This process is based on theorems controlling changes to the common meta-model, as well as abstraction mechanisms in form of views, hiding modifications to the common metamodel from existing metric definitions. We show feasibility by implementing our definition framework and the metrics specified in the compendium in a well known reverse engineering tool, the VizzAnalyzer. We evaluate our efforts in two industrial case studies supporting our claims and solution. We suggest that our description framework eliminates existing ambiguities in software metric definitions, simplifying the implementation of metrics in their original sense, and permitting the definition of standardized metrics. The compendium supports exchanging experiments and the evaluation of metrics. The maintenance process allows us to extend and modify definitions, e.g., add new programming languages, in a controlled and safe way. With the tools developed, it is possible to conduct the experiments we envision, and to evaluate the suitability of software quality metrics, in a next step.

With the objective of presenting qualitative software system most of the software producers have endeavoured and infact this is their main purpose. Software quality is having multi-dimensional content which may be distinguished and measured easily. To be specific, with the idea of determining the multidimensional content in a more exact pattern various qualitative models have been presented by virtue of which different aspects of this matter have been attempted to be investigated properly. Practically as because there are existences of different models which have used different expressions the comprehension of this basic content have become to some extent hard or difficult. Attempts have been made in this particular paper to introduce some models that have been mentioned and more clearly analysis the qualitative characteristics and side-by-side determine the software quality along with the analytical comparison of these models. This paper may serve the purpose of a reference for investigating software quality and its related models.

2016

Overall, the workshop aimed at gathering together researchers and practitioners to discuss experiences in the application of state of the art approaches to measure, assess and evaluate the quality of both software systems as well as software development processes in general and software test processes in particular. As software development organizations are always forced to develop software in the "right" quality, the quality specification and quality assurance are crucial. Although there are lots of approaches to deal with quantitative quality aspects, it is still challenging to choose a suitable set of techniques that best fit to the specific project and organizational constraints.

Journal of Computer Science, 2005

Several object-oriented metrics have been developed and used in conjunction with the quality models to predict the overall quality of software. However, it may not be enough to propose metrics. The fundamental question may be of their validity, utility and reliability. It may be much significant to be sure that these metrics are really useful and for that their construct

CEUR Workshop Proceedings, 2020

2004

Abstract. Software metrics and quality models play a pivotal role in measurement of software quality. A number of well-known quality models and software metrics are used to build quality software both in industry and in academia. However, during our research on measuring software quality using design patterns, we faced many issues related to existing software metrics and quality models. In this position paper, we discuss some of these issues and present our approach to software quality assessment

ICST Transactions on Scalable Information Systems

INTRODUCTION: The emerging industrialization of software promotes the continuous development of new evaluation models that adapt to the product's characteristics and the organizations' needs. OBJECTIVES: This article aims to identify the software quality models proposed between 2016 and 2020. METHODS: We conducted an exploratory systematic review in the SciELO, IEEE Xplore, and Scopus databases, resulting in 14 research papers proposing new models for assessing software quality. RESULTS: 79% of the research papers were extracted from IEEE Xplore, and 50% of them were authored by individuals affiliated with European institutions. We presented various software quality models focused on assessing both product quality and usability for specific purposes. Additionally, we reported that the proposed models are based on common software quality metrics standards such as CMMI, ISO/IEC 9126, and others. CONCLUSION: The review serves to update the state of the art regarding the softwar...