October 7, 2020 By admin 0


ISO/IEC defines quality in use measures for the characteristics defined in ISO/IEC , and is intended to be used together with ISO/IEC ISO/IEC. FDIS. Information technology — Software product quality —. Part 1: Quality model. Technologies de l’information — Qualité. Presenta una reflexión sobre las consideraciones y recomendaciones que se deben tener en cuenta para evaluar los criterios de calidad del Modelo.

Author: Zolorr Grolmaran
Country: Kenya
Language: English (Spanish)
Genre: Health and Food
Published (Last): 3 March 2008
Pages: 472
PDF File Size: 1.67 Mb
ePub File Size: 14.83 Mb
ISBN: 119-9-26440-137-7
Downloads: 39693
Price: Free* [*Free Regsitration Required]
Uploader: Nezahn

This page was last edited on 12 Septemberat Software product is defined in a broad sense: Views Read Edit View history. An attribute is an entity which can be verified or measured in the software product. Each quality sub-characteristic e.

Downloads Download data is not yet available. These biases include changing priorities after the start of a project or not having any clear definitions of “success”. On doing so, however, it leaves up to each organization the task of specifying precisely its own model. As a result, the notion of user extends to operators as well as to programmers, which are users of components such as software libraries. Retrieved from ” https: Quick jump to estandqr content.

ISO/IEC – Software engineering — Product quality — Part 1: Quality model

ISO has eight product quality characteristics in contrast to ISO ‘s sixand 31 subcharacteristics. Quality-in-use metrics are only available when the final product is used in real conditions.

List of International Electrotechnical Commission standards. Proof sent to secretariat or FDIS ballot initiated: The ideas and assertions expressed by the authors are their solely responsibility and do not represent the views and opinions of the Journal or its editors. The measures are applicable to the use of any human-computer system, including both computer systems in use and software products that form part of the system.


Vol 22 No 35 Check out our FAQs. ISO standards by standard number. Ideally, the internal quality determines the external quality and external quality determines quality in use. Attributes are not defined in the standard, as they vary between different software products.

Life cycle A standard is reviewed every 5 years 00 Preliminary. From Wikipedia, the free encyclopedia. Final text received or FDIS registered for formal approval.

Published Jul 5, Licence The journal authorizes the total or partial reproduction of the published article, as long as the source, including the name of the Journal, author syear, volume, issue, and pages are cited.

It does not assign ranges of values of the measures to rated levels or to grades of compliance because these values are defined for each system or product depending, on the context of use and users’ needs. This standard stems from the GE model for describing software quality, presented in by McCall et al. They are not intended to be ixo exhaustive set. Authors must complete, sign, and submit the Review and Publication Authorization Form of the manuscript provided by the Journal; this form should contain all wstandar originality and copyright information of the manuscript.

Compared to”security” and “compatibility” were added as main characteristics.

ISO/IEC 9126

This may be done, for example, by specifying target values for quality metrics which evaluates the degree of presence of quality attributes. Monday to Friday – Use British English Oxford spelling from January Sistema OJS3 – Metabiblioteca. The journal authorizes the total or partial reproduction of the published article, as long as the source, including the name of the Journal, author syear, volume, issue, and pages are cited. By using this site, you agree rstandar the Terms of Use and Privacy Policy.


Aplicación del estándar ISO/IEC 9126-3 en el modelo de datos conceptual entidad-relación

Some attributes could have a desirable range of values, which does not depend on specific user needs but depends on generic factors, for example, human cognitive factors. The Journal allows and invites authors to publish their work in repositories or on their website after the presentation of the number in which the work is published with the aim of generating greater dissemination of the work.

The proposed quality in use measures are primarily intended to be used for quality assurance and management of systems and software products based on their effects when actually used.

The main users of the measurement results are people managing development, acquisition, evaluation, or maintenance of software and estandxr. The standard provides a framework for organizations to define a quality model for a software product.