29 nov 2009 · ISO 9126 - Content ▫ Part 1: Quality model ▫ Product quality and the lifecycle ▫ Quality models for: ▫ Internal Quality, External Quality and
| Previous PDF | Next PDF |
[PDF] Lassurance qualité logicielle enseignée aux futurs ingénieurs - ISO
normes ISO choisies pour ce cours sont : • ISO/CEI 9126, partie 1 à 4 (la qualité) • ISO/ CEI 16085 (gestion des risques) • ISO 9001 (systèmes de management
[PDF] Qualité Informatique - LIM
ISO COBIT ITIL Les Certifications Internationales Entreprise d'informatique ISO 9126 ✓ Ensemble de normes qui définit le modèle de qualité pour un
[PDF] Modèles de mesure de la qualité des logiciels - Inria
Le modèle Quality Model for Object-Oriented Design (QMOOD) est également un modèle hiérarchique basé sur la norme ISO 9126 Il est composé de quatre
[PDF] ISO/IEC 9126 Quality Model for Evaluation of Student - CORE
student academic portal using ISO / IEC 9126 quality modeling approach Quality on the characteristics of the ISO 9126 model with the 10 elayyan ca/33 pdf
[PDF] ISO/IEC 9126 in practice: what do we need to know?
ISO/IEC 9126 is currently one of the most widespread quality standards In its actual form it embraces both quality models and metrics Due to its generic nature ,
[PDF] Chapitre 7c - Cedric-Cnam
ISO/IEC 25030, la qualité du logiciel est la capacité du produit logiciel à satisfaire La norme ISO/IEC 9126-1 et sa mise à jour ISO/IEC 25010 [ISO11], qui fait Software Engineering Institute, 2006 http://www sei cmu edu/reports/06tr023 pdf
[PDF] International Standard ISO/IEC 9126
29 nov 2009 · ISO 9126 - Content ▫ Part 1: Quality model ▫ Product quality and the lifecycle ▫ Quality models for: ▫ Internal Quality, External Quality and
[PDF] ISO/IEC9126–3: Internal Quality Measurement Tables (IQMT) an
Study of ISO 9126-3 prediction capacity (from internal quality to external quality), Phase III From www sei cmu edu/pub/cmm/Misc/standards-map pdf 47
[PDF] ISO/TC - School of Computer Science and Engineering, UNSW
20 mar 2000 · Details of the software products used to create this PDF file can be found in the ISO/IEC 9126 (1991): Software product evaluation - Quality
[PDF] iso budget définition
[PDF] iso dis 9001 2015
[PDF] iso square
[PDF] iso/cei 14598
[PDF] iso/dis 22000
[PDF] iso/iec 25010:2011 pdf
[PDF] iso/tc 176 pdf
[PDF] iso/tc 176/sc 2 pdf
[PDF] iso26000
[PDF] isobarycentre quadrilatere
[PDF] isocout
[PDF] isocout définition
[PDF] isolationnisme
[PDF] isolement des bactéries pdf
1
Software Engineering - Product quality
International Standard
ISO/IEC 9126
2009-11-292
ISO 9126 - Content
Part 1: Quality model
Product quality and the lifecycle
Quality models for:
Internal Quality, External Quality and Quality in UsePart 2: External Metrics
Guide to use metrics tables
External Quality Metrics
Part 3: Internal Metrics
Guide to use metrics tables
Internal Quality Metrics
Part 4: Quality in use metrics
Guide to use metrics tables
Quality in Use Metrics
22009-11-293
Quality Model
Characteristics
Sub characteristics
Metrics
Internal and
External Quality
Characteristics
Metrics
Quality in Use
2009-11-294
Quality model
Characteristics
Subcharacteristics
Metrics
External Quality
Efficiency
Time behavior
The capability of the software product to
provide appropriate response and processing times and throughput rates when performing its function, under stated conditionsName : Response time
But de la métrique:
Combien de temps prend
l'exécution d'une tâche ?Formule:
T = A - B
A = Temps que prend le système à répondre à la tâcheB = Temps que prend l'exécution de la tâche
External Quality
32009-11-295
Internal and External Quality
Internal and
External Quality
Suitability
Accuracy
Interoperability
Security
Compliance
Maturity
Fault tolerance
Recoverability
Compliance
Understandability
Learnability
Operability
Attractiveness
Compliance
Time behavior
Resource utilization
Compliance
Changeability
Stability
Testability
Compliance
Adaptability
Installability
Co-existence
Replaceability
Compliance
2009-11-296
Internal and External Quality
•Internal quality - Is the totality of characteristics of the software product from an internal view. - Internal quality is measured and evaluated against theinternal quality requirements. Details of software product quality can be improved during code implementation, reviewing and testing, but the fundamental nature of the software product quality represented by internal quality remains unchanged unless redesigned
•External Quality - Is the totality of characteristics of the software product from an external view. - It is the quality when the software is executed , which is typically measured and evaluated while testing in a simulated environment with simulated data using external metrics 42009-11-297
Functionality
• The capability of the software product to provide functions which meet stated and implied needswhen the software is used under specified conditions. -Suitability • The capability of the software product to provide an appropriate set of functionsfor specified tasks and user objectives. -Accuracy • The capability of the software product to provide the right or agreed results or effects with the needed degree of precision. -Interoperability • The capability of the software product to interact with one or more specified systems. -Security• The capability of the software product to protect information and dataso that unauthorised persons or systems cannot read or modify them and authorised persons or systems are not denied access to them.
-Functionality compliance • The capability of the software product to adhere to standards, conventions or regulationsin laws and similar prescriptions relating to functionality.2009-11-298
Reliability
• The capability of the software product to maintain a specified level of performancewhen used under specified conditions. -Maturity • The capability of the software product to avoid failure as a result of faultsin the software. -Fault tolerance • The capability of the software product to maintain a specified level of performance in cases of software faults or of infringement of its specified interface. -Recoverability • The capability of the software product to re-establish a specified level of performance and recover the datadirectly affected in the case of a failure. -Reliability compliance • The capability of the software product to adhere to standards conventions or regulations relating to reliability. 52009-11-299
Usability
• The capability of the software product to be understood, learned, usedand attractive to the user, when used under specified conditions. -Understandability • The capability of the software product to enable the user to understand whether the software is suitable,and how it can be used for particular tasks and conditions of use. -Learnability • The capability of the software product to enable the user to learn its application. -Operability • The capability of the software product to enable the user to operate and control it. -Attractiveness • The capability of the software product to be attractive to the user. -Usability compliance • The capability of the software product to adhere to standards, conventions, style guides or regulations relating to usability.2009-11-2910
Efficiency
• The capability of the software product to provide appropriate performance, relative to the amount of resources used, under stated conditions. -Time behaviour • The capability of the software product to provide appropriate response and processing times and throughput rateswhen performing its function, under stated conditions. -Resource utilisation • The capability of the software product to use appropriate amounts and types of resourceswhen the software performs its function under stated conditions. -Efficiency compliance • The capability of the software product to adhere to standards or conventions relating to efficiency. 62009-11-2911
Maintainability
• The capability of the software product to be modified. Modifications may include corrections , improvementsor adaptation of the software to changes in environment, and in requirements and functional specifications. -Changeability • The capability of the software product to enable a specified modification to be implemented. -Stability • The capability of the software product to avoid unexpected effects from modificationsof the software. -Testability • The capability of the software product to enable modified software to be validated. -Maintainability compliance• The capability of the software product to adhere to standardsor conventions relating to maintainability.
2009-11-2912
Portability
The capability of the software product to be transferred from one environment to another. -Adaptability • The capability of the software product to be adapted for differentspecified environmentswithout applying actions or means other than those provided for this purpose for the software considered.
-Installability • The capability of the software product to be installed in a specified environment. -Co-existence • The capability of the software product to co-exist with other independent software in a common environmentsharing common resources. -Replaceability • The capability of the software product to be used in place of another specified software productfor the same purpose in the same environment. -Portability compliance• The capability of the software product to adhere to standardsor conventions relating to portability.
72009-11-2913
Quality in Use
•Quality in Use -Is the user's view of the qualityof the software product when it is used in a specific environment and a specific context of use. - It measures the extent to which users can achieve their goalsin a particular environment,2009-11-2914
Quality in Use
Effectiveness
ProductivitySecuritySatisfaction
Quality in Use
82009-11-2915
Quality in Use
•Effectiveness - The capability of the software product to enable users to achieve specified goalswith accuracy and completeness in a specified context of use. •Productivity - The capability of the software product to enable users to expend appropriate amounts of resources in relation to the effectiveness achieved in a specified context of use. •Safety - The capability of the software product to achieveacceptable levels of riskof harm to people, business, software, property or the environment in a specified context of use.
•Satisfaction - The capability of the software product to satisfy usersin a specified context of use.