ISO/IEC TS 25052-1:2022 システムおよびソフトウェア エンジニアリング — システムおよびソフトウェアの品質要件と評価 (SQuaRE):クラウド サービス — Part 1: 品質モデル | ページ 6

3.1.1

service performance efficiency

degree to which a cloud service meets performance requirements under stated conditions

3.1.1.1

time-behaviour

degree to which a cloud service meets the requirements of the response times and throughput rates of a cloud service, when concurrent users take advantage of the cloud service

[SOURCE:ISO/IEC 25010:2011, 4.2.2.1, modified — “a cloud service meets the requirements of” has been added, “a product or system” has been replaced by “a cloud service” and “when performing its functions, meet requirements” by “when concurrent users take advantage of the cloud service”]

3.1.1.2

aggregated resource utilization

degree to which a cloud service utilizes efficiently aggregated resources from resource pooling in order to support multi-tenancy

Note 1 to entry: Resource pooling is the feature where physical or virtual resources can be aggregated to provide a cloud service to one or more cloud service customers.

Note 2 to entry: Resources include CPU, memory, disk and network.

3.1.1.3

capacity

degree to which the maximum limits of a cloud service’s parameters meet requirements in SLA (Service Level Agreement)

Note 1 to entry: Parameters can include the limit of simultaneous cloud service connections, the limit of available cloud service resources, cloud service throughput and cloud service bandwidth.

