| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 28174.3-2011 | English | RFQ |
ASK
|
3 days [Need to translate]
|
Unified modeling language (UML) -- Part 3: Object constraint language (OCL)
| Valid |
GB/T 28174.3-2011
|
PDF similar to GB/T 28174.3-2011
Basic data | Standard ID | GB/T 28174.3-2011 (GB/T28174.3-2011) | | Description (Translated English) | Unified modeling language (UML) -- Part 3: Object constraint language (OCL) | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 142,193 | | Date of Issue | 2011-12-30 | | Date of Implementation | 2012-06-01 | | Quoted Standard | GB/T 28174.1; GB/T 28174.2 | | 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 part is a formal language, it applies to the expression described in the UML model. These expressions to regulate the manner described in the same condition specifies how the system should be established in the modeling process, and query objects in the model. | GB/T 28174.3-2011: Unified modeling language (UML) -- Part 3: Object constraint language (OCL)---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 3. Object constraint language (OCL)
ICS 35.080
L77
National Standards of People's Republic of China
Unified Modeling Language (UML)
Part 3. Object Constraint Language (OCL)
Unifiedmodelinglanguage (UML) -
Part 3. Objectconstraintlanguage (OCL)
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
3 Object Constraint Language Description 1
Abstract syntax
5 specific syntax
The semantics described in UML
7 OCL Standard Library
The use of OCL expressions in UML models
9 OCL, UML and MOF three meta-model of the convergence of 136
Foreword
GB/T 28174 "Unified Modeling Language (UML)" 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 3 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. Object Constraint Language (OCL) 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. Guangdong Guangye Information Industry Group Co., Ltd., Guangdong Wanwei Bertone Information Technology Co., Ltd., Zhenjiang gold titanium
Software Co., Ltd., Peking University, China Institute of Electronic Technology Standardization.
This part of the main drafters. Xu Liyong, Zhou Weiqiang, Tang Zehuan, Jiang Shandong, Huang Xiaohe, Yang Sanbao, Ding Li, Wu Jiongxiang, Deng Haiqiang,
Hu Honglin, Gao Jian.
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 (such as. 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 upper structure part (GB/T 28174.2). But note that the part
Of the content is cross-referenced, can not read by the 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 3. Object Constraint Language (OCL)
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 part is a formal language that applies to expressions that describe UML models. These expressions are specified in a regulated manner
How to describe the system in the modeling process should be established in the invariant conditions and the query object in the model.
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
Unified Modeling Language (UML) - Part 2. Upper Architecture
3 Object Constraint Language Description
3.1 The role of OCL
UML diagrams (such as class diagrams) are usually not fine enough to provide all aspects related to the specification. Which is missing in the description model
Add constraints on objects. These constraints are often described in natural language. And practice shows that doing so often causes ambiguity. To write
There is no ambiguity of the constraints, has developed several new "formal language". The traditional form of language, the disadvantage is only suitable for a considerable number
It is difficult to use the background staff, the general business or the system modeler.
OCL is to fill this gap and developed. It is a formal language that retains the easy-to-read and easy-to-write features. It's already in IBM's
The insurance division was developed as a business modeling language and was rooted in the Syntropy method.
OCL is a purely regular language, thus ensuring that OCL expressions do not have side effects. When evaluating an OCL expression,
Just return a value. It can not change anything in the model. This means that the state of the system is never evaluated by the OCL expression
And change, even if the OCL expression can be used to specify a state change (for example, in the postcondition).
OCL is not a programming language, so it is not possible to write program logic or flow control in OCL. Within OCL, you can not enable processes or
Activate non-query operation. OCL is a modeling language, so OCL expressions can not be executed directly by definition.
OCL is a typed language, where each OCL expression has a type. OCL expression to be well, it should be
The type of conformity rule of the language. For example, you can not compare Integer with String. Each category defined within the UML model
(Classifier), all represent a unique OCL type. In addition, OCL also contains a set of supplemental predefined types (this is in Chapter 7)
"OCL standard library").
As a protocol language, all implementation problems are beyond the scope of OCL and can not be expressed in OCL.
The evaluation of OCL expressions is instantaneous. That is to say, the state of each object in the model can not be changed during the evaluation.
3.1.1 OCL use
OCL can be used for several different purposes.
a) as a query language;
b) specify the invariants of classes and types in class models;
c) specify the type of Stereotype (Stereotype) invariant;
|