DOCSLIB.ORG

Measuring Software Product Quality: a Survey of ISO/IEC 9126

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Measuring Software Product Quality: a Survey of ISO/IEC 9126 featurequality Measuring Software Product Quality: A Survey of ISO/IEC 9126 Ho-Won Jung and Seung-Gweon Kim, Korea University Chang-Shin Chung, Telecommunications Technology Association apid IT growth and the proliferation of PCs have resulted in nu- merous software products. For 2003, the Gartner Group esti- mates that worldwide user spending on software exceeded $730 billion, and IDC estimates that spending in the packaged soft- R 1,2 ware market topped $176 billion. Although the market is rapidly grow- ing, users are often dissatisfied with software quality. In fact, widespread dissatisfaction in the US drove recent legislative activity governing software quality and suppliers’ responsibilities.3 Simi- standards specify software product quality’s larly, user satisfaction is often considered a characteristics and subcharacteristics and their critical outcome of quality management, and metrics. However, some in the software engi- studies show it as having a positive impact on neering community have expressed concerns organizational cost, profit, and sales growth.4 about a lack of evidence to support such stan- To address the issues of software product dards. According to Shari Lawrence Pfleeger quality, the Joint Technical Committee 1 of the and her colleagues, “Standards have codified International Organization for Standardiza- approaches whose effectiveness has not been tion and International Electrotechnical Com- rigorously and scientifically demonstrated. mission published a set of software product Rather, we have too often relied on anecdote, quality standards known as ISO/IEC 9126. ‘gut feeling,’ the opinions of experts, or even (See the sidebar for related standards.) These flawed research rather than on careful, rigor- ous software engineering experimentation.”5 Stakeholders use evaluations of software The international standard ISO/IEC 9126 defines a quality model product quality as a basis for many important for software products. Based on a user survey, this study of the decisions, including improving product qual- ity, making large-scale acquisitions, and mon- standard helps clarify quality attributes and provides guidance for itoring contracts. Given this crucial business revising the standard. role and the community’s doubts about stan- 88 IEEE SOFTWARE Published by the IEEE Computer Society 0740-7459/04/$20.00 © 2004 IEEE dards, we found it essential to empirically in- Related Standards vestigate whether the ISO/IEC 9126 catego- rization is correct and reliable in evaluating Working Group 6 of Subcommittee 7 (Software and Systems Engineering user satisfaction with the judgment of a pack- Standardization) under Joint Technical Committee 1 of the International Or- aged software product’s quality. ganization for Standardization and the International Electrotechnical Com- mission is developing standards and technical reports for software product ISO/IEC 9126 evaluation and metrics. WG 6 has developed ISO/IEC 9126-1 (quality Quality, according to ISO 8402, is “the to- model), 9126-2 (external metrics), 9126-3 (internal metrics), and 9126-4 tality of characteristics of an entity that bear (quality in use metrics). WG 6 has also developed the ISO/IEC 14598 se- on its ability to satisfy stated and implied ries of technical reports, which provide guidance for evaluating software needs.” ISO/IEC 9126-1 defines a quality model product quality on the basis of ISO/IEC 9126. that comprises six characteristics and 27 sub- JTC1 publishes six types of documents. Each type follows all or part of characteristics of software product quality (see the following development stages: preliminary, proposal, preparatory, com- Table 1). Because the quality model is generic, mittee, approval, and publication.1 ISO/IEC 9126-1 is the international you can apply it to any software product by standard and 9126-2, -3, and -4 are technical reports. tailoring to a specific purpose. ISO/IEC 9126 also defines one or more Reference metrics to measure each of its subcharacteris- 1. ISO/IEC JTC1 Directives, Procedures for the Technical Work of ISO/IEC JTC1, ISO/IEC tics. For example, the quality level of a software JTC1, ISO, 1999; www.jtc1.org/directives/toc.htm. product’s functionality can be represented by measured values of its five subcharacteristics. Together, those subcharacteristics include the properties that the standard posits to consti- In ISO/IEC 9126, “satisfaction” implies “the tute functionality. Following an appropriate capability of the software product to satisfy aggregation method, you can combine the five users in a specified context of use.” Satisfaction subcharacteristics’ measured (or survey) val- in that sense refers to the user’s response to in- ues into a single value on a composite index of teraction with the product. It includes judg- functionality. ments about product use rather than about However, if any of functionality’s subcharac- properties of the software itself. Of course, in teristics measures doesn’t correlate to functional- addition to ISO/IEC 9126’s definition, user ity, the aggregated value would fail to fully rep- satisfaction also can include facets such as the resent functionality’s quality as ISO/IEC 9126 quality of service, cost, or developer’s reputa- defines it. In such a case, the unrelated sub- tion. However, we limited our survey ques- characteristic should be moved into a more ap- tions’ wording to cover only the subcharacter- propriate characteristic, so that each character- istics as defined by ISO/IEC 9126. istic includes homogeneous subcharacteristics.6 Background and method Table 1 Because you can call each of ISO/IEC 9126’s six characteristics a dimension, or factor,7,8 in Characteristics and subcharacteristics statistical terms, the standard’s structure is a in ISO/IEC 9126 multidimensional concept of software product Characteristic Subcharacteristics quality. (A similar multidimensional concept Functionality Suitability, accuracy, interoperability, security, functionality would be job satisfaction. For example, you can compliance* be more satisfied or less satisfied with various Reliability Maturity,* fault tolerance,* recoverability,* reliability compliance* combinations of your job, supervisor, pay, Usability Understandability, learnability, operability, attractiveness, and/or workplace.) Our study aims to evaluate usability compliance* empirically ISO/IEC 9126’s dimensionality, or Efficiency Time behavior, resource utilization, efficiency compliance* the classification of characteristics, and inter- Maintainability Analyzability, changeability, stability, testability, maintainability nal-consistency reliability. For this purpose, we compliance* conducted a survey in which users evaluated Portability Adaptability, installability, replaceability, coexistence, portability their satisfaction concerning the quality of a compliance* packaged software product according to the criteria of ISO/IEC 9126’s subcharacteristics. *Denotes the omitted subcharacteristics in our survey September/October 2004 IEEE SOFTWARE 89 The survey we revised the questionnaire and then tested it A marketing department identified 200 users using five industry end users again. The sec- Using too few of its company’s packaged software product— ond pretest results led to minor revisions. rating-scale a query and reporting tool for business data- Because many pretest respondents had dif- bases. Of the 200 people we contacted through ficulty relating the ISO/IEC 9126 reliability categories won’t email or telephone, 75 (38 percent) responded subcharacteristics to their experience with the capture the to the questionnaire. The respondents included product, we removed the reliability questions. 48 end users, 25 developers who had modified In addition, most respondents had the same questions’ full the tool to embed it in their applications, and trouble with the compliance subcharacteris- discriminatory two others—all of whom we refer to as users. tics, defined for each characteristic as “the powers. Using We were unable to find any significant differ- software product adheres to standards, con- ences in end-user and developer responses. ventions, or regulations in laws and similar too many might prescriptions relating to each characteristic.” be beyond the Rating scale So, we removed the compliance subcharacter- If you use too few rating-scale categories, the istic for each of the remaining five characteris- respondents’ response won’t capture the questions’ full dis- tics. In the end, our questionnaire covered 18 discriminatory criminatory power. On the other hand, using subcharacteristics of the five characteristics. too many categories might be beyond the re- During the survey, we encouraged feedback powers. spondents’ limited discriminatory powers. A from respondents regarding the question- Monte Carlo study of the number of scale naire’s contents. points’ effects on reliability showed that relia- bility estimates increased as the number of scale Dimensionality’s role points increased from two to five, but the esti- Principal component analysis (PCA) is a mates decreased as more categories were statistical method used to investigate an un- added.9 So, we used a five-category rating scale, derlying concept’s dimensionality.8 Dimen- which ranged from very satisfied to very dissat- sionality is a concept related to the correlation isfied, and included a “Don’t know” option. between each of the measured subcharacteris- Using this scale, we measured the respon- tics and derived dimensions. A dimension con- dents’ judgments
Load more

