| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 28174.2-2011 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Unified modeling language (UML) -- Part 2: Superstructure specification
| Valid |
GB/T 28174.2-2011
|
PDF similar to GB/T 28174.2-2011
Basic data | Standard ID | GB/T 28174.2-2011 (GB/T28174.2-2011) | | Description (Translated English) | Unified modeling language (UML) -- Part 2: Superstructure specification | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 367,342 | | Date of Issue | 2011-12-30 | | Date of Implementation | 2012-06-01 | | Quoted Standard | GB/T 28174.1; GB/T 28174.3 | | Regulation (derived from) | National Standard Approval Announcement 2011 No.23 | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China | | Summary | This standard specifies the various types of software systems for visualization, structure and documentation of the Unified Modeling Language, detail. The language can also be used in other fields can be modeled. This section applies to users of the standard language constructs. In strictly follow the foundation GB/T 28174. 1 infrastructure on the part of the standard describes the meta- model for users, which is the standard syntax and semantics. | GB/T 28174.2-2011: Unified modeling language (UML) -- Part 2: Superstructure specification---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Unified modeling language (UML) .Part 2. Super structured specification
ICS 35.080
L77
National Standards of People's Republic of China
Unified Modeling Language (UML)
Part 2. Upper structure
Unifiedmodelinglanguage (UML) -
Part 2. Superstructurespecification
2011-12-30 release
2012-06-01 implementation
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China
China National Standardization Management Committee released
Directory
Preface III
Introduction IV
1 Scope 1
2 normative reference document 1
Category 3
3.1 Overview 1
3.2 kernel - root map (Kernel-theRootDiagram) 2
3.3 kernel - namespace (Kernel-theNamespacesDiagram) 5
3.4 kernel - multiplicity diagram (Kernel-theMultiplicitiesDiagram) 13
3.5 kernel - expression diagram (Kernel-theExpressionsDiagram) 17
3.6 kernel - constraint diagram (Kernel-theConstraintsDiagram) 23
3.7 kernel - the case map (Kernel-theInstancesDiagram) 25
3.8 kernel - class chart (Kernel-theClassifiersDiagram) 28
3.9 kernel - feature map (Kernel-theFeaturesDiagram) 36
3.10 kernel - operation diagram (Kernel-theOperationsDiagram) 39
3.11 kernel - class diagram (Kernel-theClassesDiagram) 42
3.12 kernel - data type diagram (Kernel-theDataTypesDiagram) 54
3.13 kernel - package diagram (Kernel-thePackagesDiagram) 57
3.14 Dependencies 62
3.15 interface (interface) 67
3.16 Association class (AssociationClasses) 71
3.17 Power type (PowerType) 72
3.18 Diagram (Diagram) 79
4 component 81
4.1 Overview 81
4.2 Abstract syntax 81
4.3 Class Description 83
4.4 Figure 91
Combination structure
5.1 Overview 92
5.2 Abstract syntax 93
5.3 Class Description 96
5.4 indicates option 96
5.5 Figure 112
6 Deployment 113
6.1 Overview 113
Abstract syntax
Class 6.3 Description 116
6.4 Figure 126
6.5 graphics path 127
7 action 127
7.1 Overview 127
7.2 Abstract syntax 129
7.3 Class Description 137
7.4 Figure 172
Activity 8
8.1 Overview 172
8.2 Abstract syntax 173
8.3 Class Description 184
CommonBehavior 250
9.1 Overview 250
9.2 Abstract syntax 253
Section 9.3 Description 257
Interactions
10.1 Overview 273
10.2 Abstract syntax 273
Class 10.3 Description 277
10.4 Figure 296
11 state machine 308
11.1 Summary 308
11.2 Abstract Syntax
11.3 Class Description 312
11.4 Figure 349
Usefulness (UseCases) 352
12.1 Overview 352
Exceptional Grammar
12.3 Class Description 353
12.4 Diagrams
Foreword
GB/T 28174 "Unified Modeling Language" is divided into four parts.
- Part 1. Infrastructure;
- Part 2. Upper structure;
Part 3. Object Constraint Language (OCL);
Part 4. Graphic exchange.
This part is part 2 of GB/T 28174.
This part is drafted in accordance with the rules given in GB/T 1.1-2009.
This section refers to the "Unified Modeling Language. Upper Architecture" version 2.0 of the Object-Oriented Working Group (OMG).
Please note that some of the contents of this document may involve patents. The issuer of this document does not assume responsibility for the identification of these patents.
This part of the National Information Technology Standardization Technical Committee (SAC/TC28) proposed and centralized.
This part of the drafting unit. China Electronic Technology Standardization Institute, Peking University, Guangdong Province Guangye Information Industry Group Co., Ltd., Zhenjiang
Metal Titanium Software Co., Ltd., Guangdong Wanwei Bertone Information Technology Co., Ltd.
The main drafters of this part are. Gao Jian, Jiang Shandong, Xu Liyong, Zhou Weijiang, Huang Xiaohe, Ding Li, Yang Sanbao, Wu Jiongxiang, Deng Haiqiang, Hu Honglin,
Tang Zehuan, Ma Zhiyi.
Introduction
Unified Modeling Language (UML) is a visualization protocol language used to define and construct products of computer information systems and
Stalled. It is a generic modeling language that can be used with all the mainstream object-oriented and component-oriented methods and applies to all
Of the application areas and implementation platforms (eg, CORBA, J2EE, .NET, etc.).
0.1 Unified Modeling Language The relationship between different versions
As the new technology of UML, so the international standard after several versions of evolution, the following is the evolution of UML in the OMG process.
1997 UML1.1
1998 UML1.2
1999 UML1.3
2001 UML1.4
2003 UML2.0
GB/T 28174 in this part of the text of the UML are UML2.0 unified modeling language and GB/T 28174.
0.2 advice on the reader
Need to understand the meta-model constructs in the language, use these constructs to extend the meta-model, or construct a new modeling language
The user can read the infrastructure section (GB/T 28174.1).
Application system modeling users and modeling tools manufacturers need to read the superstructure (GB/T 28174.2). But note that the inside of that part
Capacity is cross-referenced, can not read by order of the order.
For an application system that wants to constrain the model precisely to model the user or the modeling tool manufacturer that wants to support the object constraint language,
Reading Object Constraint Language Part (GB/T 28174.3).
The modeling tool manufacturer, which supports smooth and seamless exchange of documents between different software tools, needs to read the interactive parts of the graph.
Unified Modeling Language (UML)
Part 2. Upper structure
1 Scope
This part of GB/T 28174 specifies a unified modeling language for visualizing, detailing, structuring, and documenting various types of software systems.
Words. This language can also be used to model other areas.
This section applies to the language constructs of this standard used by the user. Strictly follows the foundation of the GB/T 28174.1 infrastructure
, This section describes the meta-model of the standard used by the user, that is, the grammar and semantics of this standard.
2 normative reference documents
The following documents are indispensable for the application of this document. For dated references, only the dated edition applies to this article
Pieces. For undated references, the latest edition (including all modifications) applies to this document.
Unified Modeling Language (UML) - Part 1. Infrastructure
GB/T 28174.3 Unified Modeling Language (UML) Part 3. Object Constraint Language (OCL)
Category 3
3.1 Overview
Classe contains subpackages associated with UML basic modeling concepts, especially classes and their relationships.
The structure of the package
Figure 1 depicts the dependencies between packages of Classes (such as merge)
Figure 1 Classes package subpackages and dependencies between them
|