Data specification for disclosure of technical indicators in standard literature
Some standard content:
ICS 01.140.10 ;01.075
National Standard of the People's Republic of China
GB/T398722021
Data specification for disclosure of technical indicators in standard literature2021-03-09Issued
State Administration for Market Regulation
National Administration of Standardization
Issued
2021-10-01Implementation
-riKacerKAca-
Scope
Normative references
3 Terms and definitions
Description method of child data
A.!
Abstract
4.1.1
Overview
4.1.2
4.1.3
4.1.4
1.1.5
4.1.6
4.1.7
4.1.8
4.1.9
Chinese Name
Definition
English Name
Data Type
Range
Short Name
Constraints/Conditions
Most Occurrence
UML Diagrams
4.2.1
1.2.2
4.2.3
1.2.4
Overview
I.ML. Representation of Metadata, Metadata Entities and Metadata ElementsUML Model Notation
UMI. Model Relationship
Data Dictionary
1.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
Overview
Chinese Name/Color Name
English Name
Short Name and domain code
Definition
Constraints/conditions
Maximum number of occurrences
Data type
Domain/estimation domain
5 Standard document technical indicators Abstract representation of metadata Standard document technical indicators Abstract representation of core metadata 5.1
5.1.1
Subject category
-rrKaeerkca-
GB/T 39872—2021
GB/T39872—2021
Ontology class/disclosure vocabulary
5.1.2
5.1.3
5.1.4
5.1.5
Example structure
Disclosure content
Unit of measurement
5.1.6 Notes
5.1. 7
Professional field code table
5.2 Technical indicators of standard documents disclosure public metadata abstract representation 5.2.1
5.2.2
5.2.3
Subject object
Ontology class/disclosure vocabulary
Example structure
Disclosure content
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
5.2.10
5.2.11
5.2.12
5.2.13
5.2.11
5.2.15
5.2.16
5.2.17
5 .2.18
5.2.19
Units of measurement
Notes
Professional field code table
Issuing agency code table
Documents
Standard documents
Technical regulations
System table
System standards
System regulations
Category table
Chinese standard document classification method
International Standard Classification
Professional Classification
Product Code Table
6 Standard Document Technical Indicator Metadata UML Description ·6.1
Metadata Overview
Metadata Core Metadata
Metadata Content
6.4 Source Metadata
Classification Data
7 Standard Document Technical Indicator Metadata Data Dictionary Subject Object ·
Ontology Class/Metadata Vocabulary
Structure:
Metadata Content
-rrKaeerKAca-
7.10
7.11
Units of Measurement
Notes
Professional Field Code Table
Issuing Agency Code Table
Document|| tt||Standard Documents
Technical Regulations
7.12
7.13
7.14
7.15
7.16
7.17
7.18
System Table
System Standards
System Regulations
Category Table
Chinese Standard Document Classification
International Standard Classification
Professional Classification
7.19
Product Code Table
Appendix A (Normative Appendix)
Appendix B (Informative Appendix)
References·
Code Table
Example of the Core Metadata Form Revealed by Technical Indicators of Standard Documents -rrKaeerKa-
GB/T 39872—2021
：66
-riKacerKAca-bZxz.net
Foreword
This standard was drafted in accordance with the rules given in GB/T1.12009. The standard was proposed by the Ministry of Science and Technology of the People's Republic of China. This standard is under the jurisdiction of the National Technical Committee for Standardization of Science and Technology Platform (SAC/TC486). GB/T39872—2021
The drafting units of this standard are: China National Institute of Standardization, National Science and Technology Infrastructure Platform Center, National Standard Technical Review Center of the State Administration for Market Regulation, China National Petroleum Corporation Pipeline Branch, Beijing Lu Kesen Information Technology Co., Ltd. The main drafters of this standard are: Zhou Jie, Li Aixian, Chen Weiqing, Wang Bin, Cheng Nufan, Gong Ningping, Gong Liying, Li Jing, Bao Li, Liu Chaochen, Ma Zhiyuan, Ding Jie, Xu Huili, Liu Bing, and Liu Gang. rrKaeerkAca-
-riKacerKAca-
1 Scope
Standard document technical indicator disclosure data specification This standard specifies the standard document technical indicator disclosure metadata. This standard is applicable to the processing, database construction, publication and query of various standard document technical indicator disclosure small data sets. 2 Normative reference documents
GB/T 39872—2021
The following documents are essential for the application of this document. For any document with a specified period, only the version with the specified period is applicable to this document. For any un-dated referenced documents, the latest version (including all amendments) applies to this document GB/T2260 Administrative region code of the People's Republic of China GB/T2659 Code for names of countries and regions in the world 2005 Data elements and exchange formats
GB/T 7408
Information exchange
Date and time representation
GB/T310752014 Science and technology platform general terminology Chinese standard document classification
International standard classification
3 Terms and definitions
G3/T310752
2011 and the following terms and definitions apply to this document. For ease of use, the following lists some of the terms and definitions in GB/T 31075-2014. 3.1
Dataset
Dataset
It has a certain subject, can be identified and can be processed by a computer [(B/T 31075-2011, definition A.2.16 3.2
Dataset series
Idatasel series
The combination of multiple data sets on the same subject conforms to the same product specification. 3.3
Metadata
Metadata
Defines and describes other data.
L GB/T 18391.1—2009. Definition 3.2.16 3.4
metadata element
metadata element
The basic unit of metadata.
Note 1: What is the identity of metadata elements in metadata entities. Note 2: Synonymous with attributes in UML. Technical access, [(3/T 19710—2005, definition 4.6
-rKaeerkAca-
GB/T 39872—2021
metadata entity
Metadata entity
One red metadata element describing the same characteristics of the data. Note 1: Synonymous with \class\ in UML terminology. Note 2: Can contain one or more metadata. Entity! LGB/T19710-2005. Definition 4.7 "
metadata section
metadata subset
A subset of metadata. It consists of similar metadata entities and elements. Note: \UMI. Synonyms for "package" in terminology, [(3/T 19710-2005, definition 4.8
core metadata
core metadata
metadata that describes the most basic information of resources Minimum set of data. 3.8
Public metadata
common metadata
Protection metadata batch revealed by standard document technical indicators. 3.9
Bibliography||tt| | description | Technical method to effectively display standardized objects and their characteristic attributes and characteristic parameters. 4 Metadata description method
4.1 Summary representation
4.1.1 Overview
Use the following attributes to metadata, A summary description of the content of metadata entities and metadata elements. Chinese name
4.1.2
Chinese description of the content and attributes of metadata, metadata entities and metadata elements: 4.1.3 Definition
The basic content and properties of metadata, metadata entities and metadata elements. 4.1.4 English name
The English name of metadata, metadata entities and metadata elements. The English name is usually the full English name. The English name of the metadata element is written in a seamless continuation of the full names of all the constituent words. Except for the first word, all the other words are written in lowercase by Bai Ning's mother, 2||tt | |-rrKaeerkAca-
4.1.5 data type
GB/T 39872—2021
The valid value range of data and the ship that allows effective operations on the values ??in the value range Defined. For example, integer type, real type, Boolean type, ! period, etc.
4.1.6 Value range
For metadata entities, the value range indicates the number of rows it contains. For data, the value range indicates its valid values ??or "white meaning" indicates that there is no restriction on the content of the field. Integer-based codes should be used to represent the field values ????including the code table. 4.1.7 Short name
The English abbreviated name of a metadata entity or metadata element. Naming rules:
-The short name should be unique within the scope of this standard;
uses an international award-winning English name as the short name: if the English name of the data entity or data element does not exceed 8 English names The character. short name directly adopts the English name; for a data entity or data element with more than 8 characters in English, if the English name consists of a single word, the abbreviation of each syllable of the word is used as the English short name: if there are multiple words Composed, take the one-syllable abbreviation of each word as the short name.
4.1.8 Constraints/Conditions
Attributes selected by metadata entities or metadata elements, including required items (M), optional items (O)) and conditional required items (C), constraints/ See Table 1 for condition codes.
Table 1 Constraint/Condition Code
Code
Name
Required
Optional
Condition required
4.1.9 The maximum number of occurrences
indicates that the metadata entity or metadata element should be selected.
can be selected or not selected according to the actual application. The optional data entities and optional metadata elements that have been defined can guide domain data standard developers to fully describe their data. Optional data entities can have mandatory metadata elements; but these elements are only used when the optional elements are selected. It becomes a must-select. If an optional data entity is not selected, the elements contained by the entity (including required elements) are also not selected. The conditions for selecting the data entity or element are met. When the conditions are met, at least one data entity or element is selected. The data element must be selected. "Condition must be selected" (one of the following possibilities) indicates a selection among 2 or more metadata entities or metadata elements. There is at least one data entity or data element that must be selected,
1) When data entities or data elements have been selected, this data entity or data element is required, e) Another data element has been selected Is this data element a required metadata entity or the maximum number of instances a metadata element can have when a specific value is reached? Those that appear only once are represented by "1", and those that appear repeatedly are represented by "N" 3
-rrKaeerkAca-
GB/T39872—2021
. Fixed occurrences that are not \1\ The number of times is represented by a number, such as \2\\3", etc. 4.2UML Figure
4.2.1 Overview
Use Unified Modeling Voice (LML) to metadata entities and child data elements Trace description of grammatical features. Use class and attribute table data entities and data elements in UML respectively, and use UML model diagrams to describe the relationship between data entities and metadata elements:
4.2.2 Metadata, metadata entities and metadata elements The UML representation uses "package" in UML to represent metadata sets, uses the concept of "class" to represent metadata entities, and uses the attributes of "class" in IMI to represent metadata elements.
4.2.3UML model symbol
UML model symbol is shown in Figure 1.
Annotation
Association
Aggregation
Composition
Generalization
Dependency
Stereotype
4.2 .4UML model relationship
4.2.4.1 Association
Class 1
Class 1
Class
Class 1
Figure 1 UML model symbol | |tt||Class 2
Class 2
Class 2
→ Class 2
Class 2
The United States is used to describe two or more people Relationships between classes. It is a kind of beauty system that allows one class to know another. The
attributes and methods
of this class are represented by a straight line. If the direction of the association is not specified, it is a two-way association. , if it is a one-way association, use an arrow at the end of the line segment to mark the connection direction,
4.2.4.2 Aggregation
Aggregation is a strong association, and Ding is used to describe the relationship between two classes. The relationship between whole and part (possession). At this time, the relationship between the whole and the part is called separation. They have their own life cycles. Parts can belong to multiple whole objects or can be shared by multiple whole objects. A
-rKaeerkca-8
Core metadata
core metadata
The minimum set of metadata that describes the most basic information of resources. 3.8
public metadata
common metadata
implements the protection metadata batch revealed by standard document technical indicators. 3.9
Description
description
The process of analyzing, selecting and recording the content and formal characteristics of the standard, 3.10
Revelation
disclosure|| tt ||In-depth refinement and effective display of technical methods for standardized objects and their characteristic attributes and characteristic parameters from technical standards. 4 Metadata description method
4.1 Summary representation
4.1.1 Overview
Use the following attributes to summarize the contents of metadata, metadata entities and metadata systems. Chinese Name
4.1.2
Chinese description of the content and attributes of child data, child data entities and child data elements: 4.1.3 Definition
Cat description metadata, metadata entities and Basic content and properties of metadata elements 4.1.4 English names
English names of metadata, metadata entities and metadata elements. The English name of the metadata is usually the full English name. The English name of the metadata element is written in a seamless concatenation of the full names of all the constituent words. Except for the first word, all other words are written in lowercase letters, 2
-rrKaeerkAca-
4.1.5 Data type
GB/T 39872—2021
The valid value range and permission of data within this value range are valid The operation of the ship is determined. For example, integer type, real type, Boolean type, character type,! Period etc.
4.1.6 Value range
For metadata entities, the value range indicates the number of rows it contains. For data, the value range indicates its valid values ??or uses white definitions. Book. "Baiyiben" indicates that there are no restrictions on the content of the field. Field values ??containing code tables should be represented using integer-based codes. 4.1.7 Short name
The English abbreviated name of a metadata entity or metadata element. Naming rules:
-The short name should be unique within the scope of this standard;
uses an international award-winning English name as the short name: if the English name of the data entity or data element does not exceed 8 English names The character. short name directly adopts the English name; for a data entity or data element with more than 8 characters in English, if the English name consists of a single word, the abbreviation of each syllable of the word is used as the English short name: if there are multiple words Composed, take the one-syllable abbreviation of each word as the short name.
4.1.8 Constraints/Conditions
Attributes selected by metadata entities or metadata elements, including required items (M), optional items (O)) and conditional required items (C), constraints/ See Table 1 for condition codes.
Table 1 Constraint/Condition Code
Code
Name
Required
Optional
Condition required
4.1.9 The maximum number of occurrences
indicates that the metadata entity or metadata element should be selected.
can be selected or not selected according to the actual application. The optional data entities and optional metadata elements that have been defined can guide domain data standard developers to fully describe their data. Optional data entities can have required metadata; but these elements are only used when the optional elements are selected. It becomes a must-select. If an optional data entity is not selected, the elements included in the entity (including required elements) are also not selected. The conditions for selecting the data entity or element are met. When the conditions are met, at least one data entity or element is selected. The data element must be selected. "Condition must be selected" (one of the following possibilities) indicates a selection among 2 or more metadata entities or metadata elements. There is at least one data entity or data element that must be selected,
1) When data entities or data elements have been selected, this data entity or data element is required, e) Another data element has been selected When a specific value is reached, is this data element a required metadata entity or is the maximum number of instances that a metadata element can have? Those that appear only once are represented by "1", and those that appear repeatedly are represented by "N" 3
-rrKaeerkAca-
GB/T39872—2021
. Fixed occurrences that are not \1\ The number of times is represented by a number, such as \2\\3", etc. 4.2UML Figure
4.2.1 Overview
Use Unified Modeling Voice (LML) to metadata entities and child data elements Trace description of grammatical features. Use class and attribute table data entities and data elements in UML respectively, and use UML model diagrams to describe the relationship between data entities and metadata elements:
4.2.2 Metadata, metadata entities and metadata elements The UML representation uses "package" in UML to represent metadata sets, uses the concept of "class" to represent metadata entities, and uses the attributes of "class" in IMI to represent metadata elements.
4.2.3UML model symbol
UML model symbol is shown in Figure 1.
Annotation
Association
Aggregation
Composition
Generalization
Dependency
Stereotype
4.2 .4UML model relationship
4.2.4.1 Association
Class 1
Class 1
Class
Class 1
Figure 1 UML model symbol | |tt||Class 2
Class 2
Class 2
→ Class 2
Class 2
The United States is used to describe two or more people Relationships between classes. It is a kind of beauty system that allows one class to know another. The
attributes and methods
of this class are represented by a straight line. If the direction of the association is not specified, it is a two-way association. , if it is a one-way association, use an arrow at the end of the line segment to mark the connection direction,
4.2.4.2 Aggregation
Aggregation is a strong association, and Ding is used to describe the relationship between two classes. The relationship between whole and part (possession). At this time, the relationship between the whole and the part is called separation. They have their own life cycles. Parts can belong to multiple whole objects or can be shared by multiple whole objects. A
-rKaeerkca-8
Core metadata
core metadata
The minimum set of metadata that describes the most basic information of resources. 3.8
public metadata
common metadata
implements the protection metadata batch revealed by standard document technical indicators. 3.9
Description
description
The process of analyzing, selecting and recording the content and formal characteristics of the standard, 3.10
Revelation
disclosure|| tt ||In-depth refinement and effective display of technical methods for standardized objects and their characteristic attributes and characteristic parameters from technical standards. 4 Metadata description method
4.1 Summary representation
4.1.1 Overview
Use the following attributes to summarize the contents of metadata, metadata entities and metadata systems. Chinese Name
4.1.2
Chinese description of the content and attributes of child data, child data entities and child data elements: 4.1.3 Definition
Cat description metadata, metadata entities and Basic content and properties of metadata elements 4.1.4 English names
English names of metadata, metadata entities and metadata elements. The English name of the metadata is usually the full English name. The English name of the metadata element is written in a seamless concatenation of the full names of all the constituent words. Except for the first word, all other words are written in lowercase. 2
-rrKaeerkAca-
4.1.5 Data type
GB/T 39872—2021
The valid value range and permission of data within this value range are valid The operation of the ship is determined. For example, integer type, real type, Boolean type, character type,! Period etc.
4.1.6 Value range
For metadata entities, the value range indicates the number of rows it contains. For data, the value range indicates its valid values ??or uses white definitions. Book. "Baiyiben" indicates that there are no restrictions on the content of the field. Field values ??containing code tables should be represented using integer-based codes. 4.1.7 Short name
The English abbreviated name of a metadata entity or metadata element. Naming rules:
-The short name should be unique within the scope of this standard;
uses an international award-winning English name as the short name: if the English name of the data entity or data element does not exceed 8 English names The character. short name directly uses the English name; for a data entity or data element with more than 8 characters in English, if the English name consists of a single word, the abbreviation of each syllable of the word will be used as the English short name: if there are multiple words Composed, take the one-syllable abbreviation of each word as the short name.
4.1.8 Constraints/Conditions
Attributes selected by metadata entities or metadata elements, including required items (M), optional items (O)) and conditional required items (C), constraints/ See Table 1 for condition codes.
Table 1 Constraint/Condition Code
Code
Name
Required
Optional
Condition required
4.1.9 The maximum number of occurrences
indicates that the metadata entity or metadata element should be selected.
can be selected or not selected according to the actual application. The optional data entities and optional metadata elements that have been defined can guide domain data standard developers to fully describe their data. Optional data entities can have mandatory metadata elements; but these elements are only used when the optional elements are selected. It becomes a must-select. If an optional data entity is not selected, the elements contained by the entity (including required elements) are also not selected. The conditions for selecting the data entity or element are met. When the conditions are met, at least one data entity or element is selected. The data element must be selected. "Condition must be selected" (one of the following possibilities) indicates a selection among 2 or more metadata entities or metadata elements. There is at least one data entity or data element that must be selected,
1) When data entities or data elements have been selected, this data entity or data element is required, e) Another data element has been selected When a specific value is reached, is this data element a required metadata entity or is the maximum number of instances that a metadata element can have? Those that appear only once are represented by "1", and those that appear repeatedly are represented by "N" 3
-rrKaeerkAca-
GB/T39872—2021
. Fixed occurrences that are not \1\ The number of times is represented by a number, such as \2\\3", etc. 4.2UML Figure
4.2.1 Overview
Use Unified Modeling Voice (LML) to metadata entities and child data elements Trace description of grammatical features. Use class and attribute table data entities and data elements in UML respectively, and use UML model diagrams to describe the relationship between data entities and metadata elements:
4.2.2 Metadata, metadata entities and metadata elements The UML representation uses "package" in UML to represent metadata sets, uses the concept of "class" to represent metadata entities, and uses the attributes of "class" in IMI to represent metadata elements.
4.2.3UML model symbol
UML model symbol is shown in Figure 1.
Annotation
Association
Aggregation
Composition
Generalization
Dependency
Stereotype
4.2 .4UML model relationship
4.2.4.1 Association
Class 1
Class 1
Class
Class 1
Figure 1UML model symbol| |tt||Class 2
Class 2
Class 2
→Class 2
Class 2
The United States is used to describe two or more Relationships between classes. It is a kind of beauty system that allows one class to know another. The
attributes and methods
of this class are represented by a straight line. If the direction of the association is not specified, it is a two-way association. , if it is a one-way association, use an arrow at the end of the line segment to mark the connection direction,
4.2.4.2 Aggregation
Aggregation is a strong association, and Ding is used to describe the relationship between two classes. The relationship between whole and part (possession). At this time, the relationship between the whole and the part is called separation. They have their own life cycles. Parts can belong to multiple whole objects or can be shared by multiple whole objects. A
-rKaeerkca-The short name directly adopts the English name; for data entities or data elements with more than 8 English characters, if the English name consists of a single word, the abbreviation of each syllable of the word is taken as the English short name; if it consists of multiple words, the abbreviation of one syllable of each word is taken as the short name.
4.1.8 Constraints/Conditions
The attributes selected by metadata entities or metadata elements, including mandatory (M), optional (O) and mandatory conditions (C), and constraint/condition codes are shown in Table 1.
Table 1 Constraint/Condition Codes
Code
Name
Required
Optional
Condition Mandatory
4.1.9 Maximum Occurrences
Indicates that the metadata entity or metadata element should be selected. Description
Data entity or data element that can be selected or not according to actual application. The defined optional data entities and optional metadata elements can guide domain data standard developers to fully describe their data. Optional data entities can have mandatory elements; but these elements become mandatory only when the optional entities are selected. If an optional data entity is not selected, the elements contained in the entity (including mandatory elements) are also not selected. The condition for selecting the data entity or element. When the condition is met, at least the data entity or data element is mandatory. "Conditional mandatory" means choosing from two or more metadata entities or metadata elements. At least one data entity or data element is mandatory.
1) When a data entity or data element has been selected, this data entity or data element is mandatory. e) When another data element has selected a specific value, this data element is mandatory. The maximum number of instances a metadata entity or metadata element can have? The ones that appear only once are represented by "1", and the ones that appear repeatedly are represented by "N" 3
-rrKaeerkAca-
GB/T39872—2021
. The fixed number of occurrences other than \1\ is represented by a compound number, such as \2\\3", etc. 4.2UML diagram
4.2.1 Overview
Use the Unified Modeling Language (LML) to describe the grammatical features of metadata entities and data elements. Use the classes and attributes in UML to represent data entities and data elements respectively, and use UML model diagrams to describe the relationship between data entities and metadata elements:
4.2.2 UML representation of metadata, metadata entities and metadata elements Use the "package" in UML to represent metadata collections, the concept of "class" to represent metadata entities, and the attributes of "class" in IMI to represent metadata elements.
4.2.3UML model symbols
See Figure 1 for the UML model symbols.
Annotation
Association
Aggregation
Composition
Generalization
Dependency
Stereotype
4.2.4 UML model relationship
4.2.4.1 Association
Class 1
Class 1
Class
Class 1
Figure 1 UML model symbol
Class 2
Class 2
→Class 2
Class 2
Association is used to describe the relationship between two or more classes. It is a kind of ownership relationship, which makes one class know the properties and methods of another class. The association is represented by a straight line. If the direction of the association is not specified, it is a bidirectional association. If it is a unidirectional association, an arrow is used at the end of the line to mark the direction of the association. 4.2.4.2 Aggregation Aggregation is a strong association relationship, which is used to describe the relationship between the whole and the part (ownership) between two classes. At this time, the whole and the part are separated. They have their own life cycles. The part can belong to multiple whole objects or be shared by multiple whole objects.The short name directly adopts the English name; for data entities or data elements with more than 8 English characters, if the English name consists of a single word, the abbreviation of each syllable of the word is taken as the English short name; if it consists of multiple words, the abbreviation of one syllable of each word is taken as the short name.
4.1.8 Constraints/Conditions
The attributes selected by metadata entities or metadata elements, including mandatory (M), optional (O) and mandatory conditions (C), and constraint/condition codes are shown in Table 1.
Table 1 Constraint/Condition Codes
Code
Name
Required
Optional
Condition Mandatory
4.1.9 Maximum Occurrences
Indicates that the metadata entity or metadata element should be selected. Description
Data entity or data element that can be selected or not according to actual application. The defined optional data entities and optional metadata elements can guide domain data standard developers to fully describe their data. Optional data entities can have mandatory elements; but these elements become mandatory only when the optional entities are selected. If an optional data entity is not selected, the elements contained in the entity (including mandatory elements) are also not selected. The condition for selecting the data entity or element. When the condition is met, at least the data entity or data element is mandatory. "Conditional mandatory" means choosing from two or more metadata entities or metadata elements. At least one data entity or data element is mandatory.
1) When a data entity or data element has been selected, this data entity or data element is mandatory. e) When another data element has selected a specific value, this data element is mandatory. The maximum number of instances a metadata entity or metadata element can have? The ones that appear only once are represented by "1", and the ones that appear repeatedly are represented by "N" 3
-rrKaeerkAca-
GB/T39872—2021
. The fixed number of occurrences other than \1\ is represented by a compound number, such as \2\\3", etc. 4.2UML diagram
4.2.1 Overview
Use the Unified Modeling Language (LML) to describe the grammatical features of metadata entities and data elements. Use the classes and attributes in UML to represent data entities and data elements respectively, and use UML model diagrams to describe the relationship between data entities and metadata elements:
4.2.2 UML representation of metadata, metadata entities and metadata elements Use the "package" in UML to represent metadata collections, the concept of "class" to represent metadata entities, and the attributes of "class" in IMI to represent metadata elements.
4.2.3UML model symbols
See Figure 1 for the UML model symbols.
Annotation
Association
Aggregation
Composition
Generalization
Dependency
Stereotype
4.2.4 UML model relationship
4.2.4.1 Association
Class 1
Class 1
Class
Class 1
Figure 1 UML model symbol
Class 2
Class 2
→Class 2
Class 2
Association is used to describe the relationship between two or more classes. It is a kind of ownership relationship, which makes one class know the properties and methods of another class. The association is represented by a straight line. If the direction of the association is not specified, it is a bidirectional association. If it is a unidirectional association, an arrow is used at the end of the line to mark the direction of the association. 4.2.4.2 Aggregation Aggregation is a strong association relationship, which is used to describe the relationship between the whole and the part (ownership) between two classes. At this time, the whole and the part are separated. They have their own life cycles. The part can belong to multiple whole objects or be shared by multiple whole objects.
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.