GB/Z 18219-2008Information technology - Reference model of data management (English PDF)

Foreword

This Guidance Document is equivalent to the International Standard ISO /IEC TR10032.:2003 "Information Technology Data Management Reference Model". This Guidance Document replaces GB/T 18219-2000.

This Guidance Document has no technical changes on the basis of the previous version, only the inaccurate terms and expressions of the previous version of the translation To modify; the standard nature of the standard by the recommendation of the guidance of technical documents.

Appendix A and Appendix B of this guidance document are informative appendices.

The guidance of technical documents proposed by the People's Republic of China Ministry of Information Industry.

The guidance of technical documents by the China Electronics Standardization Institute.

Introduction

When defining a reference model for data management, we see that different data management system implementers use different terms Or refer to similar data management functions, and the same terms are often used to describe different functions. Obviously we have to make the data pipe Management function standardization. This guidance document serves as the role of a reference model for data management and defines this The scope of the model.

This guidance document defines a data management reference model. It provides one when considering both existing and emerging standards A common basis for coordinating standards for data management purposes.

The term "data management" includes describing, creating, modifying, using, and controlling data in information systems. This data management function can be done Executed for the public service of information system application. Or, each application can define and control the data associated with it. In data management function Can be implemented as a public service, it is preferable to provide standardized facilities for data access and control in order to achieve several user pairs Data sharing. Such standardization needs to decide on interfaces to facilitate the development of the relevant standards.

The goal of this guidance document is to provide a framework within the framework of Chapter 1 that can be used for.

a) Interface identification

b) locate all interrelated interfaces;

c) identify the facilities provided on each interface;

d) identify the processes that support each interface, and identify the data needed for such support, as appropriate;

e) use of interface in positioning information system life cycle;

f) Identify the binding options associated with each appropriately identified interface.

There are three main objectives of this guidance document that apply to the standardization of data management.

a) resource sharing ability

b) minimize the cost of supporting an information system life cycle;

c) optimize the use of standardized results.

The goal of resource-sharing capabilities applies not only to the data-represented information resources in the database, but also to the ones described in Chapter 6 Processor resources. We particularly emphasize the sharing of information resources in different locations and information resources developed by different hardware and software. Resource Sharing The ability ultimately comes down to access control.

The goal of minimizing the cost of supporting an information system applies to all phases of the information system life cycle, including design, Hair, operation and maintenance costs.

The goal of optimizing the use of standardized outcomes is to reduce the number of criteria needed and to simplify the content of those standards.

This guidance document defines a scope for the development or improvement of standards and provides for a system that maintains the consistency of all relevant standards Common Framework.

This guidance document provides a framework that enables expert groups to develop their own standards when it comes to developing standards for various parts of the information system Efficient and effective work.

This Guidance Document has sufficient scope to adapt to technological developments and formulate new standards accordingly.

The data management reference model given in this technical paper is described as follows.

--- Chapter 4 describes the data management and information system-based needs;

Chapter 5 explains the data concepts needed in the reference model and how they are related, and also describes the concepts of processes.

--- Chapter 6 provides an architectural model, which can be placed in different data management and data processing components;

--- Chapter 7 describes the goals and principles of data management standardization;

--- Appendix A is a list of related standards;

--- Appendix B shows how existing and future standards are related to the architecture model described in Chapter 6.

This guidance document defines the service classes provided by data management. It also provides a framework for describing the relationships between these classes the way. However, data management does not exist on its own, but rather as described in Chapter 4 in a provision of other services (eg Data storage and data communication) environment.

Appendix A lists the relevant data management standards; Appendix B describes the data management reference model of the architecture and existing and is Set the database standard relations. Information Technology Data Management Reference Model

1 Scope

This guidance document defines a data management reference model. It establishes a framework for coordinating the management of information systems Long-term data and the development of existing and future standards. The existing data management standards in Appendix A.

This guidance document defines common terminology and concepts for all data held in an information system. These concepts are used even more Specifically define the services provided by special data management components (such as database management system or data dictionary system). These related services The interface defined by Yi can be the subject of standardization in the future.

This guidance does not provide data management services and protocols. This document is neither a normative norms of various systems To achieve compliance with the basis.

Some of the processes included in the scope of this guidance document are not compatible with the requirements for handling persistent data and its specific information systems Some process related to the interaction. This includes public data management services such as defining, storing, retrieving, updating, maintaining, backing up, restoring, and communicating Application and dictionary data and the services required to communicate with them.

The scope of this guidance document is based on data management standards that reside on one or more computer systems, including distributed data Library management services.

The scope of this guidance document does not include public services commonly provided by operating systems, such as those associated with a particular type of physical storage Specific technology for storing data, and communication and the specifics of the display unit.

Data management standards define the services provided on the interface. How to achieve the process is not limited.

2 Terms and definitions

The following terms and definitions apply to this guidance document.