Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 26561:2019 — Software Engineering — Product Family — Quality Management
Ensuring quality across software product families and their shared platforms
Introduction to Quality Management in Product Families
ISO/IEC 26561:2019 is a critical standard that addresses quality management specifically within the context of software product family engineering. Quality management in a product family is inherently more complex than in single-product development because quality must be assessed and assured across multiple dimensions: the quality of the platform itself, the quality of derived products, and the quality of the variability mechanisms that connect them.
In a product family, quality is not a property of individual products — it is a property of the entire production system. A defect in the platform core propagates to every product in the family, making quality management a strategic imperative.
The standard integrates with and extends ISO/IEC 25000 series (SQuaRE) quality models by adding product-family-specific quality attributes and measurement frameworks. It is designed for quality managers, product line engineers, process improvement specialists, and anyone responsible for ensuring that product family deliverables meet their quality objectives.
Quality Model for Product Families
The standard introduces a specialized quality model for product families that extends the traditional ISO/IEC 25010 quality characteristics with family-specific considerations. Key additions include:
Variability Quality
This dimension assesses the quality of the variability mechanisms themselves, including: correctness of variability implementation (do the mechanisms correctly select the intended variants?), completeness of variability coverage (are all required variation points defined?), consistency of variability across artifacts (is the same variation point handled consistently in requirements, design, code, and tests?), and binding time appropriateness (is each variation point bound at the optimal time for its context?).
| Quality Attribute | Definition | Product Family Specificity | Measurement Approach |
|---|---|---|---|
| Variability Correctness | Variants are correctly selected and applied | Unique to product families | Variant selection test coverage |
| Reusability | Platform assets can be reused across products | High — core product family goal | Reuse ratio, adaptation effort |
| Commonality Stability | Shared core remains stable across variants | Critical for platform governance | Breaking change frequency |
| Configurability | Products can be configured without platform changes | Essential for scalability | Configuration effort per product |
| Consistency | Variability is handled consistently across artifacts | Cross-cutting concern | Traceability coverage, consistency audits |
Quality Measurement and Assessment
ISO/IEC 26561:2019 provides a comprehensive measurement framework for assessing product family quality. Key measurement categories include:
Platform Quality Metrics
These assess the quality of the shared core assets: platform defect density (defects per function point in the platform core), platform stability (frequency of breaking changes in platform interfaces), platform modularity (cohesion and coupling metrics for platform components), and platform documentation quality (completeness and accuracy of platform documentation).
Establish a platform quality baseline early in the product family lifecycle. Track platform quality metrics separately from product-specific metrics — a declining platform quality trend is the earliest warning sign of product family sustainability issues.
Product Quality Metrics
These assess the quality of derived products and include: product-specific defect density (defects in the product-specific layer vs. defects inherited from the platform), configuration quality (percentage of product configurations that pass validation as defined by the variability model), and product-to-platform defect ratio (indicates whether quality issues originate in the platform or in product-specific code).
Process Quality Metrics
The standard also defines process-level metrics: variability management process compliance (adherence to defined variability procedures), platform evolution cycle time (time from change request to platform release), and product derivation efficiency (effort required to derive a product from the platform).
Beware of metric proliferation. The standard provides a comprehensive set of candidate metrics — organizations should select a focused subset aligned with their specific quality goals and business context rather than attempting to measure everything.
Quality Assurance Activities
The standard defines quality assurance activities specific to product families: variability-centered reviews (reviews that focus on the correctness and completeness of variability specifications), platform quality audits (periodic assessments of platform health and adherence to quality standards), cross-product consistency checks (verifying that quality is consistent across all derived products), and supplier quality management (managing quality of third-party components that become part of the platform).
Continuous Quality Improvement Cycle
The standard promotes a continuous quality improvement cycle specifically designed for product families. This cycle integrates quality management with platform governance: quality metrics collected from product teams are reviewed in platform board meetings, systemic quality issues trigger platform improvement initiatives, and platform quality improvements are validated through their impact on derived product quality. The standard recommends establishing a quality review board that meets at least monthly, with representatives from the platform team, product teams, and quality assurance. Key artifacts include a platform quality dashboard that provides real-time visibility into quality trends across the product family, a quality improvement backlog that tracks platform-level quality enhancement initiatives, and a lessons-learned repository that captures quality-related knowledge from product teams for reuse across the family. This systematic approach to quality improvement ensures that quality management remains proactive rather than reactive, and that quality investments are directed to the areas of greatest impact on overall product family success.
Frequently Asked Questions
Q: How does ISO/IEC 26561 relate to ISO/IEC 25010 (SQuaRE quality model)?
ISO/IEC 26561 extends the ISO/IEC 25010 quality model with product-family-specific characteristics such as variability quality, reusability, and configurability. It also provides measurement guidance tailored to product family contexts. The two standards are complementary — 25010 provides the base quality model, and 26561 provides the family-specific extension.
ISO/IEC 26561 extends the ISO/IEC 25010 quality model with product-family-specific characteristics such as variability quality, reusability, and configurability. It also provides measurement guidance tailored to product family contexts. The two standards are complementary — 25010 provides the base quality model, and 26561 provides the family-specific extension.
Q: Can we apply ISO/IEC 26561 without implementing all the other 2655x standards?
Yes. While the standard is designed to integrate with the full product family management framework, its quality management principles can be applied independently. However, the maximum benefit is achieved when combined with platform management (26557), variability management (26558), testing management (26559), and operations management (26560), as quality is a cross-cutting concern.
Yes. While the standard is designed to integrate with the full product family management framework, its quality management principles can be applied independently. However, the maximum benefit is achieved when combined with platform management (26557), variability management (26558), testing management (26559), and operations management (26560), as quality is a cross-cutting concern.
Q: What is the recommended frequency for platform quality audits?
The standard recommends that platform quality audits be conducted at least once per major platform release cycle, or quarterly for actively evolving platforms. Triggers for ad-hoc audits include: significant platform architectural changes, accumulation of platform defects beyond established thresholds, or changes in product family scope that affect quality goals.
The standard recommends that platform quality audits be conducted at least once per major platform release cycle, or quarterly for actively evolving platforms. Triggers for ad-hoc audits include: significant platform architectural changes, accumulation of platform defects beyond established thresholds, or changes in product family scope that affect quality goals.
Q: How do we handle quality trade-offs between platform reusability and product-specific optimization?
Quality trade-offs should be managed through the governance framework defined in ISO/IEC 26557. The standard recommends establishing quality attribute scenarios that explicitly document the trade-off decisions, including the rationale, stakeholders involved, and impact analysis. These decisions should be reviewed periodically as both the platform and market conditions evolve.
Quality trade-offs should be managed through the governance framework defined in ISO/IEC 26557. The standard recommends establishing quality attribute scenarios that explicitly document the trade-off decisions, including the rationale, stakeholders involved, and impact analysis. These decisions should be reviewed periodically as both the platform and market conditions evolve.