Recommended publications
  • Software Quality Management
    Software Quality Management 2004-2005 Marco Scotto ([email protected]) Software Quality Management Contents ¾Definitions ¾Quality of the software product ¾Special features of software ¾ Early software quality models •Boehm model • McCall model ¾ Standard ISO 9126 Software Quality Management 2 Definitions ¾ Software: intellectual product consisting of information stored on a storage device (ISO/DIS 9000: 2000) • Software may occur as concepts, transactions, procedures. One example of software is a computer program • Software is "intellectual creation comprising the programs, procedures, rules and any associated documentation pertaining to the operation of a data processing system" •A software product is the "complete set of computer programs, procedures and associated documentation and data designated for delivery to a user" [ISO 9000-3] • Software is independent of the medium on which it is recorded Software Quality Management 3 Quality of the software product ¾The product should, on the highest level… • Ensure the satisfaction of the user needs • Ensure its proper use ¾ Earlier: 1 developer, 1 user • The program should run and produce results similar to those expected ¾ Later: more developers, more users • Need to economical use of the storage devices • Understandability, portability • User-friendliness, learnability ¾ Nowadays: • Efficiency, reliability, no errors, able to restart without using data Software Quality Management 4 Special features of software (1/6) ¾ Why is software ”different”? • Does not really have “physical” existence
    [Show full text]
  • Adaptability Evaluation at Software Architecture Level Pentti Tarvainen*
    The Open Software Engineering Journal, 2008, 2, 1-30 1 Open Access Adaptability Evaluation at Software Architecture Level Pentti Tarvainen* VTT Technical Research Centre of Finland, Kaitoväylä 1, P.O. Box 1100, FIN-90571 Oulu, Finland Abstract: Quality of software is one of the major issues in software intensive systems and it is important to analyze it as early as possible. An increasingly important quality attribute of complex software systems is adaptability. Software archi- tecture for adaptive software systems should be flexible enough to allow components to change their behaviors depending upon the environmental and stakeholders' changes and goals of the system. Evaluating adaptability at software architec- ture level to identify the weaknesses of the architecture and further to improve adaptability of the architecture are very important tasks for software architects today. Our contribution is an Adaptability Evaluation Method (AEM) that defines, before system implementation, how adaptability requirements can be negotiated and mapped to the architecture, how they can be represented in architectural models, and how the architecture can be evaluated and analyzed in order to validate whether or not the requirements are met. AEM fills the gap from requirements engineering to evaluation and provides an approach for adaptability evaluation at the software architecture level. In this paper AEM is described and validated with a real-world wireless environment control system. Furthermore, adaptability aspects, role of quality attributes, and diversity of adaptability definitions at software architecture level are discussed. Keywords: Adaptability, adaptation, adaptive software architecture, software quality, software quality attribute. INTRODUCTION understand the system [6]. Examples of design decisions are the decisions such as “we shall separate user interface from Today, quality of a software system plays an increasingly the rest of the application to make both user interface and important role in the domain of software engineering.
    [Show full text]
  • A Method for Assessing the Reusability of Object-Oriented
    A Method for Assessing the Reusability of Object- Oriented Code Using a Validated Set of Automated Measurements Fatma Dandashi David C. Rine Mitre Corporation George Mason University 7515 Coleshire Dr. 4400 University Drive McLean, VA 22102-7508 Fairfax, Virginia 22030-4444 1.703.883.7914 1.703.993.1530 ext. 3-1546 [email protected] [email protected] ABSTRACT indirect quality attributes, such as adaptability, completeness, maintainability, and understandability have A method for judging the reusability of C++ code not been thoroughly investigated, or rigorously validated. components and for assessing indirect quality attributes To date, some studies of limited scope have been conducted from the direct attributes measured by an automated tool was to show that relationships exist between the two collections demonstrated. The method consisted of two phases. The first of attributes, direct and indirect [28]. phase identified and analytically validated a set of measurements for assessing direct quality attributes based During our research, we identified and analytically validated on measurement theory. An automated tool was used to a set of static, syntactic, directly measurable quality compute actual measures for a repository of C++ classes. A attributes of C++ code components at the class (macro) and taxonomy relating reuse, indirect quality attributes, and method (micro) levels [11]. Our goal was to identify and measurements identified and validated during the first part validate a set of measurements that can be used as effective of this research was defined. The second phase consisted of assessors of indirect quality attributes and predictors of the identifying and validating a set of measurements for overall quality and reusability of C++ code components.
    [Show full text]
  • The Forgotten “-Ilities”
    The Forgotten “-ilities” James D. Willis, Jr. Dr. Steven Dam SPEC Innovations SPEC Innovations 10440 Balls Ford Road 10440 Balls Ford Road Manassas VA 20109 Manassas VA 20109 Topics • What is an “-Ility”? • How might we organize “-Ilities”? • How Should Systems Engineers View “-Ilities”? • Summary Most Common Lists of -ilities RAM-T (Eng) RASR (DBs) RAMS (Safety) Reliability Reliability Reliability Availability Availability Availability Maintainability Scalability Maintainability Testability Recoverability Safety RASUI (SW) FURPS (SW) Reliability Functionality Availability Usability Serviceability Reliability Usability Performance Instability Supportability © 2011 Systems and Proposal 3 Engineering Company. All rights reserved. Are there more –ilities? Accessibility Executability Performability Supportability Accountability Extensibility Portability Suitability Adaptability Evolvability Practibilty Survivability Administrability Fidelity Practicality Tailorability Affordability Flexibility Predictability Testability Agility Functionality Producibility Traceability Availability Integratability Recoverability Trainability Capability Interoperability Reliability Transportability Composability Interpretability Repeatability Trustability Configurability Maintainability Responsibility Understandability Compatibility Manageability Reusability Upgradability Demonstrability Mobility Scalability Usability Deployability Modifiability Serviceability Verifiability Durability Operability Stability Vulnerability © 2011 Systems and Proposal 4 Engineering
    [Show full text]
  • Innovate – Engineer
    Identify,Innovate –Explore, Engineer - ExecuteExecute 1 1 Proposed Unified “ility” Definition Framework Andrew Long October 2012 Identify,Innovate –Explore, Engineer - ExecuteExecute 2 2 Motivation Increased interest in system “ilities” Lack of common understanding among practitioners Definitions Relationships between one ility and another Metrics Objective: Provide a framework to promote shared discussion of system “ilities” Identify,Innovate –Explore, Engineer - ExecuteExecute 3 3 What are system “ilities”? -ility Latin: a suffix; meaning, ability, ability to [do something] In systems engineering “ilities” are desired system properties “ilities” describe the system (non-functional) rather than specific system behaviors (functional) Functional requirements define what a system is supposed to do; e.g. Performance Non-functional requirements define how a system is supposed to be. Identify,Innovate –Explore, Engineer - ExecuteExecute 4 4 Some examples? . Accessibility Extensibility Responsiveness . Accountability Fidelity Reusability . Adaptability Flexibility Robustness . Administrability Installability Safety . Affordability Integrity Scalability . Auditability Interchangeability Sustainability . Availability Interoperability Serviceability . Credibility Learnability (a.k.a. supportability) . Compatibility Maintainability Securability . Configurability Manageability Simplicity . Correctness Mobility Stability . Customizability Modifiability Survivability . Debugability Modularity Sustainability . Degradability
    [Show full text]
  • Adaptability of Buildings: a Critical Review on the Concept Evolution
    applied sciences Review Adaptability of Buildings: A Critical Review on the Concept Evolution Rand Askar 1, Luís Bragança 1,* and Helena Gervásio 2 1 ISISE, Department of Civil Engineering, University of Minho, 4804-533 Guimarães, Portugal; [email protected] 2 ISISE, Department of Civil Engineering, University of Coimbra, 3030-788 Coimbra, Portugal; [email protected] * Correspondence: [email protected] Abstract: Our ever-evolving built environment is continuously facing emerging needs for housing, work, health, and mobility, among others. Yet, buildings are usually designed and set up as finished permanent objects, reflecting the one constant scenario in mind of defined form, function, and performance. Since change is increasingly inevitable in our life, enlarging buildings’ adaptive capacities in response to arising variables and changing conditions over their lifecycle becomes a necessity in seeking global sustainability demands. The concept of building adaptability has been a notable subject in this respect, increasingly stimulating and proposing regenerative alternatives to today’s often obsolete buildings. This paper critically reviews the existing body of knowledge on the concept of adaptability in building research. The main focus is made on the evolution of the concept interpretations and related paradigms, and on the development of its applications and strategies in the light of promoting models and trends. Drawing on the literature as a source of evidence, the paper analyzes and classifies the content of existing studies published in scientific journals and gray literature, focusing on a timeframe from 2015 up-to-date. Moreover, the paper aims to build a constructive discussion to identify potential gaps between the actual state of the art and emerging Citation: Askar, R.; Bragança, L.; needs, which should be addressed by further research.
    [Show full text]
  • Software Quality: Definitions and Strategic Issues Ronan Fitzpatrick Dublin Institute of Technology, [email protected]
    Dublin Institute of Technology ARROW@DIT Reports School of Computing 1996-01-01 Software quality: definitions and strategic issues Ronan Fitzpatrick Dublin Institute of Technology, [email protected] Follow this and additional works at: http://arrow.dit.ie/scschcomrep Part of the Computer and Systems Architecture Commons Recommended Citation Fitzpatrick, Ronan, "Software quality: definitions and strategic issues" (1996). Reports. Paper 1. http://arrow.dit.ie/scschcomrep/1 This Report is brought to you for free and open access by the School of Computing at ARROW@DIT. It has been accepted for inclusion in Reports by an authorized administrator of ARROW@DIT. For more information, please contact [email protected], [email protected]. This work is licensed under a Creative Commons Attribution- Noncommercial-Share Alike 3.0 License Software Quality:Definitions and Strategic Issues Ronan Fitzpatrick MSc Computing Science (ITSM) Advanced Research Module Staffordshire University, School of Computing Report, April 1996 ______________________________________________________________________________________________ 1 Software Quality: Definitions and Strategic Issues Copyright © 1996 Ronan Fitzpatrick All rights reserved. No part of this publication may reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior permission, in writing, from the copyright owner. 2 Abstract This paper contains two sections relating to software quality issues. First, the various definitions of software quality are examined and an alternative suggested. It continues with a review of the quality model as defined by McCall, Richards and Walters in 1977 and mentions the later model of Boëhm published in 1978. Each of McCall's quality factors is reviewed and the extent to which they still apply in the late 1990s is commented on.
    [Show full text]
  • Applying the ISO 9126 Quality Model to Test Specifications
    Applying the ISO 9126 Quality Model to Test Specifications — Exemplified forTTCN-3 Test Specifications Benjamin Zeiss∗‡,Diana Vega∗∗ ‡‡,Ina Schieferdecker‡‡, Helmut Neukirchen‡ ,Jens Grabowski‡ ‡ Software Engineering for Distributed Systems Group, Institute for Informatics, University of G ottingen,¨ Lotzestr.16–18, 37083 G ottingen,¨ Germany. { zeiss,neukirchen,grabowski} @cs.uni-goettingen.de ‡‡ ETS, Technical University Berlin, Franklinstr.28–29, 10587 Berlin, Germany. { vega,ina} @cs.tu-berlin.de Abstract: Quality models are needed to evaluate and set goals for the quality of a software product. The international ISO/IEC standard 9126 defines ageneral quality model for software products. Software is developed in different domains and the usage of the ISO/IEC quality model requires an instantiation for each concrete domain. One special domain is the development and maintenance of test specifications. Test speci- fications for testing, e.g. the Internet Protocol version 6(IPv6) or the Session Initiation Protocol (SIP), reach sizes of more than 40.000 lines of test code. Such large test specifications require strict quality assurance. In this paper,wepresent an adaptation of the ISO/IEC 9126 quality model to test specifications and showits instantiation for test specifications written in the Testing and Test Control Notation (TTCN-3). Exam- ple measurements of the standardised SIP test suite demonstrate the applicability of our approach. 1Introduction Test specifications developed today by industry and standardisation are usually volumi- nous and are, in our experience, often regarded as complex. Such statements are based on subjective opinions about fewquality aspects that stand out, butneither is the term “com- plexity” clearly defined nor is it evident howitrelates to the quality of atest specification.
    [Show full text]
  • Metrics for Software Adaptability
    Metrics for Software Adaptability Nary Subramanian1, Lawrence Chung2 1Applied Technology Division Anritsu Company Richardson, TX, USA [email protected] 2Department of Computer Science University of Texas, Dallas Richardson, TX, USA [email protected] Abstract This paper discusses our initial work in developing metrics for software adaptability. In this paper we have developed several metrics for software adaptability. One of the advantages of the metrics that we have developed is that they are applicable at the architectural level. Since architecture development is the first stage of the design process, the extent to which the architecture is adaptable will determine the adaptability of the final software. Hence the metrics in this paper will help determine the extent to which the final software will be adaptable as well. This paper first defines software adaptability and then defines adaptability indices – the architecture adaptability index (AAI) and the software adaptability index (SAI). The application of these indices is illustrated with examples. Also the validity of these indices for hierarchical architectures, legacy systems and for dynamic adaptation is examined. 1 Introduction Objective measurement of non-functional requirements (NFRs) in any software is one of the most difficult activities. This is because the inherent nature of the NFRs makes their common understanding difficult. The problem is compounded by the fact that the requirements for any software are usually vague about the NFRs that the software should satisfy and how to evaluate the NFRs in the final software. An ideal solution to these problems will be the development and usage of metrics for all NFRs – this will let the software be checked for the NFRs at all stages of its lifecycle and in case of deviation from the requirements corrective action may be taken.
    [Show full text]
  • Building a Robust Web Application Eric Filonowich Regis University
    Regis University ePublications at Regis University All Regis University Theses Summer 2006 Building a Robust Web Application Eric Filonowich Regis University Follow this and additional works at: https://epublications.regis.edu/theses Part of the Computer Sciences Commons Recommended Citation Filonowich, Eric, "Building a Robust Web Application" (2006). All Regis University Theses. 322. https://epublications.regis.edu/theses/322 This Thesis - Open Access is brought to you for free and open access by ePublications at Regis University. It has been accepted for inclusion in All Regis University Theses by an authorized administrator of ePublications at Regis University. For more information, please contact [email protected]. Regis University School for Professional Studies Graduate Programs Final Project/Thesis Disclaimer Use of the materials available in the Regis University Thesis Collection (“Collection”) is limited and restricted to those users who agree to comply with the following terms of use. Regis University reserves the right to deny access to the Collection to any person who violates these terms of use or who seeks to or does alter, avoid or supersede the functional conditions, restrictions and limitations of the Collection. The site may be used only for lawful purposes. The user is solely responsible for knowing and adhering to any and all applicable laws, rules, and regulations relating or pertaining to use of the Collection. All content in this Collection is owned by and subject to the exclusive control of Regis University and the authors of the materials. It is available only for research purposes and may not be used in violation of copyright laws or for unlawful purposes.
    [Show full text]
  • Computing Curricula 2020 (CC2020)
    A Computing Curricula Series Report 2020 December 31 Computing Curricula 2020 CC2020 Paradigms for Global Computing Education encompassing undergraduate programs in Computer Engineering Computer Science Cybersecurity Information Systems Information Technology Software Engineering with data science A Computing Curricula Series Report Computing Curricula 2020 CC2020 Paradigms for Global Computing Education encompassing undergraduate programs in Computer Engineering Computer Science Cybersecurity Information Systems Information Technology Software Engineering with data science Association for Computing Machinery (ACM) IEEE Computer Society (IEEE-CS) 2020 December 31 Computing Curricula 2020 Computing Curricula Report CC2020 2020 December 31 Copyright © 2021 by ACM and IEEE ALL RIGHTS RESERVED Copyright and Reprint Permissions: Permission granted to use these curriculum guidelines for the development of educational materials and programs. Other use requires specific permission. Permission requests should be addressed to: ACM Permissions Department at [email protected] or to the IEEE Copyrights Manager at [email protected]. ISBN: 978-1-4503-9059-0 DOI: 10.1145/3467967 Web link: https://dl.acm.org/citation.cfm?id=3467967 When available, you may order additional copies from: ACM Order Department, P.O. Box 30777, New York, NY 10087-0777 This report was possible by financial support from: Association for Computing Machinery (ACM) IEEE Computer Society (IEEE-CS) and ACM China ACM India Association for Information Systems (AIS) Education SIG of the Association for Information Systems and Computing Academic Professionals (ED-SIG) Informatics Europe Italian Association of Computer Scientists (GRIN) Special Interest Group on Computer Human Interaction of (SIGCHI) Page 2 of 203 Computing Curricula 2020 Computing Curricula Report CC2020 2020 December 31 The following societies and organizations have officially endorsed this report.
    [Show full text]
  • A Review of Software Quality Models for the Evaluation of Software Products
    International Journal of Software Engineering & Applications (IJSEA), Vol.5, No.6, November 2014 A Review of Software Quality Models for the Evaluation of Software Products José P. Miguel1 , David Mauricio2 and Glen Rodríguez3 1Department of Exact Sciences, Faculty of Sciences, Universidad Peruana Cayetano Heredia, Lima, Peru [email protected] 2Faculty of System Engineering and Computing, National University of San Marcos, Lima,Peru [email protected] 3Faculty of Industrial and System Engineering, National University of Engineering, Lima, Peru [email protected] Abstract Actually, software products are increasing in a fast way and are used in almost all activities of human life. Consequently measuring and evaluating the quality of a software product has become a critical task for many companies. Several models have been proposed to help diverse types of users with quality issues. The development of techniques for building software has influenced the creation of models to assess the quality. Since 2000 the construction of software started to depend on generated or manufactured components and gave rise to new challenges for assessing quality. These components introduce new concepts such as configurability, reusability, availability, better quality and lower cost. Consequently the models are classified in basic models which were developed until 2000, and those based on components called tailored quality models. The purpose of this article is to describe the main models with their strengths and point out some deficiencies. In this work, we conclude that in the present age, aspects of communications play an important factor in the quality of software. Keywords Software Quality, Models, Software quality models, Software components, COTS 1.
    [Show full text]