Measuring software product quality: A survey of ISO/IEC 9126

Dept. of Bus. Adm., Korea Univ., Seoul, South Korea
IEEE Software (Impact Factor: 1.23). 10/2004; 21(5):88 - 92. DOI: 10.1109/MS.2004.1331309
Source: IEEE Xplore

ABSTRACT To address the issues of software product quality, the Joint Technical Committee 1 of the International Organization for Standardization and International Electrotechnical Commission published a set of software product quality standards known as ISO/IEC 9126. These standards specify software product quality's characteristics and subcharacteristics and their metrics. Based on a user survey, this study of the standard helps clarity quality attributes and provides guidance for the resulting standards.

  • Source
    • "Over the years, SE research has had a shift of focus from emphasizing only software functionalities; and has embraced the importance of various software quality attributes in success of software [17], [14], [6]. Researchers highlight that ignoring QRs can lead to developing software that is too costly, difficult to use, or results in the end users dissatisfaction [18]. Therefore, a group of studies in the filed of SE focus on modeling and providing a better understanding of how the end users perceive various aspects of software, and how that affects their satisfaction and software acceptance. "
    [Show abstract] [Hide abstract]
    ABSTRACT: The user's overall experience and perception of functionalities and qualities of a product, User eXperience (UX), is becoming increasingly important for success of software products. Yet, many software companies face challenges with their UX practices, hence fail to achieve a good UX in their products. Part of these challenges are rooted in inadequate knowledge and awareness about UX but also in that UX models are commonly not well integrated with existing software engineering (SE) models and concepts. Therefore, we present two SE-specific models of UX for practitioners: (i) a layered model that shows the relation between functional, quality, and UX requirements, and (ii) a general, UX-aware software process overview model that shows the additional concepts and activities that can help achieve a good UX. Validation of the models in interviews with 12 practitioners and researchers generally found the models useful for practice; for instance to raise knowledge and awareness about UX, improve communications regarding UX and facilitating making UX-aware decisions in the development process. In total, we identified six different areas of use for the models.
  • Source
    • "Beside treating functional requirements, the focus is shifting towards NFRs which are also known as quality requirements and they are considered as quality factors [4]. NFR plays a critical role in software systems [5]. Ineffectively dealing with them can lead a software product to failure [6], [7]. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Dependency among non-functional requirements (NFRs) is one of the major issues to handle for delivering quality software. These dependency relations are the reasons of conflict, though there are also relations where one NFR help to ensure another NFR. Interdependence relations, not treated from the beginning of a software development, may cause requirement dismissal in the later phases of development. To solve those issues, interdependencies among NFRs have been determined. A framework has been proposed to deal with interdependent NFRs from the early stages of development project. The proposed NFR interdependency framework keeps the NFRs with the functional requirements they are associated with which helps to design the system without leaving the NFRs for later stages of development. A case study is done with the proposed framework. Dealing the interdependence relation among NFRs using the framework reduces the chance of conflict and help to design the software with better management of NFRs. I. INTRODUCTION Requirement engineering is a very important phase of a software development. It is becoming the key to success for a software system as complexity of industry and consumer software is increasing [1], [2]. While functional requirements define what the system will do, NFRs state how the system will do. For example, a system's performance, security, reliability, scalability, fault-tolerance, etc [3] are known as NFRs. Beside treating functional requirements, the focus is shifting towards NFRs which are also known as quality requirements and they are considered as quality factors [4]. NFR plays a critical role in software systems [5]. Ineffec-tively dealing with them can lead a software product to failure [6], [7]. NFRs should be dealt from the very first phase of a software development [3], [8], [9]. NFRs are very expensive and difficult to deal with [9], [10], [11]. The nature of NFRs to conflict, contradict and interfere with themselves made them more complex [12]. Interdependency is the reason behind this nature of NFRs. Thus, understanding interdependency among NFRs is very important [2]. Interdependency causes conflict as well as cooperation among NFRs. Because of interdependency, implementing a NFR can hurt to achieve another NFRs [3], [13]. It is not always the case where interdependency raises conflict, in-terdependency between two NFRs can help each other too. Earlier, the NFR Framework used softgoal interdependency graph (SIG) [3], [14] to show interdependencies among NFRs. SIG is limited to two types of interdependencies, but research shows that they can be of seven types [2].
    3rd IEEE Intl. Conf. on Informatics, Electronics & Vision (ICIEV), Dhaka, Bangladesh; 05/2014
  • Source
    • "This approach defines quality according to usability, considering the users' point-of-view (e.g. Jung et al., 2004; Obeso, 2004). Technical quality has received more attention from researchers than the other two dimensions, and several methodologies have been proposed for its evaluation. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Purpose – This paper aims to propose a high-level structure for a global quality evaluation of a website. This structure is based on the characteristics, sub-characteristics and attributes of three main dimensions (content, service, and technical quality) that will substantiate the development of broad website quality evaluation, comparison and improvement methodologies, according to particular sectors of activity and evaluator’s perspective. Design/methodology/approach – Based on the literature and the author’s experience a framework is proposed for a global quality evaluation of a website. Findings – Considering the results of some studies, as well as the systematisation of the knowledge available in several bibliographies, website quality can be grouped into three main dimensions: content quality, service quality, and technical quality. There has not yet been an evaluation methodology that focuses on these three main website quality dimensions in a broad and transversal sense. Originality/value – The paper presents an innovative high-level structure for a global quality evaluation of a website, based on three dimensions not previously considered together.
    Online Information Review 03/2012; 36(3). DOI:10.1108/14684521211241404 · 1.44 Impact Factor
Show more

Preview (2 Sources)

Available from