BS ISO 20022-3-2013 Financial services Universal financial industry message scheme Modelling《金融服务 通用金融行业信息规划 建模》.pdf

1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationBS ISO 20022-3:2013Financial services Universalfinancial industry messageschemePart 3: ModellingBS ISO 20022-3:2013 BRITISH STANDARDNational forewordThis British Standard is the

2、UK implementation of ISO 20022-3:2013.The UK participation in its preparation was entrusted to TechnicalCommittee IST/12, Financial services.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessary

3、provisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2013. Published by BSI StandardsLimited 2013ISBN 978 0 580 70958 6ICS 03.060Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was publishe

4、d under the authority of theStandards Policy and Strategy Committee on 31 May 2013.Amendments issued since publicationDate Text affectedBS ISO 20022-3:2013Reference numberISO 20022-3:2013(E)ISO 2013INTERNATIONAL STANDARD ISO20022-3First edition2013-05-01Financial services Universal financial industr

5、y message scheme Part 3: Modelling Services financiers Schma universel de messages pour lindustrie financire Partie 3: Modlisation BS ISO 20022-3:2013ISO 20022-3:2013(E) COPYRIGHT PROTECTED DOCUMENT ISO 2013 All rights reserved. Unless otherwise specified, no part of this publication may be reproduc

6、ed or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749

7、01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2013 All rights reservedBS ISO 20022-3:2013ISO 20022-3:2013(E) ISO 2013 All rights reserved iiiContents Page Foreword . v Introduction . vii 1 Scope 1 2 Normative references 1 3 Terms and definitions

8、. 1 4 Workflow activities overview . 1 5 Scope level . 4 5.1 General . 4 5.1.1 Purpose 4 5.1.2 Key topics 4 5.1.3 Main activities 4 5.1.4 Deliverables . 4 5.2 Activities . 5 5.2.1 Define business context . 5 5.2.2 Define BusinessProcesses 6 5.3 Guidelines 6 6 Conceptual level 7 6.1 General . 7 6.1.1

9、 Purpose 7 6.1.2 Key topics 7 6.1.3 Main activities 7 6.1.4 Deliverables . 7 6.2 Activities . 8 6.2.1 Define business model . 8 6.2.2 Define BusinessTransactions 9 6.3 Guidelines 12 7 Logical level . 12 7.1 General . 12 7.1.1 Purpose 12 7.1.2 Key topics 12 7.1.3 Main activities 13 7.1.4 Deliverables

10、 . 13 7.2 Activities . 13 7.2.1 Define the MessageSet . 13 7.2.2 Compose MessageDefinition . 13 7.3 Constraints . 17 7.3.1 Inheritance . 17 7.3.2 Normalized MessageDefinitions 18 7.3.3 Normalization . 18 7.3.4 Non-Constraint preference . 18 7.3.5 Sibling constraints 18 7.3.6 Value derivation . 18 7.

11、3.7 Versions versus flavours 18 7.3.8 Modelling associations between MessageComponent Types. . 18 7.4 Guidelines 19 7.4.1 BusinessTransactions 19 7.4.2 MessageInstance style 19 7.4.3 Party Neutral MessageInstance . 19 BS ISO 20022-3:2013ISO 20022-3:2013(E) iv ISO 2013 All rights reserved7.4.4 Messag

12、eInstance granularity .19 7.4.5 How to handle bi-directional relations 20 7.4.6 Factorize .20 7.4.7 How to define an ExternalSchema .20 7.4.8 How to enforce canonical form for date or time related user-defined DataTypes 20 8 Physical level .21 8.1 General 21 8.1.1 Purpose .21 8.1.2 Key topics .21 8.

13、1.3 Main activities 21 8.1.4 Deliverables 21 8.2 Activities .21 8.2.1 Create syntax scheme .21 9 Conventions .22 9.1 Constraints .22 9.2 Naming 22 9.2.1 General 22 9.2.2 Generic rules applicable to all Repository Concepts 22 Annex A (normative) Applied UML diagrams .23 Bibliography 24 BS ISO 20022-3

