Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC TS 25011:2017 — IT Service Quality Models
ISO/IEC TS 25011 — Technical Specification Overview
Introduction to ISO/IEC TS 25011
ISO/IEC TS 25011:2017 is a Technical Specification that extends the SQuaRE (System and Software Quality Requirements and Evaluation) series into the domain of IT services. While the conventional ISO/IEC 25010 standard defines quality models for software products and computer systems, TS 25011 addresses a critical gap: how do we define, characterize, and evaluate the quality of IT services? As organizations increasingly transition from product-centric to service-centric delivery models — encompassing cloud computing, managed services, and IT outsourcing — having a dedicated quality model for IT services becomes essential for both providers and consumers.
Unlike software quality models that focus on static code and system attributes, TS 25011 recognizes that IT services are co-produced with the customer, evolve over time, and depend heavily on human interactions and service management processes.
The specification defines two complementary quality models: a service quality in use model viewed from the stakeholder’s perspective, and a service product quality model viewed from the provider’s perspective. This dual-model approach ensures comprehensive coverage of the service lifecycle — from design and delivery to consumption and evaluation.
TS 25011 is situated within the broader ISO/IEC 25000 SQuaRE framework and aligns with IT service management standards such as ISO/IEC 20000. It provides a common terminology and structured framework that enables objective measurement and benchmarking of IT service quality across different providers and service types.
Key Quality Characteristics and Their Engineering Implications
Service Quality in Use Model
The service quality in use model describes five key characteristics that reflect the outcomes of service interaction from the stakeholder’s viewpoint:
| Characteristic | Definition | Engineering Insight |
|---|---|---|
| Effectiveness | Accuracy and completeness with which users achieve specified goals | Map service outcomes to explicit measurable KPIs; design service level agreements (SLAs) around goal completion rates rather than technical metrics alone |
| Efficiency | Resources expended relative to the accuracy and completeness of goals achieved | Measure resource consumption (time, human effort, compute) per service transaction; optimize self-service portals to reduce agent-assisted interactions |
| Satisfaction | Degree to which user needs are satisfied when using the service | Deploy continuous satisfaction surveying with standardized instruments (e.g., CSAT, NPS); correlate satisfaction data with operational metrics to identify root causes |
| Freedom from Risk | Degree to which a service mitigates potential risks to economic status, human life, health, or the environment | Implement service continuity management, disaster recovery testing, and security incident response; quantify risk exposure in SLA credits |
| Context Coverage | Degree to which a service can be used effectively, efficiently, and satisfactorily in specified contexts of use | Design for multichannel delivery (web, mobile, API); test service behavior under varying network conditions, device types, and user profiles |
A common pitfall in IT service management is focusing exclusively on technical availability (uptime) while neglecting the broader quality dimensions. TS 25011 reminds us that a service that is “up” but fails to satisfy user needs or introduces risk is not a quality service.
Service Product Quality Model
From the provider’s perspective, the service product quality model includes the following characteristics that must be engineered into the service design:
| Characteristic | Description | Practical Application |
|---|---|---|
| Functional Suitability | Degree to which the service meets stated and implied needs when used under specified conditions | Define service functional requirements through structured service design packs; conduct service acceptance testing before go-live |
| Performance Efficiency | Performance relative to the amount of resources used under stated conditions | Establish performance baselines and auto-scaling thresholds; implement capacity management processes |
| Compatibility | Degree to which a service can exchange information with other products, systems, or services | Adopt open standards for APIs and data formats; maintain interoperability matrices for integrated service chains |
| Usability | Degree to which a service can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction | Conduct user research and usability testing for service interfaces; design self-service portals with intuitive workflows |
| Reliability | Degree to which a service performs specified functions under specified conditions for a specified period | Architect for redundancy and failover; implement proactive monitoring and automated incident remediation |
| Security | Degree to which a service protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization | Adopt zero-trust security architecture; conduct regular vulnerability assessments and penetration testing |
| Maintainability | Degree of effectiveness and efficiency with which a service can be modified by the intended maintainers | Adopt Infrastructure as Code (IaC) for service configuration management; maintain comprehensive service documentation and runbooks |
| Portability | Degree to which a service can be transferred from one environment to another | Design for cloud-agnostic deployment using containers and orchestration; minimize vendor lock-in through abstraction layers |
Applying TS 25011 in Real-World Service Engineering
The practical value of TS 25011 lies in its application across the IT service lifecycle. During service design, the quality models serve as checklists to ensure all relevant quality dimensions are addressed in service specifications. During service transition, they provide the framework for service acceptance criteria. During service operation, they form the basis for continuous service improvement programs and SLA frameworks.
Organizations that have adopted TS 25011-aligned quality frameworks report improved alignment between IT service delivery and business outcomes, more objective service evaluation, and clearer communication between service providers and consumers.
For service providers implementing TS 25011, the recommended approach begins with mapping existing service quality metrics to the TS 25011 characteristics to identify gaps. Following this gap analysis, organizations should define measurement methods for each relevant characteristic, establish baseline measurements, and set target quality levels. The final step is embedding these measurements into service management processes — incident management, problem management, change management, and continual service improvement — creating a closed-loop quality governance system.
An important engineering insight is that TS 25011 quality characteristics are not independent; they interact and sometimes trade off against each other. For example, increasing security measures may reduce usability, and improving reliability through redundancy increases cost (affecting efficiency from the provider’s perspective). Quality model-based trade-off analysis should be conducted during service design to make these trade-offs explicit and intentional rather than accidental.
Frequently Asked Questions
Q1: How does TS 25011 differ from ISO/IEC 25010?
A: ISO/IEC 25010 defines quality models for software products and computer systems, while TS 25011 specifically addresses IT services. The key differences include a focus on co-production with customers, emphasis on service delivery processes, and characteristics tailored to service-specific attributes like context coverage and service continuity.
A: ISO/IEC 25010 defines quality models for software products and computer systems, while TS 25011 specifically addresses IT services. The key differences include a focus on co-production with customers, emphasis on service delivery processes, and characteristics tailored to service-specific attributes like context coverage and service continuity.
Q2: Can TS 25011 be used for cloud services?
A: Yes, TS 25011 is well-suited for cloud services, and it has been complemented by TS 25052-1 and TS 25052-2 which provide more specific quality models for cloud service domains including SaaS, PaaS, and IaaS delivery models.
A: Yes, TS 25011 is well-suited for cloud services, and it has been complemented by TS 25052-1 and TS 25052-2 which provide more specific quality models for cloud service domains including SaaS, PaaS, and IaaS delivery models.
Q3: How do I measure service satisfaction under TS 25011?
A: TS 25011 recommends using standardized satisfaction measures including CSAT (Customer Satisfaction Score), NPS (Net Promoter Score), and CES (Customer Effort Score), supplemented by contextual inquiry and service-specific satisfaction surveys aligned with the service quality in use model.
A: TS 25011 recommends using standardized satisfaction measures including CSAT (Customer Satisfaction Score), NPS (Net Promoter Score), and CES (Customer Effort Score), supplemented by contextual inquiry and service-specific satisfaction surveys aligned with the service quality in use model.
Q4: Is TS 25011 certification available?
A: TS 25011 is a Technical Specification, not an International Standard, so it does not offer formal certification. However, organizations can use it internally or contractually as a framework for service quality assurance and as input to ISO/IEC 20000-based service management systems.
A: TS 25011 is a Technical Specification, not an International Standard, so it does not offer formal certification. However, organizations can use it internally or contractually as a framework for service quality assurance and as input to ISO/IEC 20000-based service management systems.
