Financial services—Universal financial industry message scheme—Part 5:Reverse engineering
other information
Release date:2011-12-30
drafter:Wang Pingwa, Lu Shuchun, Li Shuguang, Ma Xiaoqiong, Zhao Zhilan, etc.
Drafting unit:China Financial Electronicization Corporation, People's Bank of China, China Securities Regulatory Commission, Industrial and Commercial Bank of China, China Construction Bank, etc.
Focal point unit:National Financial Standardization Technical Committee (SAC/TC 180)
Proposing unit:People's Bank of China
Publishing department:General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Standardization Administration of China
competent authority:National Financial Standardization Technical Committee (SAC/TC 180)
Some standard content:
ICS03.060
National Standard of the People's Republic of China
GB/T 27926.5—2011/IS0/TS 20022-5:2004 Financial services
Universal financial industry message scheme
Part 5: Reverse engineering
(ISO/TS 20022-5.2004, IDT)
Issued on 2011-12-30
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Administration of Standardization of the People's Republic of China
Implementation on 2012-05-01
１ Introduction
2 Normative references
3 Terms and definitions
1 Activities and deliverables
4.1 Gap analysis
GB/T27926.5—2011/ISO/TS20022-5:2004
4.2 Development of business transactions and message sets in accordance with GB/T27926 standards GB/T27926 registration
4.4 Migration preparation
5 Workflow
Gap analysis
5.2 Compliance with GB/T2792 6 Development of standard business transactions and message sets 5.3 GB/T27926 registration
5.4 Migration preparation
Appendix A (normative appendix)
Integration document
TTKANTKACA
QB/T27926.5—2011/IS0/TS20022-5:2004 This part of GB/T27926 was drafted according to the regulations given in G/T1.1-2009. GB/T27926 Financial services Financial industry general message scheme\ consists of the following 5 parts: Part 1: Library input and output methods and format specifications; Part 2: Roles and responsibilities of registration agencies; Part 3: List construction guidelines; Part 4: XMIL design rules: Part 5: Reverse engineering. This part is the 5th part of GB/T27926. This part is equivalent to the English version of IS0/TS20U22-5.2004 Financial Services Financial Industry Common Message Scheme Part 5: IS020022 Reverse Engineering).
Appendix A in this part is a normative appendix.
For ease of use, this standard also makes the following editorial amendments; a) "This part of ISO20022\ is changed to \This part of GB/T27926\, b) Except for the foreword of the international standard.
This part is proposed by the People's Bank of China.
This part is under the jurisdiction of the National Financial Standardization Technical Committee (SAC/TC180). The responsible drafting unit of this part: China Financial Electronicization Company. The participating drafting units of this part: The People's Bank of China, China Securities Regulatory Commission, Industrial and Commercial Bank of China, China Construction Bank, Boshi Fund Management Co., Ltd., Shenzhen Securities Communication Co., Ltd., Shenyin & Wanguo Securities Co., Ltd., Changchun Central Branch of the People's Bank of China, Nanjing Branch of the People's Bank of China.
The main drafters of this section: Wang Huwa, Lu Shuchun, Li Shuguang, Ma Xiaoqiong, Zhao Zhilan, Jia Shuhui, Wang Maolu, Li Yinghui, Wang Deying, Wu Lufang, Qiang Qinghua, Shi Yiqing, Cheng Yongde, Liu Yun, Jing Yun, Chen Lijun, Wang Ji Zeng. Cheng Xiaoyang, Quan Hong. TTTKANTKACA
1 Introduction
GB/T 27926.52011/IS0/TS 20022-5:2004 Financial Services General Message Scheme for the Financial Industry
Part 5: Reverse Engineering
The GB/T27926 library given in GB/T27926.1 contains all business transactions and message sets that comply with the GB/T27926 standard. The methods to be avoided when adding business transactions and message sets that comply with the GB/T27926 standard to the library can be divided into the following situations: a) Situation 1:
There are no business transactions and message sets that comply with the GB/T27926 standard. There is no industry message set.
·Example; collective investment tool;
: Method, according to the FB/T27926.3 modeling guide, a new business transaction and message set that complies with the GB/T2726 standard is developed.
b) Situation 2:
There are no business transactions and message sets that comply with the GB/T27926 standard. Document set. One or more industry message sets exist.
Example: FIX message set exists before securities trading) Method: According to the GB/T27926.5 reverse engineering guide, the industry message set is converted into business transactions and message sets that comply with the GB/T27926 standard.
c) Scenario 3:
Business transactions and message sets that comply with the CB/T27926 standard exist. One or more existing industry message sets also exist. *Example: After securities trading (FIX, Omgeo message sets exist) Method: According to the GB/T27926.5 reverse engineering guide, the existing industry message set is compared with the business transactions and message sets that comply with the GB/T27926 standard, and the business transactions and document sets that comply with the GB/T27926 standard are expanded when necessary.
This section describes the activities of *GB/T27926 reverse engineering" from the user's perspective. These users wish to verify that the business functions covered by their industry message sets are also covered by business transactions and message sets that comply with the GB/T27926 standard. This part does not attempt to define a methodology for reverse engineering.
This part gives the following necessary set of activities: Extract relevant information from the existing industry message set and compare it with the relevant content in the GB/T27926 library: Use the results of the above comparison to develop business transactions and message sets that comply with the GB/T27926 standard - Submit the resulting update application to the Registration Authority (RA): Prepare for migration to business transactions and message sets that comply with the GB/T27926 standard. The main objectives of "Reverse Engineering GB/T 27926" are as follows: 1) To obtain industry knowledge contained in the current industry message set. This document is based on the experience of the Electronic Transaction Oriented Methodology (eBOM) and the SWIFT Standard Encryption Model Methodology framework, and is expanded on the basis of the work results of ISO/TC68/SC4/WG10 Reverse Engineering Working Group, etc. 2) Note that the purpose of reverse engineering is not to systematically generate GB/T 27926-compliant versions of all existing industry messages. Update requirements need to be based on a valid business justification. 1
TTTKAONYKACA
CB/T 27926.5—2011/IS0/TS 20022-5:2004Establish business transactions and message sets that conform to the GB/T27926 standard based on the existing standardization achievements in the industry:- Ensure that the final business transactions and message sets that conform to the GB/T27926 standard completely cover the business scope of the existing industry message sets:
-.- Maximize the interoperability between the existing industry message sets and the business transactions and message sets that conform to the GB/T27926 standard: Support the migration from the existing industry message sets to the business transactions and message sets that conform to the GB/T27926 standard. The structure of this part is as follows:
Chapter 3 gives the specific terms used in this part; Chapter 4 describes the main activities of reverse engineering and describes the approximate final results; Chapter 5 gives a detailed workflow, explaining all activities, inputs and outputs:-…- Appendix A gives a detailed description of the fusion document. 2 Normative references
The following documents are indispensable for the application of this document. For any dated referenced document, only the dated version applies to this document. For any undated referenced document, the latest version (including all amendments) applies to this document. GB/T 27926.1 Financial services, financial industry, general message scheme, Part 1: Library input and output methods and format specifications (GB/T27926.1—2011, IS0/TS20022-1; 2001, MOD) GB/T27926.3 Financial services, financial industry, general message scheme, Part 3: Modeling guidelines (GB/T27926.3-2011, ISO/TS20022-3:200.IDT)
3 Terms and definitions
The terms and definitions in GB/T27926.1 and the following terms and definitions apply to this document. 3.1
Industry message
A message that provides a special message function (possibly multifunctional) and whose message definition is part of the industry message set. 3.2
GB/T 27926 message A message that provides a specific message function and whose message definition is registered in the business process directory of the new GB/T27926 library. 3.3
Message item message item
An element or field used at a specific position in a message. Its exact position is generally described in a message path. 3.4
Message path mesuage path
An exact position in a specific message definition. This position is uniquely identified by a complete hierarchy (i.e. path) from the message level (i.e. the highest level) to the element level (i.e. the lowest level).
4 Post-processing and deliverables
\GB/T27926 reverse engineering\ has four main activities:- Gap analysis
Development of business transactions and message sets that comply with the GB/T27926 standard:- GB/T 27926 registration;
TTTKAONYKACA
—Migration preparation.
GB/T27926.5—-2011/1S0/TS20022-5:2004 This chapter will give the main self-deliverables related to these activities. 4. Gap Analysis
Purpose:
Determine the business domain of the industry document set and identify the corresponding business domains, business processes, activities and supported business transactions in the GB/T27926 business process catalog:
-Compare the business roles in GB/T27926 business transactions and business processes with the parties using industry messages or identified in industry messages
-Verify whether the existing GB/T27926 messages provide all message functions provided by industry messages; evaluate whether the business content of related GB/T27926 messages covers the business content of a single industry message; compare the meaning and data types of used message components and/or business components with single message items. Deliverables:
Description of the gaps, differences and coverage between industry message sets and business transactions and message sets that comply with GB/T27926:
This part focuses on the following library items:
Business domain;
Business process;
Business transaction and message set
Message definition (including message rules):
Business role;
Business component (including business elements and rules): Message component (including message elements and rules): Data type.
Description of industry message sets where library items are missing (i.e., gaps) or where differences have been identified. 4.2 Development of business transactions and message sets that comply with GB/T27926 standards:
Complete the gap analysis for defining or improving all additional information carried by business transactions and message sets that comply with GB/T27926 standards:
-Define the updates and additions necessary for existing business transactions and message sets that comply with GB/27926 standards. This step only focuses on the identified gaps and differences and should verify whether there is a valid business rationale for these gaps and differences in the GB/T27926 library. It should also be considered that the purpose of reverse engineering is not to modify or supplement the business functions supported by the current industry message set (except for business rationale). Deliverables:
Detailed description of how existing GB/T27926 compliant business transactions and message sets must be updated to include the identified gaps and differences,
4.3GB/T27926 Registration
-Preparation room GB/T27926 registration authority request to update the GB/T27926 database with all extensions and modifications. Deliverables:
-Application to the GB/T27926 registration authority to add or change dictionary items and/or catalog items. 3
TTTKAONTKACA
CB/T 27926.5—2011/IS0/TS 20022-5:20044.4 Migration Preparation
Purpose:
Define and document the relationship between the industry message set and the GB/T27926 compliant business transactions and message sets. The amount of information required depends on the migration path chosen:
If it is a complete migration, only the relationship information to support the integration to GB/T27926 is required: If coexistence is allowed for a period of time, a "bidirectional" document is required. This document not only supports the integration to GB/T27926, but also supports the reverse mapping to the industry message set. Develop a plan for migrating business transactions and message sets that meet the GB/T27926 standard. Delivery content:
Integration document;
Coexistence document (optional)
Migration plan.
5 Workflow
This chapter provides a detailed work process description of the four main activities in the GB/T27926 counter-intelligence project. 5.1 Gap analysis
Note:
Gap analysis requires a lot of expertise and documentation on industry message sets. If this document is not available, a comprehensive analysis of the industry message set and its application is required (see step 1 below). The gap analysis also requires compliance with GB/T 27926 standard business transactions and message sets. These documents will be included in the library output; gap analysis is crucial for all subsequent steps; the identification of gaps and risks will quickly determine the subsequent compliance with the business transactions and message sets promoted by the (GB/T27926 standard and the (GB/T27926 registered scope). The identification of overlapping parts will provide the necessary information for the integration of documents and related migration. The main steps of the gap analysis are summarized in the figure below and further explained in text. 1 Industry message ticket document collection
2. Business amount domain vertical gap analysis
3 Business process gap analysis
4 Business transaction difference analysis
5 Message definition difference analysis
6 Business Role Gap Analysis
The above steps will be described in detail in the subsequent chapters and will be performed in an interactive and progressive manner. In "Reverse Engineering Scenario 2" (i.e., there is no business transaction and message set that conforms to the GB/T27926 standard), only the industry message set documents need to be collected. 4
TTTKONYKAA
5.1.1 Industry message set document collection
G/T27926.5—2011/ISO/TS20022-5.2004If the industry message set is fully documented (i.e., including a complete description of the business domain, business processes and business transactions), this step is limited to the clear identification of the document set.
However, in most cases, the industry message set documentation is only about message definitions and mainly records the functions and content of all industry messages. In some cases, even these documents are very limited (i.e., limited to the description of the physical structure). In this case, it is mandatory to complete the industry message set documentation before reverse engineering begins.
Activities:
The recommended approach to the industry message set documentation is depicted in the figure below and further explained in the literature. 1 Start with message definitions
2 Determine the message functions
3 Describe the business meaning
4 Identify business roles
5 Identify business stakeholders
Identify business processes
? Identify business domains
1) Start with the description of the industry message definitions! 1. Describe the business meaning of each industry message item. 2. When industry messages are functional, the meaning of the item may be derived from a specific message function. In this case, all meanings should be given. 3. Describe the business role of each industry message by identifying the functional roles of the sender and receiver of the industry message, and by identifying the functional roles of all other parties present in the content of the industry message. 4. Analyze the purpose of the industry message to identify the "business transactions" (i.e., the different message flows that occur in the industry) that use the industry message, and 5. Document each business transaction. This is best done using a message flow diagram and text description. 6. Analyze the list of identified business transactions to identify the supported business processes. 7. Identify the business areas to which the business processes belong. 3) The biggest problem in this step is to identify the actual business meaning of the domain. Note: An industry message domain can contain multiple business elements and/or partial business elements (in some cases, it may need to be combined with other industry messages to obtain important business solutions).
Note: Multi-function industry messages can also contain domains that specify the use of functions. These domains should not have corresponding message elements in GB/T 27926 messages, and should record the message functions represented by the domain.
Note: An industry message can contain "technical" or "technical" domains, which have no business meaning. In some cases, these domains may have corresponding technical message elements in the GB/T 27926 message definition, but they may not have corresponding business elements. 4) The difference between "business participants" and "business actors" is that the latter represents a functional role (e.g., buyer, seller, etc.), while the former represents a real business entity (e.g., bank, company, broker/distributor, etc.). In the course of a business, a business participant can play multiple business roles (for example, a bank can be a buyer, a service provider, an account service provider, etc.), and multiple business participants can usually have the same business role (a bank, a company, and an individual can all be a buyer). 5
TTTKAONTKACA
GB/T 27926.5--2011/IS0/TS 20022-5:200451.2 Business domain gap analysis
The purpose is to identify the GB/T27926 business domains that use industry message sets, and to investigate whether the industry message sets are also used in other business domains that are not yet part of the GB/T27926 library. Input:
List of GB/T27926 business domains, including definitions; Industry message set documents related to the business domains. Encapsulation:
The recommended approach for business domain gap analysis is shown in the figure below and further explained in the text. GB/T27926
Business domain,
Industry document set model
Compare business domain
Record the scope, differences, and gaps
Industry requirements:
■Differences.
■Differences.
1) Carefully review the list of business areas stored in the GB/T27926 business process catalog. Use the definitions of these business areas to identify the GB/T27926 business areas that best cover the business areas of the industry document set: The following situations may be identified:
No GB/T27926 business areas that cover the business areas of the industry document set; → Based on the industry document set, record this additional business area. One or more GB/T27926 business areas accurately cover the business areas of the industry message set; · Record the coverage:
Record the possible differences between the definitions of the business areas of the identified GB/T 27926 and the corresponding industry message set. One GB/T27926 business area covers multiple industry message set business areas, record which part of the GB/T27926 business area covers the industry message set; * Record the possible differences between the definitions of the business areas of the identified GB/T27926 and the corresponding industry message set. One or more GB/T27926 business areas cover part of the business areas in the industry message set, but the rest of the industry message set is not covered.
Record each benefit scope (i.e., which part of the industry message set is covered by each part of the GB/T27926 business area");
TKNTKACA
Output:
GB/T 27926.5—2011/IS0/TS 20022-5:2004 Based on the industry message set documentation, record which part of the industry message set is not covered. Record the possible differences between the definitions of the identified GB/T27926 business areas and the corresponding industry message set definitions. Give a list of GB/T27926 business areas that cover the (partial) business areas of the industry message set (if necessary, it should include: an explanation of which parts of the industry message set business areas are covered). The list should include possible differences between the identified definitions; give a list of additional business areas that are not covered by the existing GB/T27926 business areas. Each business area in the table should be given a definition based on the industry message set documentation. 5.1.3 Business process gap analysis
The purpose is to identify the GB/T27926 business processes that use the industry message set, And investigate whether the industry message set is also used for other business processes that have not yet become part of the GB/T27926 database. Input 1
---GB/T27926 business process documentation:
GB/T27926 business process description, business process diagram and business activity diagram. Industry message set documents related to business processes. Activities:
The recommended approach for business process gap analysis is described by the following figure and further explained in text. CB/T27926 business-related
Process:
Industry message set documents
Business area:
Supranational:
■Regional measurement:
Matched business processes in the identified GB/T27926 business domain
In the identified GB/T 27926 business process defined in the additional business amount domain
Define business processes in the additional business amount domain Business processes:
Huaqie Pavilion
Gap,
1) For each GB/T27926 business area that has been identified as matching the business area in the industry message set, perform the following activities: Check the list of GB/T27926 business areas stored in the business process directory: * Use documents to identify the GB/T27926 business processes supported by the industry message set: Record the scope of this question:
Net Record the possible differences between the identified GB/T27926 and the business process definitions in the corresponding industry message set. 7
TKNYKACA
GB/T 27926,5—2011/1ISO/TS 20022-5:20042) For each GB/T27926 business area that has been identified as matching a business area in the industry message set, perform the following activities: Identify business processes that are supported by the industry message set and do not yet exist in GB/T27926: Record these attached business processes based on the industry message set documentation. 3) For each business area that has been identified that does not exist in GB/T27926, perform the following activities: Record the business processes supported by the industry message set. Output.
A list of GB/T27926 business processes supported by the industry message set. The list should include possible differences in the definitions that have been identified: A list of attached business processes that are not part of the GB/T27926 library. Each business process in this list will contain available industry message set documentation. 5. 1.4 Business Transaction Gap Analysis
The purpose is to identify GB/T27926 business transactions that use industry message sets and investigate whether the industry message sets also use other business transactions that are part of the GB/T27926 library. Input:
CB/T27926 business transaction documents:
·Textual definition;
·Message flow diagram, including message description.
Industry message set documents related to business transactions and message functions. Activities:
The recommended approach for business transaction gap analysis is described by the following figure and further explained in text. GB/T279286 business
Follow-up description:
■Message flow
Industry message set documents
Business process:
■Key benefit groups
■Gap.
It is the business transaction and approval function that matches the GB/T27926 business process that has been identified.
In the identified business process, small cooperative identification is carried out for industry business transactions, such as identifying related industry business changes in other business processes as additional business transactions. The function of matching the message business transactions:
Egg blue flower four
Two difference matching.
Reference function:
Resolve the gap
GB/T27926.5—2011/1S0/TS20022-5:20041) For each GB/T27926 business process identified as matching the business process in the industry message set, use the document to identify the GB/T27926 business transaction supported by the industry message set; record the coverage range;
Record the possible differences between the identified GB/T27926 and the business transaction documents (text definition and message flow diagram) in the relevant industry message set. Identify the message function that is part of the business transaction in the industry message set and does not affect the GB/T27926 business transaction. If these message functions are identified, then: verify whether the existing GB/T27926 message provides this message function; record which GB/T27926 messages cover these message functions; record the message functions that are not covered by the existing GB/T27926 message definition. , compare the differences between the message functions of GB/T27926 documents in different GB/T27926 business transactions (or message flow diagrams) and the message functions provided in the industry documents; record which industry messages cover the message functions of each GB/T27926 message in each GB/T27926 business transaction. For each GB/T27926 business process that has been identified as matching a business process in the industry message set: 2)
* Identify additional business transactions that the industry message is currently used for and that do not yet exist in GB/T27926: Based on the industry message set document, record additional business transactions (including related business processes). For each business process that has been identified that does not yet exist in GB/T27926: 3||t t||Identify the business transactions that the industry messages are currently used for; based on the industry message set document, record these business transactions (including related business processes). For business transactions that have been identified in this step but do not yet exist in GB/T27926: 42
Identify the message functions of all industry messages used. Verify whether the existing GB/T27926 messages provide this message function; record which GB/T27926 messages cover the additional functions of the industry messages: record which message functions of the industry message set are not covered by the existing GB/27926 message definitions. Output: bzxz.net
A list of GB/T27926 business transactions covered by the industry message set. The list should include possible differences between the identified definitions: - Existing GB/T A list of additional business transactions not covered in the 27926 business transaction - industry documents (in the case of multi-function messages, the industry message should include the specific functions of the message) and their corresponding 27926 message list, if possible, refer to GB/T27926 business transactions, business processes and business areas: a list of additional message functions not covered in the existing GB/T27926 messages. 5.1.5 Message definition gap analysis
The purpose is to identify the GB/T27926 message definitions that use the industry message set, and investigate whether the industry message set is also used in other fields that have not yet been compliant with the GB/T27926 standard Business transactions and message definitions covered by message sets. Input:
-GB/T27926 message:
·Message function;
·Message definition,
Message rule.
5) Not only should the single message used be obtained, but also the business process (i.e., message function) of the message should be obtained. The existing industry message standard is "multi-functional message, and the gap analysis and projection documents require precise business descriptions. For example, it is not enough to declare that IS015022MT502 is used, and further explanation is required, such as for "paying the order" or "sending the order", 95 Message Definition Gap Analysis
The purpose is to identify GB/T27926 message definitions that use industry message sets, and investigate whether industry message sets are also used for other business transactions and message sets that have not been covered by GB/T27926 standards. Input:
-GB/T27926 message:
·Message function;
·Message definition,
Message rule.
5) Not only should the individual messages used be obtained, but also the business transactions that use the message (i.e., message functions). The existing industry message definition is "multi-functional message", and the gap analysis and mapping documents require precise business descriptions. For example, it is not enough to declare that IS015022MT502 is used, and further explanation is required, such as for "paying orders" or "sending orders", 95 Message Definition Gap Analysis
The purpose is to identify GB/T27926 message definitions that use industry message sets, and investigate whether industry message sets are also used for other business transactions and message definitions that have not been covered by GB/T27926-compliant message sets. Input:
-GB/T27926 message:
·Message function;
·Message definition,
Message rule.
5) Not only should the individual messages used be obtained, but also the business transactions that use the message (i.e., message functions) should be obtained. The existing industry message definition is "multi-functional message", and the gap analysis and mapping documents require precise business descriptions. For example, it is not enough to declare that IS015022MT502 is used, and further explanation is required, such as for "paying orders" or "sending orders", 9
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.