ISO/TR 25060 — SQuaRE: General Framework for Common Industry Format (CIF) for Usability-Related Information

Structured Documentation Framework for Human-Centred Design and Usability Engineering

1. Introduction to ISO/TR 25060 and the CIF Framework

ISO/TR 25060:2023, developed jointly by ISO/TC 159/SC 4 (Ergonomics of human-system interaction) and ISO/IEC JTC 1/SC 7 (Software and systems engineering), defines a general framework for the Common Industry Format (CIF) for usability-related information. This Technical Report is part of the SQuaRE (Systems and software Quality Requirements and Evaluation) family of documents and provides a structured approach to documenting and communicating usability information throughout the system development life cycle.

The human-centred design approach established in ISO 9241-210 emphasizes that usability can only be achieved when user needs, tasks, and environments are systematically considered from the outset. ISO/TR 25060 operationalizes this principle by defining a set of information items — each with a prescribed content structure, terminology, and intended audience — that together form a complete usability documentation package.

The CIF framework is process-agnostic: it can be integrated into waterfall, agile, DevOps, or any other development methodology. The key requirement is that usability information is systematically captured and made available to all stakeholders at the right time.

2. Information Items and Content Structure

ISO/TR 25060 identifies seven primary usability-related information items, each addressing a distinct aspect of human-centred design. These items are referenced by separate International Standards that elaborate their detailed format.

Information ItemStandard ReferencePurposePrimary Users
Context of Use DescriptionISO/IEC 25063Describes users, goals, tasks, resources, and environmentsDesigners, evaluators
User Needs ReportISO/IEC 25064Documents user needs derived from researchRequirements engineers
User Requirements SpecificationISO 25065Specifies measurable usability requirementsDevelopers, testers
User-System Interaction and UI SpecificationDescribes interaction design and interface behaviourUI designers, developers
Evaluation ReportISO/IEC 25066Reports usability evaluation findingsProject managers, stakeholders
Quantitative Usability Test ReportISO/IEC 25062Reports effectiveness, efficiency, and satisfaction metricsProcurement, quality assurance
Field Data ReportCaptures usability data from deployed systemsMaintenance, product improvement

2.1 Framework Design Principles

The framework is built on four key design principles. First, process independence — the information items are defined independently of any specific development process, allowing integration with diverse methodologies. Second, iterative refinement — information items can be initially drafted at a high level and progressively detailed as understanding grows. Third, stakeholder orientation — each item specifies its intended users and uses, ensuring that documentation serves practical purposes rather than bureaucratic overhead. Fourth, traceability — items reference each other, creating a coherent chain from user research through design to evaluation.

A common failure mode in usability engineering is treating these information items as one-time deliverables rather than living documents. The CIF framework explicitly supports iteration — new insights from evaluation should feed back into updated context descriptions, user needs, and requirements.

3. Engineering Design Insights: Practical Application

For engineers and usability practitioners, ISO/TR 25060 provides several actionable insights:

3.1 Procurement and Acquisition Support

The CIF framework is particularly valuable in procurement contexts. Organizations acquiring interactive systems can specify that suppliers must deliver CIF-conformant usability information items as part of the contract deliverables. This enables evidence-based comparison of competing products and provides objective criteria for acceptance testing. The Quantitative Usability Test Report (ISO/IEC 25062) is especially useful here, as it enables direct comparison of effectiveness, efficiency, and satisfaction metrics across products.

3.2 Integration with Agile Development

Contrary to the perception that usability documentation is incompatible with agile methods, the CIF framework can be effectively integrated into agile workflows. Each information item can be maintained as a lightweight artefact that evolves across sprints. The Context of Use Description can be refined as user stories are elaborated. The User Requirements Specification can be linked to acceptance criteria. The Evaluation Report can capture sprint review findings.

3.3 Regulatory Compliance and Risk Mitigation

In regulated domains such as medical devices, aviation, and industrial control systems, usability documentation is a regulatory requirement (e.g., IEC 62366 for medical devices, FDA human factors guidance). The CIF framework provides a ready-made structure that satisfies many regulatory expectations, reducing the effort needed to compile compliance evidence.

For organizations building their usability capability, adopting the CIF framework provides a systematic pathway from ad-hoc usability testing to mature, integrated human-centred design. The framework’s modular structure allows incremental adoption — start with the Context of Use Description and Evaluation Report, then add other items as the practice matures.

4. Frequently Asked Questions

Q1: Is ISO/TR 25060 applicable to non-software products?
Yes. The CIF framework covers systems broadly, including hardware-software combinations, services, and documentation. The term “interactive system” in the standard encompasses any combination of hardware, software, services, and people that users interact with.
Q2: How does ISO/TR 25060 relate to UX maturity models?
The CIF framework supports UX maturity assessment by defining the information items that a mature organization should produce. Standards such as ISO/TR 18458 (maturity model for human-centred design) reference the CIF information items as indicators of organizational capability.
Q3: What is the difference between CIF and traditional usability testing reports?
Traditional reports vary widely in format and content. CIF standardizes the structure, ensuring that all essential information — including context, methodology, metrics, and findings — is consistently captured and comparable across projects and organizations.
Q4: Can CIF information items be automated?
Partially. The structured nature of CIF items makes them suitable for template-based authoring tools and requirements management systems. Automated extraction of usability metrics from analytics platforms can populate the Quantitative Usability Test Report directly.

📥 Standard Documents Download

🔒
Please wait 10 seconds, the download links will appear after the ad loads

Leave a Reply

Your email address will not be published. Required fields are marked *