[SOURCE:ISO/IEC 25010:2011, 4.2.2.3, modified — “a product or system parameter” has been replaced by “a cloud service's parameters” and “in SLA (Service Level Agreement)” has been added]

3.1.1.4

scalability

degree to which physical and virtual resources are available automatically and immediately, when they are needed, subject to constraints of service agreements

3.1.1.5

elasticity

degree to which a cloud service adjusts rapidly and elastically the amount of resources that are allocated to an instance of the service

3.1.2

service compatibility

degree to which a cloud service can exchange information with CSC’s systems or other cloud services and/or perform its required functions

[SOURCE:ISO/IEC 25010:2011, 4.2.3, modified- “a product, system or component” has been replaced by “a cloud service” and “other products, systems or components” by “CSC’s systems or other cloud services”, and “while sharing the same hardware or software environment” has been deleted.]

3.1.2.1

cloud interoperability

degree to which a cloud service interacts with CSC's systems, or interacts with other cloud services, by exchanging information according to a prescribed method to obtain predictable results

[SOURCE:ISO/IEC 22123-1: 2021, 3.7.2, modified — “ability of a CSC’s system to interact with a cloud service, or the ability for one cloud service to interact” has been replaced by “degree to which a cloud service interacts with CSC's systems, or interacts”]

3.1.3

service usability

degree to which a cloud service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use

[SOURCE:ISO/IEC 25010:2011, 4.2.4, modified — “a product or system” has been replaced by “a cloud service”]

3.1.3.1

accessibility

degree to which a cloud service can be accessed by a variety of client devices over a network through standard mechanisms

3.1.4

service reliability

degree to which a cloud service performs specified functions under specified conditions for a specified period of time

[SOURCE:ISO/IEC 25010:2011, 4.2.5, modified — “a system, product or component” has been replaced by “a cloud service”]

3.1.4.1

availability

degree to which a cloud service is accessible and usable upon demand by an authorized entity

[SOURCE:ISO/IEC 22123-1: 2021, 3.14.7, modified — “property of being” has been replaced by “degree to which a cloud service is”]

3.1.4.2

resilience

degree to which a cloud service recovers operational condition quickly after a fault occurs

[SOURCE:ISO/IEC 19086-1:2016, 3.19, modified — “ability of” has been replaced by “degree to which”]

3.1.4.3

recoverability

degree to which a cloud service supports its critical business functions to an acceptable level within a predetermined period of time following a disaster

[SOURCE:ISO/IEC 19086-1:2016, 3.7, modified — “ability of the ICT elements of an organization to support” has been replaced by “degree to which a cloud service supports”]

3.1.5

service security

degree to which a cloud 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

[SOURCE:ISO/IEC 25010:2011, 4.2.6, modified — “a product or system” has been replaced by “a cloud service”]

3.1.5.1

confidentiality

degree to which a cloud service ensures that data are accessible only to those authorized to have access

[SOURCE:ISO/IEC 25010:2011, 4.2.6.1, modified — “a product or system” has been replaced by “a cloud service”]

3.1.5.2

accountability

degree to which the actions of an entity can be traced back uniquely to the entity

[SOURCE:ISO/IEC 25010:2011, 4.2.6.4 — “back” has been added]

3.1.5.3

isolation

degree to which computations and data of a cloud service are isolated from and inaccessible to one another in the situation that physical and virtual resources are shared by multi-tenants

3.1.5.4

PII protection conformance

personally identifiable information protection conformance

degree to which a cloud service conforms to the standards, laws, or regulations applied to collection, processing and disposal of PII (personally identifiable information)

Note 1 to entry: The scope of PII is determined by laws or regulations of the country where a cloud service is provided. If privacy data, such as race, religion, and health, is considered PII, a cloud service needs to address compliance with relating laws or regulations to protect the privacy data.

3.1.5.5

security responsibility

degree to which the security responsibilities of both CSC and CSP are clearly defined and security incidents are detected and reported by either party

3.1.5.6

asset protection

degree to which a cloud service has processes to protect physical facilities used to provide the covered services from loss of data, connectivity and availability of necessary infrastructure and IT equipment, and to secure the covered services during operation

Note 1 to entry: Connections to cloud services should be protected, and therefore far less vulnerable to virus or other malware attacks. They should also be strong enough to withstand determined distributed denial of service (DDoS) attacks from hackers and botnets.

3.1.6

service maintainability

degree of effectiveness and efficiency with which a cloud service can be modified by the intended maintainers

Note 1 to entry: Modifications can include corrections, improvements or adaptation of a cloud service to changes in environment, and in requirements and functional specifications. Modifications include those carried out by specialized support staff, and those carried out by business or operational staff, or end users.

Note 2 to entry: Maintainability includes installation of updates and upgrades.

[SOURCE:ISO/IEC 25010:2011, 4.2.7, modified — “a product or system” has been replaced by “a cloud service”]

3.1.6.1

maintenance compliance and versioning

degree to which a cloud service provides maintenance according to the SLA, and a new version is assigned and published after maintenance

Note 1 to entry: Maintenance is the process of modifying a system or component after delivery to correct flaws, improve performance or other attributes, or adapt to a changed environment.

3.1.6.2

reversibility

degree to which a cloud service provides the process for the CSC to retrieve their data and application artifacts and for the CSP to delete all CSC data as well as contractually specified cloud service derived data after the agreed upon period

[SOURCE:ISO/IEC 22123-1:2021, 3.14.8, modified — “degree to which a cloud service provides” is added and “an agreed period” has been replaced by “the agreed upon period”]

3.1.6.3

monitorability

degree to which a cloud service provides monitoring parameters and tools to monitor the performance of the service

3.1.7

portability

degree of a cloud service provides the ability to move data and migrate applications from one cloud service to another

3.1.7.1

cloud data portability

degree to which a cloud service provides the ability to move their data from one cloud service to another

[SOURCE:ISO/IEC 22123-1:2021, 3.9.3, modified — “data portability” has been deleted, and “degree to which a cloud service provides the ability to move their data” has been added]

3.1.7.2

cloud application portability

degree to which a cloud service provides the ability to migrate their applications from one cloud service to another

[SOURCE:ISO/IEC 22123-1:2021, 3.9.1, modified — “degree to which a cloud service provides” has been added]

3.1.8

service provisionability

degree to which a cloud service is provisioned by the CSC, as needed, automatically or with minimal interaction with the CSP

3.1.8.1

service measurability

degree to which a cloud service provides metered delivery of cloud services such that usage can be monitored, controlled, reported and billed

[SOURCE:ISO/IEC 22123-1:2021, 3.5.1, modified — “degree to which a cloud service provides” has been added]

3.1.8.2

auditability

degree to which a cloud service collects and provides available necessary evidential information related to the operation and use of a cloud service for the purpose of conducting an audit

[SOURCE:ISO/IEC 22123-1:2021, 3.14.11, modified — “capability of collecting and making” has been replaced by “degree to which a cloud service collects and provides”]

3.1.8.3

governability

degree to which the provision and use of a cloud service is directed and controlled by a system, and which the cloud service complies with the regulations applied in the countries where the cloud service is used

3.1.8.4

self-provisioning

degree to which a cloud service supports on-demand self-service

3.1.8.5

SLA information completeness

service level agreement information completeness

degree to which SLA include the essential information required to set up the quality level of the cloud services

Note 1 to entry: The essential information includes covered services, SLO (service level objectives) and SQO (service qualitative objectives).

3.1.8.6

SLA satisfaction

service level agreement satisfaction

degree to which a cloud service satisfies the cloud SLOs and SQOs specified in SLA

3.1.9

service responsiveness

degree to which a cloud service responds to CSC requests and provides outcomes in a prompt and timely way

[SOURCE:ISO/IEC TS 25011:2017, 3.2.6, modified — “an IT service” has been replaced by “a cloud service”, and “to CSC request” has been added]

3.1.9.1

service supportiveness

degree to which a cloud service supports CSC activities according to the service support scope specified in SLA

3.1.9.2

reactiveness

degree to which a cloud service promptly responds to user requests

[SOURCE:ISO/IEC TS 25011:2017, 3.2.6.2, modified — “an IT service” has been replaced by “a cloud service”]

3.1.9.3

continuity

degree to which a cloud service is provided under all foreseeable circumstances, including mitigating the risks resulting from interruption to an acceptable level

[SOURCE:ISO/IEC TS 25011:2017, 3.2.4.1, modified — “an IT service” has been replaced by “a cloud service”]