ISO/IEC TS 7339:2024 情報テクノロジー — クラウド コンピューティング — プラットフォーム機能のタイプとサービスとしてのプラットフォームの概要 | ページ 6

3.1

platform capabilities type

cloud capabilities type in which the cloud service customer can deploy, manage and run customer-created or customer-acquired applications using one or more programming languages and one or more execution environments supported by the cloud service provider

Note 1 to entry: In this context “applications” can include programs, software components (such as containers, code, function libraries, and microservices, etc.), unfinished or incomplete programs (such as test versions or prototypes), and other forms of source code or executable software code artefacts, with or without a user interface being included.

Note 2 to entry: This does not include any minimal scripting capability internal to a single application, such as simple macros within a spreadsheet.

[SOURCE:ISO/IEC 22123-1:2023, 3.5.4, modified — Notes 1 and 2 to entry have been added.]

3.2

CSC-provided code

software code artefacts created by CSDs acting on the CSC’s behalf, that are designed to execute within a cloud service to meet the needs of the CSC

Note 1 to entry: Such code artefacts can be supplemented by data or metadata.

Note 2 to entry: The CSDs creating the code can be employees or contractors of the CSC, or of another organization such as a vendor, partner, or contractor to the CSC.

3.3

metadata

data that defines and describes other data

Note 1 to entry: Metadata can include many different kinds of attributes of the data it describes. Some metadata fields are almost universal, such as date of creation and last change, type of file or object, permissions, and ownership. Other metadata can be specific to the type of object, such as the camera settings of a digital image, the author’s name for a document, the version of a code artefact, etc.

Note 2 to entry: Some metadata may be directly attached to (or embedded within) the data to which it relates and will always move with it. Other metadata may be stored separately and associated with the data by reference or other means.

[SOURCE:ISO/IEC 11179-3:2022, 3.2.30, modified — The notes to entry have been added.]

3.4

cloud native

cloud native computing

approach and practices for developing, deploying, and running applications and services in cloud computing systems with specific platform capabilities type which offer features such as functional decomposition, containerization, orchestration, microservices for applications, automation, monitoring and logging, and continuous operation

Note 1 to entry: Additional tools and technologies that support these capabilities include DevOps, CI-CD tools, automation of orchestration etc., which individually and collectively, enable autoscaling, resilience, superior performance, ease of portability and interoperability and ease of maintenance among other benefits.

Note 2 to entry: Orchestration refers to automatic or semi-automatic deployment, instantiation, interconnection, and management of containerised software.

Note 3 to entry: This approach contrasts with more traditional virtualisation-based approaches based largely on customer-managed Virtual Machines.

Note 4 to entry: See also Clause 10.

3.5

jurisdiction

geographical or corporate area over which a cloud computing policy extends

Note 1 to entry: In a government policy context this will generally be the geographical area over which the body enacting the policy has legal authority either as government or as authorised regulator. However, in an enterprise or government agency environment, the jurisdiction of a policy might cover a business function, department, agency, or other organisational area of responsibility not tied to geography.

[SOURCE:ISO/IEC TR 22678:2019, 3.2]

3.6

cloud service developer

sub-role of the cloud service partner role, with the responsibility for designing, developing, testing and maintaining the implementation of software that is either part of a cloud service, or is designed to run on a cloud service

Note 1 to entry: The cloud service developer sub-role can be performed by any party, including CSN, CSP, and CSC.

Note 2 to entry: Normally software that is part of a cloud service will only be developed by a CSD under the control of the CSP. Software that runs on top of a cloud service can be developed by a CSD under the control of a CSC (e.g. for IaaS or PaaS).

Note 3 to entry: This definition supersedes the definition in ISO/IEC 22123-1:2023, 3.3.13.