Standard number: GB/T 37944-2019 Standard name: General resource of military and civilian--Compiling requirements for data model Standard format: PDF Release time: 2019-08-30 Implementation time: 2020-03-01 Standard size: 1280K Standard introduction: This standard was drafted in accordance with the rules given in GB/T1.12009 This standard was proposed by the National Technical Committee for Logistics Information Management Standardization (SAC/TC267) and is under the jurisdiction of the drafting units of this standard: Joint Service College of National Defense University of the People's Liberation Army, Academy of Military Sciences of the People's Liberation Army, China Article Coding Center, China Aviation Comprehensive Technology Research Institute, China Electronics Technology Standardization Institute, China National Institute of Standardization, Information Center of the Logistics Support Department of the Central Military Commission, Military Standard Research Center of the Systems Engineering Institute of the Academy of Military Sciences of the People's Liberation Army, and Qingdao Standardization Institute. The main drafters of this standard are Qian Lufeng, Liu Zhi, Li Ying, An Jing, Wang Limeng, Luo Qiuke, Li Sucai, Han Shuwen, Yang Ying, Sun Wenfeng, Ma Wenjing, Yang Xiaojun, Ren Jie, Liu Wen, Wang Haiwei, Yang Jun, Xu Junxia, ​​Chen Jun, Wang Jing, Yang Wenhong, Liu Xinjian, Huang Nan, Zhang Yanqi, Wang Pei, Du Jingrong, Li Yurong, Xing Yanlin, Li Junmei, Xu Ni This standard specifies the composition, description content, methods and requirements of the military-civilian common resource data model. This standard applies to the compilation of the military-civilian common resource data model 2 Normative references The following documents are indispensable for the application of this document. For all referenced documents with dates, only the versions with dates apply to this document. For any undated referenced documents, the latest version (including all amendments) applies to this document GB/T18391.1—2009 Information Technology Metadata Registration System (MDR) Part 1: Framework GB/T37936—2019 Requirements for the Classification and Coding of Military and Civilian General Resource Information GB/T37948—2019 Requirements for the Compilation of Military and Civilian General Resource Data Elements 3 Terms and Definitions The terms and definitions defined in GB/T18391.12009 and the following terms and definitions apply to this document. Primary key A combination of one or more data elements in a data entity, whose value can uniquely identify a record Foreign key In a data entity, a data element that introduces the primary key of another entity to form a relationship between entities 3.3 Composite attribute The same attribute that needs to be described differently in different components or under different conditions of the same military and civilian
common resource This standard specifies the composition, description content, methods and requirements of the military and civilian common resource data model. This standard applies to the compilation of the military and civilian common resource data model.