14、:2013ISO 20022-3:2013(E) ISO 2013 All rights reserved vForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees.

15、 Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the Interna

16、tional Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Stan

17、dards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subje

18、ct of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 20022-3 was prepared by Technical Committee ISO/TC 68, Financial services. This first edition cancels and replaces ISO/TS 20022-3:2004. ISO 20022 consists of the following parts, under the gener

19、al title Financial services Universal financial industry message scheme: Part 1: Metamodel Part 2: UML profile Part 3: Modelling Part 4: XML Schema generation Part 5: Reverse engineering Part 6: Message transport characteristics Part 7: Registration Part 8: ASN.1 generation ISO 20022-1:2013, ISO 200

20、22-2:2013, ISO 20022-3:2013, ISO 20022-4:2013, ISO 20022-5:2013, ISO 20022-6:2013, ISO 20022-7:2013 and ISO 20022-8:2013 will be implemented by the Registration Authority by no later than the end of May 2013, at which time support for the concepts set out within them will be effective. Users and pot

21、ential users of the ISO 20022 series are encouraged to familiarize themselves with the 2013 editions as soon as possible, in order to understand their impact and take advantage of their content as soon as they are implemented by the Registration Authority. For further guidance, please contact the Re

22、gistration Authority. BS ISO 20022-3:2013ISO 20022-3:2013(E) vi ISO 2013 All rights reservedFor the purposes of research on financial industry message standards, users are encouraged to share their views on ISO 20022:2013 and their priorities for changes to future editions of the document. Click on

23、the link below to take part in the online survey: http:/ BS ISO 20022-3:2013ISO 20022-3:2013(E) ISO 2013 All rights reserved viiIntroduction This International Standard defines a scalable, methodical process to ensure consistent descriptions of messages throughout the financial services industry. Th

24、e purpose of this International Standard is to describe precisely and completely the externally observable aspects of financial services messaging in a way that can be verified independently against operational messaging. The trigger for the creation of this International Standard was the rapid grow

25、th in the scale and sophistication of messaging within financial services during the 1990s using ISO 15022. The financial services industry (from here on referred to as “the industry“) created the first version of this International Standard as the successor to ISO 15022 in response to that trigger.

26、 Since ISO 15022, the industry has broadened the scope from securities to the entire industry for this International Standard. This International Standard is based on open technology standards, which historically have evolved more rapidly than the industry itself. Consequently, this International St

27、andard adopted a model-driven approach where the model of the industrys messaging can evolve separately from the evolution of the messaging technology standards. The period during which this International Standard has emerged followed the widespread adoption of the World Wide Web (the Web) for busin

28、ess. XML (eXtensible Mark-up Language) emerged as the de facto standard for document representation on the Web and it became the first syntax for ISO 20022. The modelling process is further refined into three levels which, in addition to the messaging technology standard, is why this International S

29、tandard is based on four levels: the Scope level, the Conceptual level, the Logical level and the Physical level. This four-level approach is based on the first four levels of the Zachman Framework. The remaining two levels of the Zachman Framework are equivalent to the implementations and the opera

30、tional levels, respectively. In ISO 20022-1, the first, second and third levels are described in UML (Unified Modelling Language) because it is widely supported and supports multiple levels of abstraction. The models created in accordance with this International Standard are technology independent i

31、n that they do not require any particular physical expression or implementation. Such models aim to describe all parts of the message exchange. The models form the definition of the protocol between participants exchanging messages. This International Standard defines a method that describes a proce

32、ss by which these models can be created and maintained by the modellers. The models and the Physical level artefacts are stored in a central repository, serviced by a Registration Authority. This International Standards repository is available on the World Wide Web and offers public access for brows

33、ing. The Repository is organized into two areas: A DataDictionary containing the industry model elements likely to have further or repeated use. A BusinessProcessCatalogue that contains models describing specific message definitions and business processes, and physical syntax implementations. This I

