Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 26553:2018 — Software Engineering — Product Family Engineering — Configuration Management
Configuration management strategies for software product families with variability-aware versioning and build management
Overview of ISO/IEC 26553:2018
ISO/IEC 26553:2018 addresses the critical discipline of configuration management (CM) in the context of software product family engineering.
While configuration management for single systems is well understood, product families introduce unique challenges: managing variants of configuration items, maintaining multiple product derivations simultaneously, and ensuring that shared core assets evolve without breaking existing product instances.
The standard provides a comprehensive framework for tracking and controlling changes to product family artifacts — including requirements, design models, source code, test cases, and documentation — across both domain engineering and application engineering lifecycles.
Effective CM is foundational to achieving sustainable reuse in product families.
ISO/IEC 26553 recognizes that in product family engineering, configuration management is not merely about version control. It encompasses variability management, product derivation configuration, and systematic baseline management across the entire product portfolio.
Core Configuration Management Processes
The standard defines several key CM processes specifically adapted for product family contexts:
Variability-Aware Version Control
Traditional version control systems track revisions of individual files over time.
For product families, CM must additionally track which variants of each artifact belong to which product configurations.
This requires techniques such as variant branching, conditional file inclusion, and feature-based version labeling.
| CM Process | Product Family Specifics | Common Techniques |
|---|---|---|
| Version Control | Track artifacts across multiple variant dimensions | Feature branches, variant tags, conditional commits |
| Baseline Management | Define baselines that span the product family platform | Platform releases, feature-complete baselines |
| Build Management | Build systems that resolve variability at build time | Conditional compilation, build-time feature flags, Maven profiles |
| Product Derivation CM | Generate and track product-specific configurations | Product derivation scripts, configuration files |
| Change Management | Assess impact of changes across the product family | Impact analysis, change advisory board |
| Audit and Review | Verify CM integrity across all product instances | Automated CM audits, compliance reports |
Baseline Management Across the Family
A unique contribution of ISO/IEC 26553 is its treatment of baselines in product family contexts.
The standard distinguishes between platform baselines (which capture the state of core assets at a point in time) and product baselines (which capture the configuration of a specific derived product).
Managing the relationship between these two types of baselines is essential for maintaining product family coherence.
Without proper baseline management, organizations face the ‘product family drift’ problem: products diverge from the platform over time, shared fixes are not propagated, and the cost of maintaining the family increases exponentially with each new product addition.
Build Management and Variant Resolution
ISO/IEC 26553 dedicates significant attention to build management in product families.
The build process must resolve variability at the appropriate binding time — whether at compile time (conditional compilation), link time (library selection), or deployment time (configuration files and feature toggles).
The standard describes three primary build strategies for product families:
- Single-product build: Build each product individually with its specific feature set. Simple but does not leverage platform commonalities.
- Platform-first build: Build the shared platform once, then build product-specific layers on top. More efficient for families with high commonality.
- Delta-based build: Build a base product and then generate variants by applying deltas. Most scalable for large product families.
Organizations implementing delta-based builds following ISO/IEC 26553 guidance report 50-70% reduction in build time for product variants compared to individual builds, along with improved consistency across products.
Engineering Design Insights
Key practical takeaways from ISO/IEC 26553 for configuration managers and DevOps engineers:
- Invest in automated CM tooling: Manual CM processes do not scale in product families with more than 5-10 products. Automation of branching, labeling, and build configuration is essential.
- Design your variant strategy before tool selection: Different version control tools support variant management differently. Evaluate tools against your product family structure, not the other way around.
- Establish clear CM roles: The standard recommends designated CM roles for platform-level and product-level configuration management, with clear escalation paths for cross-family issues.
- Implement continuous integration across variants: CI pipelines should validate changes against multiple product configurations, not just a single product, to detect integration issues early.
Do not underestimate the complexity of merging changes across variant branches. Without a disciplined merge strategy, the product family platform can fragment into incompatible forks. ISO/IEC 26553 recommends regular cross-variant merges and automated conflict detection.
Frequently Asked Questions
Q: How does ISO/IEC 26553 differ from standard CM practices like those in ISO/IEC 12207?
ISO/IEC 12207 defines generic CM processes for any software project. ISO/IEC 26553 extends these specifically for product family contexts, adding variability-aware versioning, product derivation configuration management, and platform-vs-product baseline management that are not covered in generic standards.
ISO/IEC 12207 defines generic CM processes for any software project. ISO/IEC 26553 extends these specifically for product family contexts, adding variability-aware versioning, product derivation configuration management, and platform-vs-product baseline management that are not covered in generic standards.
Q: Can Git be used for product family CM as described in ISO/IEC 26553?
Git can be used, but its branch-and-merge model requires careful design for product families. Common approaches include using Git feature branches for variant management, Git submodules for platform sharing, or tools like Git LFS for large binary assets. Some teams supplement Git with dedicated product family CM tools.
Git can be used, but its branch-and-merge model requires careful design for product families. Common approaches include using Git feature branches for variant management, Git submodules for platform sharing, or tools like Git LFS for large binary assets. Some teams supplement Git with dedicated product family CM tools.
Q: What is the recommended approach for managing configuration items that are shared across multiple products?
ISO/IEC 26553 recommends establishing a core asset repository with controlled access and change management. Shared configuration items should have explicit variant tags or attributes indicating which products they apply to. Changes to shared items require impact assessment across all affected products.
ISO/IEC 26553 recommends establishing a core asset repository with controlled access and change management. Shared configuration items should have explicit variant tags or attributes indicating which products they apply to. Changes to shared items require impact assessment across all affected products.
Q: How do we handle CM for legacy products that were not originally built as part of a product family?
The standard provides guidance for migrating legacy products into a product family CM structure. This typically involves reverse-engineering the variant structure, establishing baseline definitions, and incrementally consolidating common assets while managing the transition through a defined migration plan.
The standard provides guidance for migrating legacy products into a product family CM structure. This typically involves reverse-engineering the variant structure, establishing baseline definitions, and incrementally consolidating common assets while managing the transition through a defined migration plan.