ICS35.040
National Standard of the People's Republic of China
GB/T37944—2019
General resource of military and civilian-Compiling requirementsfor data model
2019-08-30 Issued
State Administration for Market Regulation
Standardization Administration of China
2020-03-01 Implementation
Normative references
Terms and definitions
Model composition
5 Preparation requirements
Appendix A (Normative Appendix)
Information engineering symbols
Appendix B (Informative Appendix)
Data model example
References
GB/T37944—2019
This standard was drafted in accordance with the rules given in GB/T1.12009. This standard was proposed and managed by the National Technical Committee for Logistics Information Management Standardization (SAC/TC267). GB/T37944—2019
The drafting units of this standard are: Joint Service College of National Defense University of the Chinese People's Liberation Army, Academy of Military Sciences of the Chinese People's Liberation Army, China Article Numbering Center, China Aviation Comprehensive Technology Research Institute, China Electronics Technology Standardization Institute, China National Institute of Standardization, Information Center of the Logistics Support Department of the Central Military Commission, Military Standard Research Center of the Institute of Systems Engineering of the Chinese People's Liberation Army Academy of Military Sciences, Qingdao Institute of Standardization. The main drafters of this standard are: Qian Lufeng, Liu Zhi, Li Ying, An Jing, Wang Limeng, Luo Qiuke, Li Sucai, Han Shuwen, Yang Ying, Sun Wenfeng, Ma Wenjing, Yang Xiaojun, Ren Jie, Liu Wen, Wang Haiwei, Yang Jun, Xu Junxia, ​​Chen Jun, Wang Jing, Yang Wenhong, Liu Xinjian, Huang Nan, Zhang Yanqi, Wang Pei Du Jingrong, Li Yurong, Xing Yanlin, Li Junmei, Xu Ni. 1 Scope
Military and Civilian Common Resources
Data Model Preparation Requirements
This standard specifies the composition, description content, methods and requirements of the military and civilian common resource data model. This standard applies to the compilation of the military and civilian general resource data model Normative reference documents
GB/T37944—2019
The following documents are essential for the application of this document. For any dated referenced document, only the dated version applies to this document. For any undated referenced document, its latest version (including all amendments) applies to this document GB/T18391.1-2009 Information Technology Metadata Registration System (MDR) Part 1: Framework GB/T37936-2019 Requirements for the compilation of military and civilian general resource information classification and coding GB/T37948—2019
Requirements for the compilation of military and civilian general resource data elements
Terms and definitions
The terms and definitions defined in GB/T18391.1-2009 and the following terms and definitions apply to this document. 3.1
primarykey
The combination of one or more data elements in a data entity, whose value can uniquely identify a record. 3.2
Foreign keyforeignkey
In a data entity, a data element that introduces the primary key of another entity to form a relationship between entities. 3.3
Composite attribute
Ecompositeattribute
The same attribute that needs to be described differently in different components or under different conditions of the same military and civilian general resource. Example
Material attribute of a shovel: the material of the shovel head is steel, and the material of the shovel handle is wood. 3.4
Information engineering symbolinformationengineeringnotationThe symbol used to describe entities and entity relationships in the data model. (See Appendix A) 4 Model composition
The data model includes a composition structure diagram, a data model index table, a conceptual data model, a logical data model, a physical data model, a data element index table, a code table index table and a code table. The composition and requirements of the data model are shown in Table 1. 1
GB/T37944—2019
Component elements
Composition structure diagram
Data model index table
Conceptual data model
Logical data model
Physical data model
Data element index table
Code table index table and code table
5 Preparation requirements
Basic requirements
Data model composition and requirements| |tt||If it contains two or more data models and there is a relationship between the data models, it should include
should include
should include
should include
should include
should include
should include
The description of the data model should meet the following requirements: a) It is described in the form of text, tables, entity-relationship diagrams, design diagrams, etc.; Remarks
is used to describe the relationship between data models. For example, see B.1.2 in Appendix B
is used to explain the number, name and wording information of all data models. For example, see B.1.3
is used to describe the conceptual structure of data. For example, see B.1.4.1
is used to describe the logical structure of data. For example, see B.1.4.2 and B.2.2
is used to describe the physical structure of data. See B.1.4.3 for an example.
It is used to give an overview of the data elements used in the data model. See B.1.5 for an example.
The code table index table is used to give an overview of all the code tables used in the model: the code table is used to describe the selectable codes for the data elements in the model. See B.1.6 for an example.
The entity-relationship diagram should be described using information engineering symbols. In the diagram, the foreign key symbol of the entity is displayed, and the primary key symbol of the entity, entity icon, attribute icon, etc. are not displayed. 5.2 Requirements for describing the composition structure diagram
It should be described using a combination of entity-relationship diagrams and text. Requirements for description of data model index table
The data model index table adopts the format of Table 2 and should meet the following requirements:a) Serial number: positive integer, arranged in ascending order;Data model number: 8-digit mixed code, the format is shown in Figure 1, and the major category identifier is shown in GB/T37936b)
2019; The data model number should be unique and assigned by the data model management agency;c
Data model name: Chinese should be used, and may contain internationally used foreign words or abbreviations;Data model description: The purpose, scope of application, etc. of the data model should be accurately stated to distinguish it from other data models.d)
The data model description should be concise.
Data model number
XXXXXXXX
XXXXXXXX
5.4 Conceptual data model description requirements
Table 2 Data model index table
Data model name
XX model
XX model
Sequence code (5-digit number)
Subcategory code (2 letters)
Major category identifier
Figure 1 Data model number format
GB/T37944—2019| |tt||Data model description
Applicable to XXXX
Applicable to ××××
The conceptual data model is described in a combination of graphics and text, including entities, entity relationships, and necessary text descriptions. Requirements for logical data model description
5.5.1 Basic requirements
The logical data model is used to describe the logical structure of military and civilian general resource information, and is described in a combination of entity-relationship diagram, data element-entity relationship table, data element value impact description table, and composite attribute code table. The following requirements should be met: a) A data element-entity relationship table should be compiled; for logical data models with data element values ​​that affect each other, a data element value impact description table should be compiled; b
For logical data models with composite attributes, a composite attribute code table should be compiled; c)
For logical data models containing two or more entities, an entity-relationship diagram should be drawn. 5.5.2 Entity-Relationship Diagram
In the entity-relationship diagram, the type field of the entity data item should be displayed, and the data type of the entity data item in the specific database management system should not be displayed.
5.5.3 Data element-entity relationship table
The data element-entity relationship is described in the format of Table 3 and should meet the following requirements: Data element identifier: should comply with the requirements of GB/T37948-2019; a
Data element name: should use the data element name or abbreviation that complies with the requirements of GB/T37948-2019; b)
Entity name: should be in Chinese and can contain internationally used foreign words or abbreviations; Fill in "A\" to represent that the entity contains the data element; Fill in "B" to represent that the entity contains the data element, and the value of the data element cannot be empty; d
Fill in "X" to represent that the entity contains the data element, and the data element has a mutual influence on the value; Fill in "M" to represent that the entity contains the data element, And the data element has composite attributes; Fill in "-" to indicate that the entity does not contain the data element; e)
If there are too many entities or it is inconvenient to list them in the same table, the data element-entity relationship table can be described in separate tables: If there is a situation where the data element values ​​affect each other, the format of Table 4 should be used for description, and necessary text descriptions should be made; if there are composite attributes, a composite attribute code table should be compiled. 3
GB/T37944—2019
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXX X
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
Data element value impact description table
Data element name
Data element-entity relationship table
Name of entity 1
Name of entity 2
Name of entity N
The data element value impact description is described in the format of Table 4. For examples, see B.1.4.2.3. The following requirements should be met: Serial number: a positive integer, in ascending order; a
Entity name: Fill in the Chinese name of the entity that is affected by the data element value, which should be the same as the corresponding entity name in the data element-entity relationship table:||tt| |Explanation of the impact of data element value selection: The impact of data element value selection in the entity should be accurately described Table 4
Explanation of the impact of data element value selection table
Compound attribute code table
Entity name
The compound attribute code table should comply with the requirements of GB/T37936-2019. Physical data model description requirements
Basic requirements
Explanation of the impact of data element value selection
The physical data model should accurately describe the physical structure of military and civilian general resource information in a specific database management system, mainly including data item name, data type, data length, data table definition, table relationship, primary key, foreign key, integrity constraint, etc. It is described by combining entity-relationship diagram and entity data item definition table. 5.6.2 Entity-relationship diagram
The entity-relationship diagram shall meet the following requirements:
Should include all entities;
The entity shall include all data items, and identify the primary key and foreign key; b)
GB/T37944—2019
Should accurately describe the one-to-one, one-to-many, many-to-one and many-to-many relationships between entities, as well as data integrity constraint relationships:
d) The data type of the data item in the entity in the specific database management system shall be displayed, and the type domain of the data item shall not be displayed. 5.6.3
Entity data item definition table
Entity data item definition shall be described in the format of Table 5 and shall meet the following requirements: a)
Database management system name and version: Fill in the name of the database management system used, and fill in the specific version number: Serial number: Use a positive integer in ascending order; Entity name: Should be the same as the corresponding entity name in the data element-entity relationship table in the logical data model: Data table name: Fill in the data table name corresponding to the entity in the database management system; Data element identifier: The data element identifier corresponding to the data field in the data table; Data element name: Fill in the data element name or abbreviation corresponding to the data element identifier; Field name: Fill in the name of the data table field corresponding to the data item; Storage type: Fill in the data type of the data table field: Storage parameters: Fill in the character length of the field, or the number of significant digits and precision of the value; Remarks: Fill in other content that needs to be explained in the data table field. Table 5 Entity data item definition table
Database management system
Name and version
Data table
Data element index table Description requirements
XXXXX(XX)
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
The data element index table adopts the format of Table 6 and should meet the following requirements: Serial number: positive integer, arranged in ascending order; a
Data element
Storage type
Compound attribute code table: if there is a compound attribute, fill in the corresponding compound attribute code table number; Storage
The data element identifier, data element name, and data element value field should be filled in according to the requirements of GB/T379482019. Table 6 Data element index table
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
Data element name
Composite attribute code table
Value range of data element
GB/T37944—2019
Code table index table and code table description requirements 5.8.1
Code table index table
The code table index table adopts the format of Table 7 and should meet the following requirements: a)
Serial number: Use a positive integer in ascending order; the code table number and code table name should comply with the requirements of GB/T37936-2019; Remarks: Fill in necessary instructions, such as: code table source, etc. Table 7
Code table number
X×××
Code table
The code table should comply with the requirements of GB/T37936
2019
Code table index table
Code table name
X×code table
X×code table
XX code table3. The following requirements should be met: Serial number: positive integer, in ascending order; a
Entity name: fill in the Chinese name of the entity affected by the data element value, which should be the same as the corresponding entity name in the data element-entity relationship table:
Data element value impact description: the impact of the data element value in the entity should be accurately described Table 4
Data element value impact description table
Compound attribute code table
Entity name
Compound attribute code table should comply with the requirements of GB/T37936-2019. Physical data model description requirements
Basic requirements
Data element value impact description
The physical data model should accurately describe the physical structure of military and civilian general resource information in a specific database management system, mainly including data item name, data type, data length, data table definition, table relationship, primary key, foreign key, integrity constraint, etc. It should be described by combining entity-relationship diagram and entity data item definition table. 5.6.2 Entity-relationship diagram
The entity-relationship diagram shall meet the following requirements:
Should include all entities;
The entity shall include all data items, and identify the primary key and foreign key; b)
GB/T37944—2019
Should accurately describe the one-to-one, one-to-many, many-to-one and many-to-many relationships between entities, as well as data integrity constraint relationships:
d) The data type of the data item in the entity in the specific database management system shall be displayed, and the type domain of the data item shall not be displayed. 5.6.3
Entity data item definition table
Entity data item definition shall be described in the format of Table 5 and shall meet the following requirements: a)
Database management system name and version: Fill in the name of the database management system used, and fill in the specific version number: Serial number: Use a positive integer in ascending order; Entity name: Should be the same as the corresponding entity name in the data element-entity relationship table in the logical data model: Data table name: Fill in the data table name corresponding to the entity in the database management system; Data element identifier: The data element identifier corresponding to the data field in the data table; Data element name: Fill in the data element name or abbreviation corresponding to the data element identifier; Field name: Fill in the name of the data table field corresponding to the data item; Storage type: Fill in the data type of the data table field: Storage parameters: Fill in the character length of the field, or the number of significant digits and precision of the value; Remarks: Fill in other content that needs to be explained in the data table field. Table 5 Entity data item definition table
Database management system
Name and version
Data table
Data element index table Description requirements
XXXXX(XX)
Data element identifier
XXXXXXXXXXXwwW.bzxz.Net
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
The data element index table adopts the format of Table 6 and should meet the following requirements: Serial number: positive integer, arranged in ascending order; a
Data element
Storage type
Compound attribute code table: if there is a compound attribute, fill in the corresponding compound attribute code table number; Storage
The data element identifier, data element name, and data element value field should be filled in according to the requirements of GB/T379482019. Table 6 Data element index table
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
Data element name
Composite attribute code table
Value range of data element
GB/T37944—2019
Code table index table and code table description requirements 5.8.1
Code table index table
The code table index table adopts the format of Table 7 and should meet the following requirements: a)
Serial number: Use a positive integer in ascending order; the code table number and code table name should comply with the requirements of GB/T37936-2019; Remarks: Fill in necessary instructions, such as: code table source, etc. Table 7
Code table number
X×××
Code table
The code table should comply with the requirements of GB/T37936
2019
Code table index table
Code table name
X×code table
X×code table
XX code table3. The following requirements should be met: Serial number: positive integer, in ascending order; a
Entity name: fill in the Chinese name of the entity affected by the data element value, which should be the same as the corresponding entity name in the data element-entity relationship table:
Data element value impact description: the impact of the data element value in the entity should be accurately described Table 4
Data element value impact description table
Compound attribute code table
Entity name
Compound attribute code table should comply with the requirements of GB/T37936-2019. Physical data model description requirements
Basic requirements
Data element value impact description
The physical data model should accurately describe the physical structure of military and civilian general resource information in a specific database management system, mainly including data item name, data type, data length, data table definition, table relationship, primary key, foreign key, integrity constraint, etc. It should be described by combining entity-relationship diagram and entity data item definition table. 5.6.2 Entity-relationship diagram
The entity-relationship diagram shall meet the following requirements:
Should include all entities;
The entity shall include all data items, and identify the primary key and foreign key; b)
GB/T37944—2019
Should accurately describe the one-to-one, one-to-many, many-to-one and many-to-many relationships between entities, as well as data integrity constraint relationships:
d) The data type of the data item in the entity in the specific database management system shall be displayed, and the type domain of the data item shall not be displayed. 5.6.3
Entity data item definition table
Entity data item definition shall be described in the format of Table 5 and shall meet the following requirements: a)
Database management system name and version: Fill in the name of the database management system used, and fill in the specific version number: Serial number: Use a positive integer in ascending order; Entity name: Should be the same as the corresponding entity name in the data element-entity relationship table in the logical data model: Data table name: Fill in the data table name corresponding to the entity in the database management system; Data element identifier: The data element identifier corresponding to the data field in the data table; Data element name: Fill in the data element name or abbreviation corresponding to the data element identifier; Field name: Fill in the name of the data table field corresponding to the data item; Storage type: Fill in the data type of the data table field: Storage parameters: Fill in the character length of the field, or the number of significant digits and precision of the value; Remarks: Fill in other content that needs to be explained in the data table field. Table 5 Entity data item definition table
Database management system
Name and version
Data table
Data element index table Description requirements
XXXXX(XX)
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
XXXXXXXXXXX
The data element index table adopts the format of Table 6 and should meet the following requirements: Serial number: positive integer, arranged in ascending order; a
Data element
Storage type
Compound attribute code table: if there is a compound attribute, fill in the corresponding compound attribute code table number; Storage
The data element identifier, data element name, and data element value field should be filled in according to the requirements of GB/T379482019. Table 6 Data element index table
Data element identifier
XXXXXXXXXXX
XXXXXXXXXXX
Data element name
Composite attribute code table
Value range of data element
GB/T37944—2019
Code table index table and code table description requirements 5.8.1
Code table index table
The code table index table adopts the format of Table 7 and should meet the following requirements: a)
Serial number: Use a positive integer in ascending order; the code table number and code table name should comply with the requirements of GB/T37936-2019; Remarks: Fill in necessary instructions, such as: code table source, etc. Table 7
Code table number
X×××
Code table
The code table should comply with the requirements of GB/T37936
2019
Code table index table
Code table name
X×code table
X×code table
XX code table
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.