Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding CAN CSA ISO IEC TR 9126-2-04: External Metrics for Software Product Quality
A Comprehensive Guide to the Canadian Adoption of ISO/IEC TR 9126-2:2004 for Software Quality Measurement
Introduction
The CAN CSA ISO IEC TR 9126-2-04 is the Canadian adoption of the international Technical Report ISO/IEC TR 9126-2:2004, which defines a comprehensive set of external metrics for evaluating software product quality. This standard is part of the ISO/IEC 9126 series, the precursor to the ISO/IEC 25000 SQuaRE (Software Quality Requirements and Evaluation) framework. It provides organizations with practical measures to assess software behaviour during testing, operation, and maintenance from an external perspective—how the software performs in its intended environment.
Why It Matters: CAN CSA ISO IEC TR 9126-2-04 enables consistent, reproducible measurement of software quality characteristics, supporting benchmarking, procurement, and process improvement initiatives across Canadian and international markets.
1. Scope of CAN CSA ISO IEC TR 9126-2-04
The Technical Report specifies a taxonomy of external metrics for the six quality characteristics defined in ISO/IEC 9126-1: Functionality, Reliability, Usability, Efficiency, Maintainability, and Portability. Each characteristic is further divided into subcharacteristics. The metrics are intended to be used during the later stages of the software life cycle—primarily during testing and operational use—where the product is executed in a specific environment.
Scope Note: This standard does not define internal metrics or quality-in-use metrics. For those, refer to ISO/IEC TR 9126-3 and ISO/IEC TR 9126-4 respectively.
2. Technical Requirements: Quality Characteristics and External Metrics
CAN CSA ISO IEC TR 9126-2-04 provides a detailed breakdown of each quality characteristic and its subcharacteristics, along with one or more base measures and derived measures. The metrics are classified by their applicability phase (e.g., test, operation). The following table summarizes the core characteristics and representative metrics:
| Quality Characteristic | Subcharacteristics (selected) | Example External Metric | Measurement Formula (Simplified) |
|---|---|---|---|
| Functionality | Suitability, Accuracy, Security | Functional Implementation Coverage | Number of implemented functions / total required functions |
| Reliability | Maturity, Fault Tolerance, Recoverability | Mean Time Between Failures (MTBF) | Total operation time / number of failures |
| Usability | Understandability, Learnability, Operability | Task Effectiveness | Proportion of tasks completed by user without error |
| Efficiency | Time Behaviour, Resource Utilisation | Response Time Under Load | Average response time across defined workload scenarios |
| Maintainability | Analysability, Changeability, Stability | Change Success Ratio | Successful changes / total attempted changes |
| Portability | Adaptability, Installability, Replaceability | Porting Effort Ratio | Effort to port to new platform / original development effort |
Important: The metrics in this Technical Report are guidelines—not prescriptive. Users must adapt them to their specific context, product type, and organisational quality goals.
Each metric entry includes:
- Metric name and purpose
- Measurement method (quantification approach)
- Scale type (nominal, ordinal, interval, or ratio)
- Measurement formula
- Interpretation guidance (e.g., higher values indicate better quality)
2.1 Relationship to the Quality Model
The external metrics align with the quality model in ISO/IEC 9126-1. For each subcharacteristic, the Technical Report defines one or more metrics that capture externally visible attributes. For instance, under Reliability -> Maturity, the metric Failure Density is defined as the number of failures per unit of time (e.g., per hour of operation).
Benefit: Using these metrics allows stakeholders to set quantifiable acceptance criteria and track quality improvements over releases.
3. Implementation Highlights
Successfully applying CAN CSA ISO IEC TR 9126-2-04 requires integration into the software development life cycle, particularly during system testing and acceptance testing. Here are practical implementation steps:
- Select metrics aligned with project goals – Not all metrics are relevant for every project; prioritise those that reflect critical quality attributes (e.g., safety, performance).
- Establish measurement baselines – Collect data over a baseline release to calibrate expected ranges.
- Automate data collection – Use testing frameworks, monitoring tools, and log analysis to gather base measures efficiently.
- Interpret results contextually – Use the interpretation guidance from the standard to decide whether measured values indicate acceptable quality or need corrective action.
Tip: Consider complementing external metrics with internal metrics (ISO/IEC TR 9126-3) for early quality prediction. The combination provides a more complete view.
Caution: External metrics are sensitive to the test environment and operational profiles. Always document the context in which measurements were taken to ensure comparability.
4. Compliance and Adoption Considerations
As a Canadian adoption (CAN/CSA), this standard is identical in technical content to ISO/IEC TR 9126-2:2004. Organizations seeking to demonstrate alignment with international best practices for software quality can reference this Canadian standard to meet both domestic and global requirements.
- Adoption status: Published by Canadian Standards Association (CSA Group) as a National Standard of Canada.
- Equivalence: Technically identical to the original ISO/IEC TR; no deviations or additional Canadian-specific annexes.
- Regulatory use: While not mandatory by law, it may be invoked in contracts, procurement specifications, or quality management systems following ISO 9000 principles.
Note on Supersession: The ISO/IEC 9126 series has been superseded by the ISO/IEC 25000 SQuaRE series (e.g., ISO 25010:2011, ISO 25023:2016). However, CAN CSA ISO IEC TR 9126-2-04 remains available for legacy systems or as a transitional reference. Organizations are encouraged to migrate to the newer standards for current projects.
Frequently Asked Questions
Q: What is the difference between internal and external metrics as described in the 9126 series?
A: Internal metrics (Part 3) measure attributes of the software itself (e.g., code complexity, test coverage) during development. External metrics (Part 2) measure behaviour of the system as a whole when executed, such as response time, reliability during operation, or user task completion. External metrics are typically measured during testing or in production.
A: Internal metrics (Part 3) measure attributes of the software itself (e.g., code complexity, test coverage) during development. External metrics (Part 2) measure behaviour of the system as a whole when executed, such as response time, reliability during operation, or user task completion. External metrics are typically measured during testing or in production.
Q: Is CAN CSA ISO IEC TR 9126-2-04 still current, or has it been replaced?
A: The technical content of ISO/IEC TR 9126-2:2004 has been superseded by the ISO/IEC 25000 series, in particular ISO 25023 (external metrics for product quality). However, the CAN/CSA adoption remains available as a stable reference for contracts or legacy systems that were designed under the older framework. For new projects, adopting the SQuaRE series is recommended.
A: The technical content of ISO/IEC TR 9126-2:2004 has been superseded by the ISO/IEC 25000 series, in particular ISO 25023 (external metrics for product quality). However, the CAN/CSA adoption remains available as a stable reference for contracts or legacy systems that were designed under the older framework. For new projects, adopting the SQuaRE series is recommended.
Q: Can I use the metrics from this standard for agile or DevOps processes?
A: Yes. Many of the external metrics (e.g., failure rate, response time, change success ratio) fit well into continuous testing and monitoring pipelines. Teams should select a subset that aligns with their quality goals and automate data collection as part of their CI/CD workflows.
A: Yes. Many of the external metrics (e.g., failure rate, response time, change success ratio) fit well into continuous testing and monitoring pipelines. Teams should select a subset that aligns with their quality goals and automate data collection as part of their CI/CD workflows.
Q: How does this standard relate to ISO 9001?
A: ISO 9001 requires organisations to monitor and measure product quality. CAN CSA ISO IEC TR 9126-2-04 provides a structured, internationally recognised approach to defining software quality metrics, which can support the measurement requirements of a quality management system. However, it is not a mandatory element of ISO 9001 certification.
A: ISO 9001 requires organisations to monitor and measure product quality. CAN CSA ISO IEC TR 9126-2-04 provides a structured, internationally recognised approach to defining software quality metrics, which can support the measurement requirements of a quality management system. However, it is not a mandatory element of ISO 9001 certification.
© 2026 — This article is for informational purposes and does not constitute legal or certification advice. Always consult the most recent published version of the standard from CSA Group or ISO.