Challenges to Development of Standard Software Quality Model

Abstract

To stay ahead in competition, software organizations have to deliver required functionality consistently guaranteed with high quality. The quality expectations of customers at purchase time from the software is the major reason of emergent attention of software organizations to implement quality management in software development. Nowadays, use of Component Based Software Development (CBSD) approach is considered success factor for business because of its underlying benefits like reusability, on-time delivery, high quality, and less cost. But success of CBSD depends upon the quality of components used. Many quality models have been proposed to provide high quality products, some of these are for general usage and others are for specific applications or domains. These specific purpose models are improved or modified forms of basic quality models especially ISO 9126. This paper presents key challenges or deterrents to the development of standard, complete and pervasive software quality models, solution to these challenges and their importance is also discussed.

A Review of Software Quality Models for the Evaluation of Software Products

“…Figure 1 updates the work of Thapar [6] and shows the evolution of quality models from the Mc Call first model in 1977 until 2013. This evolution has categorized the models in: the Basic Models (1977 -2001) whose objective is the total and comprehensive product evaluation [6] and the Tailored Quality Models (from 2001 onwards) oriented to evaluations of components. In this work models oriented to evaluation of Free Software are also considered because of their actual importance.…”

A Comparison of Software Quality Characteristics and Software Sustainability Characteristics

“…As a result, there is no agreement about how many exist. According to [15] the quality of software could be best described through NFRs. This necessitates a way to identify the most important software characteristics for a piece of software.…”

“…Software process quality is described as software engineering-related components such as technology, people, tools and organisation, whereas software product quality comprises many aspects, such as the clarity of documentation and integrity, design traceability, application reliability and test integrity as its basic characteristics. [15] and [21] categorise quality models into two types, namely basic and tailored (2002-2011) models. The purpose of basic models is to define quality in a new way that covers various aspects of software quality, taking into consideration different points of view regarding the evaluation of software products [15].…”

“…[15] and [21] categorise quality models into two types, namely basic and tailored (2002-2011) models. The purpose of basic models is to define quality in a new way that covers various aspects of software quality, taking into consideration different points of view regarding the evaluation of software products [15]. Both [21] and [15] argue that basic quality models are hierarchical in structure.…”

“…The purpose of basic models is to define quality in a new way that covers various aspects of software quality, taking into consideration different points of view regarding the evaluation of software products [15]. Both [21] and [15] argue that basic quality models are hierarchical in structure. The former argues that the basic models are McCall, Boehm, FURPS, Dromey and ISO 9126.…”