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

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


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.

Full-text preview

Available from:
  • Source
    • "For the purpose of this study, the NFR defined as how the system should perform the tasks. Even though that the NFR are often underestimated or ignored [22] there is a common consensus that NFR are essential and can be critical for the success of a system project [6], [10], [19], [23]-[25]. Furthermore, to achieve a high quality software system, both FR and NFR should be addressed [12], [26]. Therefore, in this study both types of requirements have been taken into confederation. "

    Full-text · Article · May 2016
  • 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.
    Full-text · Article · Sep 2014
  • 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.
    Full-text · Conference Paper · May 2014
Show more