introduction to the iso 9126

IntroductionApproach using a Quality Model

LimitationsReferences

Introduction to ISO 9126Master on Free Software

Felipe Ortega, Daniel Izquierdo, Pedro Coca

[email protected]/Libresoft

17 de noviembre de 2010

Felipe Ortega, Daniel Izquierdo, Pedro Coca Introduction to ISO 9126



(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 inhttp://creativecommons.org/licenses/by-sa/3.0/




Index

1 Introduction

2 Approach using a Quality Model

3 Limitations

4 References




What is ISO?

ISO: International Organization for Standardization

One of the largest organizations in charge of developing andpublishing standards

There are at least 160 different countries

http://www.iso.org/iso/home.htm


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

Reliability

Usability

Efficiency

Maintainability

Portability




Functionality sub-attributes

Functionality definition: A set of attributes that bear on theexistence of a set of functions and their specified properties.The functions are those that satisfy stated or implied needs.

SuitabilityAccuracyInteroperabilitySecurityFunctionality compliance




Reliability sub-attributes

Reliability definition: A set of attributes that bear on thecapability of software to maintain its level of performanceunder stated conditions for a stated period of time.

Maturity,Fault toleranceRecoverabilityReliability compliance




Usability sub-attributes

Usability definition: A set of attributes that bear on the effortneeded for use, and on the individual assessment of such use,by a stated or implied set of users.

UnderstandabilityLearnabilityOperabilityAttractivenessUsability compliance




Efficiency sub-attributes

Efficiency definition: A set of attributes that bear on therelationship between the level of performance of the softwareand the amount of resources used, under stated conditions.

Time behaviorResource utilizationEfficiency compliance




Maintainability sub-attributes

Maintainability definition: A set of attributes that bear on theeffort needed to make specified modifications.

AnalyzabilityChangeabilityStabilityTestabilityMaintainability compliance




Portability sub-attributes

Portability definition: A set of attributes that bear on theability of software to be transferred from one environment toanother.

AdaptabilityInstallabilityReplaceabilityCoexistencePortability compliance




Index

1 Introduction


3 Limitations

4 References




Using a Quality Model

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




Using a Quality Model: Metrics

What we need to obtain an objective approach is to base thestudy in objective metrics

Examples:

Number of people involved in the core teamNumber of fixed bugsNumber 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 atree

Finally, and this is the most creative part, it is needed tomatch branches and leafs




How to get metrics?

This is part of the automation of this quality models

To be continued




Index

1 Introduction


3 Limitations

4 References




Domain

Quality models are highly dependable of the domain used

IDE? ERP? E-mail client?: Requirements are all different




Too abstract Quality Attributes

It is not mandatory to use all of them in an evaluation of aproject

As we have seen, there are different points of view

The ISO standard is generic enough to be partially used

In fact, new attributes are added, other are modified andothers are removed




Objective Metrics?

Having too many metrics could derive in an unusable qualitymodel.

What about an automated quality model?

Then we will face problems derived from the empiricalsoftware engineering




Objective Metrics?

Are the tools we are using trustable enough?

Several different data sources (tool for each one?)

Different programming languages

Others...




Index

1 Introduction


3 Limitations

4 References




Objective Metrics?

ISO/IEC. ISO/IEC 9126. Software engineering – Productquality. 2001. ISO/IEC.

Franch, X. and Carvallo, J. P. Using quality models insoftware package selection. 2003. Software, IEEE.

http://en.wikipedia.org/wiki/ISO/IEC_9126


http://en.wikipedia.org/wiki/ISO/IEC_9126

introduction to the iso 9126

Documents