Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 26556:2018 — Software Engineering — Product Family Engineering — Information Management
Managing information assets across software product families for effective reuse and traceability
Introduction to ISO/IEC 26556:2018
ISO/IEC 26556:2018 addresses information management in software product family engineering — the processes and infrastructure for creating, storing, retrieving, and maintaining the information assets that underpin the entire product family lifecycle.
While the other ProdFab standards focus on specific engineering or management disciplines, this standard deals with how information itself is managed as a critical organizational asset.
In product family engineering, information assets are unusually diverse and interconnected. They include feature models, requirements specifications, architecture descriptions, design models, source code, test cases, user documentation, and product derivation artifacts — all of which must be consistently managed and maintained across multiple products and versions.
The standard provides a framework for establishing a coherent information management infrastructure that supports both domain engineering and application engineering.
ISO/IEC 26556 recognizes that information is the most valuable long-term asset in product family engineering. While code can be rewritten, the knowledge embedded in well-structured information assets represents years of accumulated engineering wisdom.
Core Information Management Processes
The standard defines several key information management processes adapted for product family contexts:
Asset Management
At the heart of ISO/IEC 26556 is the concept of core asset management.
Core assets are the reusable information artifacts that constitute the product family platform.
The standard provides guidance on asset identification, classification, storage, retrieval, versioning, and retirement.
A well-organized asset management system enables engineers to quickly find and reuse relevant assets across the product family.
| Information Type | Description | Management Challenges |
|---|---|---|
| Feature Models | Captures commonality and variability of the product family | Versioning, feature dependencies, binding time tracking |
| Requirements Specifications | Domain and application requirements with variability | Traceability, variant selection, impact analysis |
| Architecture Descriptions | Reference architecture and product-specific views | View consistency, architecture conformance |
| Design Models | Detailed component designs and variability realizations | Model synchronization, tool interoperability |
| Test Assets | Reusable test cases, test data, and test configurations | Variant-specific testing, coverage analysis |
| User Documentation | Manuals, help systems, and training materials | Document variability, translation management |
| Product Derivation Records | Configuration choices and derivation history | Audit trail, reproducibility |
Knowledge Management
Beyond structured information assets, ISO/IEC 26556 addresses knowledge management — capturing and sharing the tacit knowledge that engineers acquire while working with the product family.
This includes design rationale, lessons learned, best practices, and expert knowledge about variability decisions and their consequences.
Product family knowledge is often concentrated in a few key engineers. When these individuals leave the organization, critical knowledge about platform design decisions and variability trade-offs can be lost forever. ISO/IEC 26556 emphasizes systematic knowledge capture as a risk mitigation strategy.
Information Modeling and Structuring
The standard provides guidance on creating information models that represent the structure, relationships, and dependencies of product family information assets.
An information model serves as a blueprint for the product family information infrastructure, defining:
- Asset types and their attributes: What kinds of information assets exist and their metadata.
- Relationships between assets: Traceability links, dependency relationships, and configuration associations.
- Access control and security: Who can create, modify, and retire different types of assets.
- Lifecycle states: The states an asset passes through from creation to retirement.
- Variability representation: How variability information is attached to or embedded within assets.
Organizations implementing a well-structured information model following ISO/IEC 26556 report 35-50% improvement in asset retrieval times and significantly reduced duplication of information across the product family.
Engineering Design Insights
Critical insights from the standard for information architects, technical writers, and engineering managers:
- Design the information architecture before populating it: The standard strongly recommends defining the information model first, then gradually populating it with assets. Retrofitting structure onto existing assets is significantly more difficult than building structure from the start.
- Invest in automated information management tooling: With potentially thousands of information assets across dozens of product variants, manual information management does not scale. Asset repositories, search engines, and automated traceability tools are essential.
- Establish information quality criteria: Not all information assets are equally valuable. The standard recommends defining quality criteria (completeness, accuracy, consistency, currency) for different asset types and regularly auditing the asset base.
- Plan for information asset evolution: Just as software evolves, information assets must evolve. The standard provides guidance on asset lifecycle management, including versioning, deprecation, and retirement procedures.
The ‘information silo’ problem is particularly damaging in product families. When different product teams maintain separate information repositories without integration, the product family fragments and the value of the platform diminishes. ISO/IEC 26556 emphasizes integrated information management across the entire product family.
Frequently Asked Questions
Q: How does ISO/IEC 26556 differ from general information management standards like ISO 15489?
ISO 15489 provides generic records management principles. ISO/IEC 26556 specializes these for software product family contexts, addressing variability-aware information modeling, core asset management, and the specific types of information artifacts unique to product line engineering.
ISO 15489 provides generic records management principles. ISO/IEC 26556 specializes these for software product family contexts, addressing variability-aware information modeling, core asset management, and the specific types of information artifacts unique to product line engineering.
Q: What is the relationship between information management in 26556 and configuration management in 26553?
Configuration management (26553) focuses on version control and build management of artifacts. Information management (26556) covers a broader scope including knowledge management, information modeling, content management, and the semantic relationships between information assets. The two standards complement each other.
Configuration management (26553) focuses on version control and build management of artifacts. Information management (26556) covers a broader scope including knowledge management, information modeling, content management, and the semantic relationships between information assets. The two standards complement each other.
Q: How do we handle information management for globally distributed product family teams?
The standard addresses distributed information management, recommending centralized asset repositories with synchronized local caches, clear information ownership policies, and collaboration tools that support asynchronous work across time zones. The information model should account for localization and cultural differences in documentation.
The standard addresses distributed information management, recommending centralized asset repositories with synchronized local caches, clear information ownership policies, and collaboration tools that support asynchronous work across time zones. The information model should account for localization and cultural differences in documentation.
Q: What tools are typically used for product family information management?
Typical tool stacks include asset repositories (e.g., SharePoint, ALM platforms), knowledge bases (Confluence, corporate wikis), document management systems, and specialized product line engineering tools. The standard provides capability requirements to guide tool selection rather than prescribing specific products.
Typical tool stacks include asset repositories (e.g., SharePoint, ALM platforms), knowledge bases (Confluence, corporate wikis), document management systems, and specialized product line engineering tools. The standard provides capability requirements to guide tool selection rather than prescribing specific products.