34、nternational Standard is organized into the following parts. ISO 20022-1 describes in MOF (Meta-Object Facility) the metamodel of all the models and the Repository. BS ISO 20022-3:2013ISO 20022-3:2013(E) viii ISO 2013 All rights reserved ISO 20022-2 covers the UML profile, a grounding of general UML

35、 into a specific subset defined for this International Standard (to be used when UML is selected to define the models). This part of ISO 20022 describes a modelling method to produce models for this International Standard. ISO 20022-4 covers XML schema generation rules to transform a Logical level m

36、odel into a Physical level description in the syntaxes. ISO 20022-5 covers logical model alignment and reverse engineering of existing message syntaxes. ISO 20022-6 covers message transport characteristics that define the quality of service required by the business process definitions so that they c

37、an operate successfully. ISO 20022-7 describes the process of managing the registration of models and physical syntax implementations. ISO 20022-8 gives ASN.1 syntax generation rules to transform a Logical level model into a Physical level description in ASN.1. BS ISO 20022-3:2013INTERNATIONAL STAND

38、ARD ISO 20022-3:2013(E) ISO 2013 All rights reserved 1Financial services Universal financial industry message scheme Part 3: Modelling 1 Scope This part of ISO 20022 describes the modelling workflow, complementing ISO 20022-1 and ISO 20022-2. The modelling workflow describes the required steps a mod

39、eller follows in order to develop and maintain standardized BusinessTransactions and MessageSets. This part of ISO 20022 is not intended to describe what will be the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022-7). E

40、xamples are provided only to illustrate the modelling methodology and are not normative. 2 Normative references ISO 20022-1, Financial services Universal financial industry message scheme Part 1: Metamodel ISO 20022-2, Financial services Universal financial industry message scheme Part 2: UML profil

41、e 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 20022-1 and ISO 20022-2 apply. 4 Workflow activities overview The objective of a standardized BusinessTransaction is to define a commonly agreed solution for communication problems existing among diff

42、erent organizations within the context of a given BusinessProcess. For a given communication problem in a given business context, several solutions can be developed. The purpose of this part of ISO 20022 is to explain the different steps a modeller should follow to ensure that all ISO 20022 items su

43、ch as BusinessComponents/BusinessElements, MessageComponentTypes/MessageElements, BusinessTransactions and MessageDefinitions are defined in a consistent way. The ISO 20022 methodology is composed of a set of activities. These activities are grouped into the following levels: Scope level; Conceptual

44、 level; BS ISO 20022-3:2013ISO 20022-3:2013(E) 2 ISO 2013 All rights reserved Logical level; Physical level. For each of these activities, this part of ISO 20022 describes: the artefacts needed to start this activity (required input); the artefacts that should be the result of this activity (expecte

45、d output); an example (where useful); any constraints and rules of modelling that should be followed or taken into account. BS ISO 20022-3:2013ISO 20022-3:2013(E) ISO 2013 All rights reserved 3Figure 1 High level workflow activity diagram BS ISO 20022-3:2013ISO 20022-3:2013(E) 4 ISO 2013 All rights

46、reserved5 Scope level 5.1 General 5.1.1 Purpose The purpose of the Scope level is to achieve a better understanding of the BusinessArea and BusinessProcesses for which ISO 20022 compliant BusinessTransactions and MessageSets will be developed. a) Describing the BusinessProcesses, including the Busin

47、essRoles and their need for business information, helps in the identification of the communication problems that exist among the organizations that take part in these processes. Those communications problems are the main drivers for the next phase (Conceptual level). b) Identifying business informat

48、ion manipulated in a BusinessArea is also important because the MessageDefinitions, which will be designed later, will contain data elements that are related to the BusinessConcepts. An explicit link between BusinessConcepts and MessageConcepts will be helpful for interoperability for later maintena

49、nce and for change management; if something changes in a BusinessArea, it will be possible to identify the impact on previously defined MessageDefinitions. 5.1.2 Key topics The key topics of the Scope level are: identification of the business context of the communication problem to be solved; understanding the daily business in the BusinessArea and BusinessProcesses with no special focus on the BusinessTransactions and Mess