ISO/IEC TR 19583-22:2018 情報技術—メタデータの概念と使用法—パート22：ISO / IEC19763を使用した開発プロセスの登録とマッピング | ページ 2

3.1 用語と定義

このドキュメントの目的のために、ISO/IEC 19763-1, ISO/IEC 19763-5, ISO/IEC 19763-8, ISO/IEC 19763-10 および以下に記載されている用語と定義が適用されます。

ISO および IEC は、次のアドレスで標準化に使用する用語データベースを維持しています。

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, 2 (see www.iso.org/directives ).

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents ).

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL www.iso.org/iso/foreword.html .

This document was prepared by Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 32, Data, management and interchange.

A list of all parts in the ISO/IEC 19583 series can be found on the ISO website.

Introduction

The ISO/IEC 19583 series consists of Technical Reports showing how to implement ISO/IEC 11179 and ISO/IEC 19763.

When a software development project is started the project structure, consisting of processes, activities and tasks, is defined and described in the Project Initiation Document or Project Plan. The project deliverables are also defined in these documents. These documents are then maintained until the project is completed.

The project processes, activities and tasks can be modelled using a process model. A ‘standard project process model’ is defined in ISO/IEC/IEEE 12207 but the process model for each project should be defined and tailored to recognize the distinctive characteristics of that project. These tailored process models, and their associated deliverables, should be preserved so that the processes, activities, tasks and deliverables can be reused or adapted for new projects, enabling these new projects to be managed efficiently and effectively and at low risk.

ISO/IEC/IEEE 12207 establishes a common framework for software development, containing the processes, activities, and tasks that are to be applied during the whole lifecycle of a software product or service. In software development, each organisation establishes its standard processes based on the specification provided by ISO/IEC/IEEE 12207. During project initiation, the project manager defines the processes, activities, and tasks for the project by tailoring the standard processes so that the new project process model recognizes the distinctive characteristics of the project. For future projects with similar characteristics the new project will be more efficiently and effectively managed with higher quality deliverables produced at lower risk if an existing project process model can be easily reused.

1 Scope

This document provides a usage scenario that utilizes the facilities defined in ISO/IEC 11179-3, ISO/IEC 19763-5 and ISO/IEC 19763-10 to demonstrate the registration of the mapping between process models. The availability of these registered process model mappings will help to promote the reuse of process models.

The scope of this document is limited to a discussion of the process models associated with software development projects and the deliverables produced during these projects.

This document describes a scenario that evaluates the combined usage of ISO/IEC 11179-3, ISO/IEC 19763-5 and ISO/IEC 19763-10 to enable the reuse of past knowledge of process models describing project processes and deliverables.

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

3 Terms, definitions and abbreviated terms

3.2 Abbreviated terms

Bibliography