Académique Documents
Professionnel Documents
Culture Documents
17 de noviembre de 2010
(cc) 2010 Felipe Ortega, Daniel Izquierdo, Pedro Coca. Some rights reserved. This document is distributed under the Creative Commons Attribution-ShareAlike 3.0 licence, available in http://creativecommons.org/licenses/by-sa/3.0/
Index
What is ISO?
ISO: International Organization for Standardization One of the largest organizations in charge of developing and publishing standards There are at least 160 dierent countries http://www.iso.org/iso/home.htm
ISO 9126
Full name: ISO 9126-1 Software engineering Product quality Part 1: Quality model This model is based on six main attributes and 27 sub-attributes
Main attributes
Functionality sub-attributes
Functionality denition: A set of attributes that bear on the existence of a set of functions and their specied properties. The functions are those that satisfy stated or implied needs.
Suitability Accuracy Interoperability Security Functionality compliance
Reliability sub-attributes
Reliability denition: A set of attributes that bear on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
Maturity, Fault tolerance Recoverability Reliability compliance
Usability sub-attributes
Usability denition: A set of attributes that bear on the eort needed for use, and on the individual assessment of such use, by a stated or implied set of users.
Understandability Learnability Operability Attractiveness Usability compliance
Eciency sub-attributes
Eciency denition: A set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used, under stated conditions.
Time behavior Resource utilization Eciency compliance
Maintainability sub-attributes
Maintainability denition: A set of attributes that bear on the eort needed to make specied modications.
Analyzability Changeability Stability Testability Maintainability compliance
Portability sub-attributes
Portability denition: A set of attributes that bear on the ability of software to be transferred from one environment to another.
Adaptability Installability Replaceability Coexistence Portability compliance
Index
Similar to a G-Q-M approach. There are main attributes Then, each of them is divided by some new quality attributes However, quality is too abstract
What we need to obtain an objective approach is to base the study in objective metrics Examples:
Number of people involved in the core team Number of xed bugs Number of new features added in the last six months ... Others ...
Top-Down
Similar to a G-Q-M approach. There are main attributes Then, each of them is divided by some others conforming a tree Finally, and this is the most creative part, it is needed to match branches and leafs
Index
Domain
Quality models are highly dependable of the domain used IDE? ERP? E-mail client?: Requirements are all dierent
It is not mandatory to use all of them in an evaluation of a project As we have seen, there are dierent points of view The ISO standard is generic enough to be partially used In fact, new attributes are added, other are modied and others are removed
Objective Metrics?
Having too many metrics could derive in an unusable quality model. What about an automated quality model? Then we will face problems derived from the empirical software engineering
Objective Metrics?
Are the tools we are using trustable enough? Several dierent data sources (tool for each one?) Dierent programming languages Others...
Index
Objective Metrics?
ISO/IEC. ISO/IEC 9126. Software engineering Product quality. 2001. ISO/IEC. Franch, X. and Carvallo, J. P. Using quality models in software package selection. 2003. Software, IEEE. http://en.wikipedia.org/wiki/ISO/IEC_9126