|
US$1409.00 · In stock
Delivery: <= 10 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 32392.2-2015: Information technology -- Metamodel framework for interoperability (MFI) -- Part 2: Core model
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 32392.2-2015 | English | 1409 |
Add to Cart
|
10 days [Need to translate]
|
Information technology -- Metamodel framework for interoperability (MFI) -- Part 2: Core model
| Valid |
GB/T 32392.2-2015
|
PDF similar to GB/T 32392.2-2015
Basic data | Standard ID | GB/T 32392.2-2015 (GB/T32392.2-2015) | | Description (Translated English) | Information technology -- Metamodel framework for interoperability (MFI) -- Part 2: Core model | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L72 | | Classification of International Standard | 35.040 | | Word Count Estimation | 67,621 | | Date of Issue | 2015-12-31 | | Date of Implementation | 2017-01-01 | | Regulation (derived from) | State Standard Announcement 2015 No.43 | | 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 | GB/T 32392.2-2015: Information technology -- Metamodel framework for interoperability (MFI) -- Part 2: Core model
---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.
Information technology - Metamodel framework for interoperability (MFI) - Part 2. Core model
ICS 35.040
L72
National Standards of People's Republic of China
IT metamodel interoperability framework (MFI)
Part 2. Core model
Informationtechnology-Metamodelframeworkforinteroperability (MFI) -
Part 2. Coremodel
Issued on. 2015-12-31
2017-01-01 implementation
Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
Standardization Administration of China released
Table of Contents
Introduction Ⅴ
Introduction Ⅵ
1 Scope 1
2 Normative references 1
3 Terms, Definitions and Abbreviations 1
3.1 UML and MOF terminology used in Part 1
3.2 generic term used part 8
3.3 Acronyms 11
4 metamodel interoperability framework (MFI) core specification 12
4.1 Overview 12
4.2 Registration System package (registration system structure) 16
4.3 target package (Construction Sign target) 19
4.4 Relations package (related Sign target) 23
5 Compliance 24
5.1 Summary 24
5.2 Compliance level 24
5.3 Compliance level 25
25 5.4 Commitment
5.5 to achieve compliance statement 25
5.6 Register roles and responsibilities 25
Appendix A (normative) to follow the MOF's MDR 26
A.1 Overview 26
Naming 27 A.2 management items
A.3 named example 28
Annex B (informative) follow MOF object 29
B.1 Overview 29
B.2 Namespace 29
B.3 package 31
Annex C (informative) Model element 32
C.1 Overview 32
C.2 stereotype 33
C.3 code value 33
C.4 mode 33
C.5 Communications 34
C.6 member 34
C.7 frame 34
Annex D (informative) Level 35
D.1 Overview 35
D.2 top 36
D.3 top model 36
D.4 upper model element 36
D.5 lower 37
D.6 lower model 37
D.7 lower model element 37
D.8 Model View 38
D.9 model level 38
Annex E (informative) notation Overview 39
E.1 Overview 39
E.2 basic notation 39
Role E.3 metaclasses 39
E.4 simple example 41
Annex F (informative) conceptualization 43
F.1 Overview 43
F.2 member and classification 43
Conceptualization type F.3 concepts and components set between 43
Annex G (informative) usage and component type 48
G.1 Overview 48
G.2 typical developers, users and 48 registered
G.3 Component Type 49
G.4 registration process 49
Primitive data architecture and be registered article 1 MFI of 13
Figure 2 MFI core package and the target model 14
Figure 3 core Model Overview 15
FIG. 4 MFI's core package registration system 16
Figure 5 core model of the target package 19
Relationship between core model package Figure 6 23
Figure A.1 MDR package (management and identification) 27
Figure A.2 MDR registration packet (context, naming and definition) 27
Figure B.1 MOF package 30
Example Figure C.1 model element package 32
Figure D.1 level pack 35
Figure E.1 enhanced significance triangle and select 40
Figure E.2 registered target objects basic relationship 40
Figure E.3 on "vehicle" registered audiences 41
Figure E.4 concerning the selection of the target object 42 is registered
Figure E.5 has a hierarchical Audience registered 42
Figure F.1 Example 1. Conceptualization Type "Type - Example" (1) 44
Figure F.2 Example 2. conceptualization Type "Type - Example" (2) 44
Figure F.3 Example 3. conceptualization type "super - sub" 45
Figure F.4 Example 4. conceptualization type "basis - variant" (1) 45
Figure F.5 Example 4. conceptualization type "basis - variant" (2) 46
Figure F.6 Example 5. conceptualization type "abstract syntax - the expression" (1) 46
Figure F.7 Example 5. conceptualization type "abstract syntax - the expression" (2) 47
Figure G.1 metamodel Example (1) 50
Figure G.2 metamodel Example (2) 50
Figure G.3 model registered member 51
Figure G.4 registered domain model contour 52
Register Figure G.5 model concepts 53
Figure G.6 model registration mark 54
Figure G.7 model parts sets and model selection register 55
Figure G.8 model components and model selection register 56
Table 1 model type code set (informative) 17
Table 2 conceptualization types of code sets 18
Table 3 to achieve the degree of conformity 24
Table 4 Compliance level 25
Table naming convention A.1 international registration data identifier 28
Table F.1 conceptualization Type - Operation "basic variant" on 47
Table G.1 typical developers, users and 48 registered
Table G.2 part type candidate 49
Table G.3 model part 51
Table G.4 model domain profile 52
Table G.5 model concepts 53
Table G.6 Model 54 mark
Table G.7 model selection and model set 55 parts
Table G.8 model and model selection means 56
Foreword
GB/T 32392 "IT metamodel interoperability framework (MFI)" contains the following sections.
--- Part 1. Reference Model;
--- Part 2. Core model;
--- Part 3. Registry metamodel ontology;
--- Part 4. Model Mapping element model;
--- Part 5. six model component model framework;
--- Part 6. registration procedure.
This section drafted in accordance with GB/T 1.1-2009 given rules.
This section GB/T Part of 232,392. This part of the draft final reference to international standards committee ISO /IEC FCD19763-
2.2007 Edition prepared.
Please note that some of the content of this document may involve patents. Release mechanism of the present document does not assume responsibility for the identification of these patents.
This part of the National Information Technology Standardization Technical Committee (SAC/TC28) and focal points.
This section is drafted. State Key Laboratory of Software Engineering, Wuhan University, China Electronics Standardization Institute.
The main drafters of this section. HE Ke-qing, sail, Wang Chong, Wang Jian, Wang Jing.
Introduction
With e-business and e-commerce on the Internet widespread, cross-country and cross-cultural business trade and other related information exchange
IT industry has become a major concern of foreign staff. Their commitment to regulate the field of business practices on behalf of a specific business process models and standards
Quasi-modeling constructs, such as data elements in each business domain, solid profile range and so on. Standardization work focuses on the model or metamodel
Content, the use of UML and XML representation and exchange business semantics.
Promote the development of standardization activity metamodel and UML profile, these activities include the United Nations Trade Facilitation and Electronic Business
(UN/CEFACT), Organization for the Advancement of Structured Information Standards (OASIS), the Object Management Group (OMG) and health 7 (HL7) standards. However
Instead, different standards organizations in accordance with the provisions of its own way metamodel mode. Therefore, the need to develop consistency element model and registration requirements
Public foundation, or it may result in duplicate and inconsistent.
Unified framework for the classification and registration of standardized model elements to establish an independent development coordination element model is an important part of
Points, and be able to promote their extensive reuse across the organization.
Metamodel and model to describe business concepts that can be shared and components to support interoperability between systems.
Development of Internet applications such sharing of information is becoming increasingly important. However, for real information, different developers, not
Different users and different perspectives will give it a different interpretation. Only by word of classified information is more difficult to organize. we
The complex nature of these order information into a systematic world of information, and suggested that MFI can improve information through co-registration
Sharing and compatibility. This section to solve problems in this area has helped.
IT metamodel interoperability framework (MFI)
Part 2. Core model
1 Scope
GB/T 32392 in this section provides a core model. The core model will be applied in GB/T 32392 of the other part. nuclear
Center model provides for the registration of standardized MFI metamodel meta-model and other models.
Standardize specific business domain registration business concepts and business models is not within the scope of this section.
2 Normative references
The following documents for the application of this document is essential. For dated references, only the dated version suitable for use herein
Member. For undated references, the latest edition (including any amendments) applies to this document.
GB/T 18391.6-2009 Information technology - Metadata registries (MDR) - Part 6. Registration (ISO /IEC 11179-
6.2005, IDT)
Sign metamodel ontology. GB/T 32392.3-2015 Information technology metamodel interoperability framework (MFI) - Part 3
(ISO /IEC 19763-3.2007, IDT)
(MFI) - Part 4 GB/T 32392.4-2015 Information technology metamodel interoperability framework. model mapping metamodel
ISO /IEC 19501.2005 Information technology - Open Distributed Processing - Unified Modeling Language
ISO /IEC 19502.2005 Information technology - Meta Object Facility
ISO /IEC 20944 Information technology Metadata Registry Interoperability and Bindings
3 Terms, definitions and abbreviations
The following terms, definitions and abbreviations apply to this document.
NOTE. 3.1 defines the unified modeling language UML in this part (ISO /IEC 19501.2005) and Meta Object Facility MOF (ISO /IEC 19502.
) 2005 term. 3.2 This section lists used but not included in the terms and their definitions 3.1.
3.1 UML and MOF terminology used in part
3.1.1
Abstract abstraction
So that the essential characteristics of an entity distinct from other entities.
Note. The abstract definition of the boundaries of the observer perspective.
3.1.2
Abstract syntax abstractsyntax
UML class diagrams to define the elements and their relations metaclass.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 32392.2-2015_English be delivered?Answer: Upon your order, we will start to translate GB/T 32392.2-2015_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 10 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 32392.2-2015_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 32392.2-2015_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|