ISO 20022-2:2013

Financial services - Universal financial industry message scheme - Part 2: UML profile

ISO 20022-2:2013 defines the UML Profile for ISO 20022. In essence, it defines how to use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1:2013. In so doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of additional concrete syntaxes for the Metamodel, such as a textual concrete syntax. The Profile defines how to represent in UML each of the Metamodel's Scope Level Elements (Level 1), Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements that are scoped across the levels. Therefore, the Profile covers all of the Metamodel's Packages, except for the following: · ISO20022::Metamodel::ConceptualLevel::MessageTransport · ISO20022::Metamodel::LogicalLevel::Reversing · ISO20022::Metamodel::LogicalToPhysicalTransformation · ISO20022::Metamodel::PhysicalLevel The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some dependencies. ISO 20022-2:2013 is only applicable when UML is used.

Services financiers — Schéma universel de messages pour l'industrie financière — Partie 2: Profil UML

General Information

• Status: Published
• Publication Date: 06-May-2013
• ICS: 03.060 - Finances. Banking. Monetary systems. Insurance
• Technical Committee: ISO/TC 68/SC 9 - Information exchange for financial services
• Drafting Committee: ISO/TC 68/SC 9 - Information exchange for financial services
• Current Stage: 9093 - International Standard confirmed
• Start Date: 23-Dec-2024
• Completion Date: 13-Dec-2025

Relations

• Revises: ISO 20022-2:2007 - Financial services - UNIversal Financial Industry message scheme - Part 2: Roles and responsibilities of the registration bodies
• Effective Date: 22-Aug-2009

Overview

ISO 20022-2:2013 - "Financial services - Universal financial industry message scheme - Part 2: UML profile" defines the UML profile for the ISO 20022 Metamodel (specified in ISO 20022-1:2013). It provides a UML-based concrete syntax that tells modellers how to represent ISO 20022 Metamodel elements in UML diagrams and models. The standard is applicable only when UML is used and does not preclude other concrete syntaxes (for example textual syntaxes).

Key facts:

• Formalizes how to model the Metamodel in UML (Scope, Business and Message levels).
• Covers almost all Metamodel packages plus the ISO20022::TypeLibrary on which the Metamodel depends.
• Excludes these packages: ISO20022::Metamodel::ConceptualLevel::MessageTransport, ::LogicalLevel::Reversing, ::LogicalToPhysicalTransformation, and ::PhysicalLevel.
• Third edition (2013), replacing the 2007 edition.

Key technical topics and requirements

• Mapping rules: Detailed UML realizations for Metamodel metaclasses (BusinessProcess, BusinessComponent, MessageDefinition, MessageElement, DataTypes, Enumerations, etc.).
• Profile structure: Package organization, stereotypes, tagged values (tags), and constraints that extend UML to capture ISO 20022 semantics.
• Modeling guidance: Which UML diagrams to create, association end semantics, cardinality treatment, and how to express Metamodel properties using UML features.
• Normative artifacts: Annexes defining stereotypes and tags to ensure consistent tool support and interchange.
• Scope levels: Explicit treatment of Level 1 (Scope), Level 2 (Business/Conceptual) and Level 3 (Message/Logical) elements and cross-level Metamodel elements.
• UML-only applicability: The Profile is normative when UML is the modelling notation; alternative concrete syntaxes may be specified separately.

Practical applications and target users

ISO 20022-2:2013 is practical for:

• Financial architects and message designers who create ISO 20022-compliant models using UML.
• Systems integrators and implementers translating business models into logical message definitions.
• Tool vendors and repository providers implementing UML profiles, stereotype/tag support, model validation, and XML/ASN.1 generation workflows.
• Standards bodies and Registration Authorities managing central repositories of models and requiring consistent UML-based artefacts.
• Project leads performing model-driven design of financial message exchanges and interoperability testing.

Benefits:

• Enables consistent, tool-friendly UML representations of ISO 20022 message definitions.
• Improves model portability, validation and mapping to downstream artifacts (e.g., XML Schema generation).

Related standards

• ISO 20022-1:2013 - Metamodel (core definitions)
• Other parts of the series: Parts 3–8 (Modelling, XML Schema generation, Reverse engineering, Message transport, Registration, ASN.1 generation)

Keywords: ISO 20022-2:2013, UML profile, ISO 20022, financial messaging, ISO 20022 Metamodel, message modelling, UML stereotypes, tagged values, financial message standards.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 20022-2
Third edition
2013-05-01
Financial services — Universal financial
industry message scheme —
Part 2:
UML profile
Services financiers — Schéma universel de messages pour l'industrie
financière —
Partie 2: Profil UML
Reference number
©
ISO 2013
©  ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced 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
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved

Contents Page
Foreword . v
Introduction . vii
1  Scope . 1
2  Normative references . 1
3  Terms and definitions . 1
4  How the Profile is specified . 2
4.1  General . 2
4.2  Package structure of the Profile . 2
4.3  Basic organization of the Profile specification . 2
4.4  Properties of the Metamodel and UML — Tag Definitions . 3
4.5  Properties of the Metamodel that correspond to existing UML Properties . 3
4.6  AssociationEnds . 3
4.7  Constraints . 3
4.8  Figures . 3
4.9  How modellers choose which UML Diagrams to create . 3
5  Mapping the Metamodel’s elements to UML . 4
5.1  General . 4
5.2  UML realization of ISO20022::Metamodel . 4
5.2.1  General . 4
5.2.2  Metaclass: BusinessProcessCatalogue . 4
5.2.3  Metaclass: CodeSet . 4
5.2.4  Metaclass: Code . 5
5.2.5  Metaclass: Constraint . 5
5.2.6  Metaclass: DataDictionary . 5
5.2.7  Metaclass: IdentifierSet . 5
5.2.8  Metaclass: Repository . 5
5.2.9  Metaclass: RepositoryConcept . 6
5.2.10  Metaclass: TopLevelCatalogueEntry . 6
5.2.11  Metaclass: TopLevelDictionaryEntry . 6
5.2.12  Metaclass: Trace . 6
5.2.13  DataType: Cardinality . 6
5.3  UML realization of ISO20022::Metamodel::ScopeLevel . 7
5.3.1  General . 7
5.3.2  Metaclass: BusinessProcess . 7
5.3.3  Metaclass: BusinessRole . 7
5.4  UML realization of ISO20022::Metamodel::ScopeToConceptualTransformation . 8
5.4.1  General . 8
5.4.2  Metaclass: BusinessProcessTrace . 8
5.4.3  Metaclass: BusinessRoleTrace . 8
5.5  UML realization of ISO20022::Metamodel::ConceptualLevel::Dynamic . 8
5.5.1  General . 8
5.5.2  Metaclass: BusinessTransaction . 9
5.5.3  Metaclass: MessageTransmission . 9
5.5.4  Metaclass: MessageTransportMode . 10
5.5.5  Metaclass: Participant . 10
5.5.6  Metaclass: Receive . 11
5.5.7  Metaclass: Send . 11
5.6  UML realization of ISO20022::Metamodel::ConceptualLevel::Static . 11
5.6.1  General . 11
5.6.2  Metaclass: BusinessAssociation .11
5.6.3  Metaclass: BusinessAssociationEnd .12
5.6.4  Metaclass: BusinessAttribute .12
5.6.5  Metaclass: BusinessComponent .12
5.6.6  Metaclass: BusinessElement .13
5.7  UML realization of ISO20022::Metamodel::ConceptualToLogicalTransformation .13
5.7.1  General .13
5.7.2  Metaclass: BusinessComponentTrace .13
5.7.3  Metaclass: BusinessElementTrace .14
5.7.4  Metaclass: CodeSetTrace .14
5.7.5  Metaclass: MessageTypeTrace .14
5.8  UML realization of ISO20022::Metamodel::LogicalLevel .15
5.8.1  General .15
5.8.2  Metaclass::BusinessArea .15
5.8.3  Metaclass: ChoiceComponent .15
5.8.4  Metaclass: ExternalSchema .15
5.8.5  Metaclass: MessageAssociation .15
5.8.6  Metaclass: MessageAssociationEnd .15
5.8.7  Metaclass: MessageAttribute .16
5.8.8  Metaclass: MessageBuildingBlock .16
5.8.9  Metaclass: MessageComponent .16
5.8.10  Metaclass: MessageComponentType .17
5.8.11  Metaclass: MessageDefinition .17
5.8.12  Metaclass: MessageDefinitionIdentifier .18
5.8.13  Metaclass: MessageElement .18
5.8.14  Metaclass: MessageSet .19
5.9  UML realization of ISO20022::Metamodel::DataTypes .19
5.9.1  General .19
5.9.2  DataType: Amount .19
5.9.3  DataType: Indicator .19
5.9.4  DataType: Quantity .19
5.9.5  DataType: Rate .19
5.9.6  DataType: Text .20
5.10  UML realization of ISO20022::TypeLibrary::XMLSchema .20
5.11  UML realization of ISO20022::TypeLibrary::Enumerations .21
5.11.1  Enumeration: Aggregation .21
Annex A (normative) Definitions of Stereotypes and Tags .22
Bibliography .71

iv © ISO 2013 – All rights reserved

Foreword
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. 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
International 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 Standards
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 subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 20022-2 was prepared by Technical Committee ISO/TC 68, Financial services.
This third edition cancels and replaces the second edition (ISO 20022-2:2007) which has been technically
revised.
ISO 20022 consists of the following parts, under the general 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 20022-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 potential 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
Registration Authority.
For 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 the link below to take part in the online survey:
http://www.surveymonkey.com/s/20022_2013

vi © ISO 2013 – All rights reserved

Introduction
This International Standard defines a scalable, methodical process to ensure consistent descriptions of
messages throughout the financial services industry.
The 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 growth 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. 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 Standard adopted a model-driven approach
where the model of the industry's 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 business. 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 Standard 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 operational 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 in 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 process 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 Standard's repository is available on the World Wide Web and offers public
access for browsing.
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 International 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.
 This part of ISO 20022 covers the UML profile, a grounding of general UML into a specific subset defined
for this International Standard (to be used when UML is selected to define the models).
 ISO 20022-3 describes a modelling method to produce models for this International Standard.
 ISO 20022-4 covers XML schema generation rules to transform a Logical level model 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 can 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.
viii © ISO 2013 – All rights reserved

INTERNATIONAL STANDARD ISO 20022-2:2013(E)

Financial services — Universal financial industry message
scheme —
Part 2:
UML profile
1 Scope
This part of ISO 20022 defines the UML Profile for this International Standard. In essence, it defines how to
use UML to create models that conform to the ISO 20022 Metamodel, which is defined in ISO 20022-1. In so
doing, it defines a UML-based concrete syntax for the Metamodel. It does not preclude the specification of
additional concrete syntaxes for the Metamodel, such as a textual concrete syntax.
The Profile defines how to represent in UML each of the Metamodel’s Scope Level Elements (Level 1),
Business Level Elements (Level 2) and Message Level Elements (Level 3), as well as Metamodel Elements
that are scoped across the levels.
Therefore, the Profile covers all of the Metamodel’s Packages, except for the following:
 ISO20022::Metamodel::ConceptualLevel::MessageTransport
 ISO20022::Metamodel::LogicalLevel::Reversing
 ISO20022::Metamodel::LogicalToPhysicalTransformation
 ISO20022::Metamodel::PhysicalLevel

The Profile also covers the ISO20022::TypeLibrary Package, upon which the Metamodel has some
dependencies.
This part of ISO 20022 is only applicable when UML is used.
2 Normative references
ISO 20022-1, Financial services — Universal financial industry message scheme — Part 1: Metamodel
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20022-1 and the following apply.
3.1
1)
Metamodel
the ISO 20022 metamodel
1) The reason that the defined term is “the metamodel” rather than “metamodel” is that sometimes the term “UML
Metamodel” is used, and it would be incorrect in such cases to substitute “ISO 20022 metamodel” for “metamodel,” since
the result of the substitution would be “UML ISO 20022 metamodel.”
3.2
Profile
the UML profile for ISO 20022
3.3
UML metamodel
OMG's metamodel of UML
4 How the Profile is specified
4.1 General
This clause explains the technique used to specify the Profile.
4.2 Package structure of the Profile
The internal Package structure of the Profile is similar to the internal Package structure of the Metamodel.
Whereas the Metamodel’s top-level Package is ISO20022::Metamodel, the Profile’s top-level Package is
ISO20022::Profile. The following are the top-level Packages within the ISO20022::Profile Package:
1) ISO20022::Profile::ScopeLevel;
2) ISO20022::Profile::DataTypes;
3) ISO20022::Profile::ConceptualLevel;
4) ISO20022::Profile::LogicalLevel;
5) ISO20022::Profile::ConceptualToLogicalTransformation.

The ISO20022::Profile::Conceptual Package contains two Packages:
ISO20022::Profile::Conceptual::Dynamic;
ISO20022::Profile::Conceptual::Static.

The ISO20022::Profile Package imports two Packages:
ISO20022::TypeLibrary::Enumerations;
ISO20022::TypeLibrary::XMLSchema.
NOTE The ISO20022::Profile Package contains no Package that corresponds to the
ISO20022::Metamodel::ScopeToConceptual Package, because it is not necessary for the Profile to define any
Stereotypes in order to implement that Metamodel Package.
4.3 Basic organization of the Profile specification
Clause 5 systematically outlines the Metamodel, Package by Package, defining how each Metamodel element
maps to UML (it does not include the Packages of the Metamodel that the Profile does not cover, which are
listed in the Scope). Within each Metamodel Package, the Metaclasses are treated in alphabetical order, and
2 © ISO 2013 – All rights reserved

2)
then any DataTypes contained in the Package are treated in alphabetical order . For each Metaclass and
DataType, the Corresponding UML Element is specified.
After outlining the ISO20022::Metamodel Package and its sub-Packages, Clause 5 covers the
ISO20022::TypeLibrary Package and its sub-Packages, defining how each element maps to UML.
In many cases, the definition of how an element maps to UML refers to Stereotypes and
Tag Definitions that are normatively defined in Annex A.
4.4 Properties of the Metamodel and UML — Tag Definitions
In outlining the Metamodel, Metaclass by Metaclass, this part of ISO 20022 lists each of the Properties of the
Metaclass along with the defined approach for modelling that Property in UML. In some cases, the definition
states that the Property in question maps to a Tag Definition defined in Annex A.
4.5 Properties of the Metamodel that correspond to existing UML Properties
In many cases, a Property of a Metaclass from the Metamodel corresponds to a UML Property already
defined in the OMG’s UML specification. This part of ISO 20022 explicitly defines these correspondences. In
such a case, there is no need to define a Tag Definition to realize the Property in UML.
In a number of these cases, the Profile defines that the corresponding UML Property is the non-navigable
memberEnd of an Association in the UML specification, meaning that the Property cannot be captured in an
ISO 20022-compliant UML model. In essence, this means that the Metamodel supports the back-pointer
while UML does not, and there is no compelling reason to define a Tag Definition to fill the gap. The burden of
tracking and setting the back-pointer via a Tagged Value would fall entirely on the modeller, unless additional
code with specific knowledge of this back-pointer had been added to the UML tool.
4.6 AssociationEnds
UML 1.x has a Metaclass named AssociationEnd. UML 2.x does not have a Metaclass of that name; the
Metaclass has been replaced by the “memberEnd” Property of Association. Consequently, this part of ISO
20022 refers frequently to a “memberEnd” of an Association, whereas UML 1.x discourse would refer to an
“AssociationEnd.” For readability, the quotation marks have been omitted when referring to this Property,
even though all other Property names are in quotation marks when they appear in narrative text.
4.7 Constraints
Profile Constraints are expressed in OCL. The Constraints are motivated by the fact that the Profile is an
implementation of the ISO 20022 Metamodel, and they restrict the freedom of the UML modeller. UML models
that do not adhere to the Constraints are not ISO 20022-compliant.
4.8 Figures
The definitions in Annex A of the Profile Stereotypes and Tagged Definitions include figures that use UML
Profile notation to graphically depict the Stereotypes and Tag Definitions. The figures also depict the UML
Metaclasses that the Stereotypes extend, and the Stereotypes’ superclasses where applicable. As is typical
in specifications of MOF Metamodels and UML Profiles, the diagrams duplicate some of the information
contained in the narrative text. The narrative text is normative and the diagrams are non-normative.
4.9 How modellers choose which UML Diagrams to create
A complete overview of when to use which UML diagram can be found in ISO 20022-3.

2) The DataTypes that lie within the Metamodel Package and its contained Packages are DataTypes used to specify the
Metamodel. On the other hand, the DataTypes that lie within the ISO20022::TypeLibrary Package and its contained
Packages are DataTypes used by modellers to specify ISO 20022–compliant financial models.
5 Mapping the Metamodel’s elements to UML
5.1 General
This clause defines how each element of the Metamodel is realized in UML.
5.2 UML realization of ISO20022::Metamodel
5.2.1 General
This subclause defines how the elements of the ISO20022::Metamodel Package map to UML.
5.2.2 Metaclass: BusinessProcessCatalogue
 Corresponding UML Element: A <>-stereotyped Package.
 Mappings of the Metaclass’s Properties:
3)
repository: not implemented in the Profile ;
topLevelCatalogueEntry: corresponds to UML Package’s “packagedElement” Property, which points to
<>-stereotyped UML Elements contained by the
<>-stereotyped Package.
5.2.3 Metaclass: CodeSet
 Corresponding UML Element: A <>-stereotyped Enumeration.
 Mappings of the Metaclass’s Properties:
identificationScheme: captured via <>’s “identificationScheme” Tag Definition;
code: corresponds to UML Enumeration's "ownedLiteral" Property, which points to <>-
stereotyped EnumerationLiterals;
derivation: corresponds to the “supplierDependency” memberEnd of the Association between UML’s
NamedElement and Dependency Metaclasses (the other memberEnd of the Association is named
“supplier”). The <>-stereotyped Enumeration is the NamedElement playing the “supplier”
role and a <>-stereotyped Dependency plays the “supplierDependency” role (another
<>-stereotyped Enumeration is the client end of the Dependency);
trace: corresponds to the “clientDependency” memberEnd of the Association between UML’s
NamedElement and Dependency Metaclasses (the other memberEnd of the Association is named
“client”). The <>-stereotyped Enumeration is the NamedElement playing the “client” role
and a <>-stereotyped Dependency plays the “clientDependency” role (another
<>-stereotyped Enumeration is the supplier end of the Dependency);
length (inherited from Text): captured via <>'s length Tag Definition;
minLength (inherited from Text): captured via <>'s minLength Tag Definition;
maxLength (inherited from Text): captured via <>'s maxLength Tag Definition.

3) It is not realized in the Profile because there is no explicit element in the Profile that corresponds to the Metamodel’s
Repository Metaclass (see 5.2.8).
4 © ISO 2013 – All rights reserved

5.2.4 Metaclass: Code
 Corresponding UML Element: a <>-stereotyped EnumerationLiteral.
 Mappings of the Metaclass’s Properties:
Code value: corresponds to the “body” Property of the OpaqueExpression that plays the “specification”
role for the UML EnumerationLiteral.
5.2.5 Metaclass: Constraint
 Corresponding UML Element: a <>-stereotyped Constraint.
 Mappings of the Metaclass’s Properties:
 expression: corresponds to the “body” Property of the OpaqueExpression that plays the
“specification” role for the UML Constraint;
 expressionLanguage: corresponds to the “language” Property of the OpaqueExpression that plays
the “specification” role for the UML Constraint.
5.2.6 Metaclass: DataDictionary
 Corresponding UML Element: a <>-stereotyped Package.
 Mappings of the Metaclass’s Properties:
4)
 repository: not implemented in the Profile ;
 topLevelDictionaryEntry: corresponds to UML Package’s “packagedElement” Property, which points
to <>-stereotyped UML Elements contained by the <>-
stereotyped Package.
5.2.7 Metaclass: IdentifierSet
 Stereotype: an <>-stereotyped Class.
 Mappings of the Metaclass’s Properties:
identificationScheme: captured via <>'s “identificationScheme” Tag Definition;
length (inherited from Text): captured via <>'s length Tag Definition;
minLength (inherited from Text): captured via <>'s minLength Tag Definition;
maxLength (inherited from Text): captured via <>'s maxLength Tag Definition.
5.2.8 Metaclass: Repository
 Corresponding UML Element: there is no corresponding UML element. ISO 20022-compliant models do
not contain an explicit element corresponding to the Metamodel’s Repository Metaclass. The overall ISO
20022 Repository implicitly realizes this Metaclass.
 Mappings of the Metaclass’s Properties: N/A

4) It is not realized in the Profile because there is no explicit element in the Profile that corresponds to the Metamodel’s
Repository Metaclass (see 5.2.8).
5.2.9 Metaclass: RepositoryConcept
 Corresponding UML Element: a NamedElement, stereotyped by one of the concrete descendants of the
<> Stereotype.
 Mappings of the Metaclass’s Properties:
name: corresponds to NamedElement’s “name” Property;
definition: corresponds to the “ownedComment” Property of UML Element. NamedElement is a
descendant of Element and thus inherits the “ownedComment” Property. “ownedComment” is of type
Comment, and the “definition” populates the “body” Property of Comment;
example: captured via <>'s “example” Tag Definition;
registrationStatus: captured via <>'s “registrationStatus” Tag Definition;
removalDate: captured via <>'s “removalDate” Tag Definition;
semanticMarkup: captured via <>'s “semanticMarkup” Tag Definition;
constraint: corresponds to <>-stereotyped UML Constraints. For each such UML Constraint,
the value of the “constrainedElement” Property points to the RepositoryConcept that owns the
Constraint.
5.2.10 Metaclass: TopLevelCatalogueEntry
 Corresponding UML Element: a NamedElement, stereotyped by one of the concrete descendants of the
<> Stereotype.
 Mappings of the Metaclass’s Properties:
 businessProcessCatalogue: corresponds to the “owner” Property, which UML NamedElements
inherit from Element, and which points to a <>-stereotyped Package.
5.2.11 Metaclass: TopLevelDictionaryEntry
 Corresponding UML Element: a NamedElement, stereotyped by one of the concrete descendants of the
<> Stereotype.
 Mappings of the Metaclass’s Properties:
 dataDictionary: corresponds to the “owner” Property, which UML NamedElements inherit from
Element, and which points to a <>-stereotyped Package.
5.2.12 Metaclass: Trace
 Corresponding UML Element: a <>-stereotyped Dependency.
 Mappings of the Metaclass’s Properties: Trace has no Properties of its own.
5.2.13 DataType: Cardinality
 Corresponding UML Element: MultiplicityElement.
 Mappings of the Metaclass’s Properties:
6 © ISO 2013 – All rights reserved

 isOrdered: corresponds to the “isOrdered” Property of MultiplicityElement;
 isUnique: corresponds to the “isUnique” Property of MultiplicityElement;
 maximumOccurrence: corresponds to the “upperValue” Property of MultiplicityElement. If
maximumOccurence contains 'UNBOUNDED' then the "upperValue" is literal UnlimitedNatural with
value "infinity";
 minimumOccurrence: corresponds to the “lowerValue” Property of MultiplicityElement.
5.3 UML realization of ISO20022::Metamodel::ScopeLevel
5.3.1 General
This subclause defines how the elements of the ISO20022::Metamodel::ScopeLevel Package map to UML.
5.3.2 Metaclass: BusinessProcess
 Corresponding UML Element: a <>-stereotyped UseCase.
 Mappings of the Metaclass’s Properties:
 businessRole: corresponds to the Actor memberEnd of an Association between a
<>-stereotyped Actor and a <>-stereotyped UseCase;
 included: corresponds to the “includingCase” Property of the UML Include Metaclass, which is
accessed via UseCase’s “include” Property;
 includer: corresponds to the non-navigable memberEnd of the Association between UML’s Include
and UseCase Metaclasses, where the navigable memberEnd is “includingCase”;
 extender: corresponds to the non-navigable memberEnd of the Association between UML’s Extend
and UseCase Metaclasses, where the navigable memberEnd is “extendedCase”;
 extended: corresponds to the “extendedCase” Property of the UML Extend Metaclass, which is
accessed via UseCase’s “extend” Property;
 businessProcessTrace: corresponds to the “ownedBehavior” Property that UseCase inherits from
BehavioredClassifier, pointing to the <>-stereotyped Interactions that the
5)
<>-stereotyped UseCase owns.
5.3.3 Metaclass: BusinessRole
 Corresponding UML Element: a <>-stereotyped Actor.
 Mappings of the Metaclass’s Properties:
 businessProcess: corresponds to the UseCase memberEnd of an Association between a
<>-stereotyped Actor and a <>-stereotyped UseCase;
 businessRoleTrace: corresponds to the use of an instance of a <>-stereotyped Actor
6) 7)
to represent a Lifeline  in a <>-stereotyped Interaction.

5) In the Metamodel, this relationship is captured via the BusinessProcessTrace Metaclass, which relates
BusinessProcesses to BusinessTransactions.
5.4 UML realization of ISO20022::Metamodel::ScopeToConceptualTransformation
5.4.1 General
This subclause defines how the elements of the ISO20022::Metamodel::ScopeToConceptualTransformation
Package map to UML.
NOTE The Profile implements all of the Properties of this Package’s Metaclasses via existing UML elements, so
Annex A defines no Stereotypes corresponding to the elements of this Package.
5.4.2 Metaclass: BusinessProcessTrace
 Corresponding UML Element: a link between a <>-stereotyped UseCase and a
<>-stereotyped Interaction. Such a link is an instance of the UML Metamodel’s
8)
Association between BehavioredClassifier and Behavior.
 Mappings of the Metaclass’s Properties:
 businessProcess: corresponds to the “context” property that UML Interaction inherits from Behavior,
which points a <>-stereotyped Interaction to a <>-
9)
stereotyped UseCase.
 businessTransaction: corresponds to the “ownedBehavior” Property that UseCase inherits from
BehavioredClassifier, which points a <>-stereotyped UseCase to
<>-stereotyped Interactions.
5.4.3 Metaclass: BusinessRoleTrace
 Corresponding UML Element: corresponds to the binding of an instance of a <>-
stereotyped Actor to a Lifeline in a <>-stereotyped Interaction.
 Mappings of the Metaclass’s Properties:
businessRole: points to a <>-stereotyped Actor;
participant: points to a <>-stereotyped Interaction.
5.5 UML realization of ISO20022::Metamodel::ConceptualLevel::Dynamic
5.5.1 General
This subclause defines how the elements of the ISO20022::Metamodel::ConceptualLevel::Dynamic Package
map to UML.
6) As specified below, the Metamodel’s Participant Metaclass maps to UML’s Lifeline element.
7) In the Metamodel, this relationship is captured via the BusinessRoleTrace Metaclass, which relates BusinessRoles to
Participants.
8) UML does not define a visual representation of the link between a UseCase and an Interaction, but UML tools typically
provide a way to create the link via property sheets or model explorer windows.
9) The UML Metamodel’s “ownedBehavior” Property is an end of an Association that is not navigable in the other
direction; in other words, that Association does not have a backpointer that points from an Interaction back to the owning
UseCase. However, the “context” Property that Interaction inherits from Behavior can be used to navigate back to the
owning UseCase.
8 © ISO 2013 – All rights reserved

5.5.2 Metaclass: BusinessTransaction
 Corresponding UML Element: a <>-stereotyped Interaction.
 Mappings of the Metaclass’s Properties:
businessProcessTrace: corresponds to the “context” Property that UML Interaction inherits from Behavior,
pointing to the <>-stereotyped UseCase that owns the
<>-stereotyped Interaction;
messageTransportMode: captured via the
Tag Definitions defined for the <> Stereotype;
parentTransaction: if "parentTransaction" points to the outermost BusinessTransaction, then the
"parentTransaction" Property corresponds to the InteractionFragment's "enclosingInteraction"
Property; otherwise, it corresponds to the InteractionFragment's "enclosingOperand" Property;
participant: corresponds to UML Interaction’s “lifeline” Property, pointing to the <>-
stereotyped Interaction’s <>-stereotyped Lifelines;
subTransaction: corresponds to Interaction's "fragment" Property;
trace: not implemented by the Profile. This Property is an artefact of the mapping of the Zachman Logical
level to the Physical level, which is out of scope for this Profile;
transmission: corresponds to UML Interaction’s “message” Property, which points to a
<>-stereotyped Message.
5.5.3 Metaclass: MessageTransmission
 Corresponding UML Element: a <>-stereotyped Message.
 Mappings of the Metaclass’s Properties:
 businessTransaction: corresponds to UML Message’s “interaction” Property, which points to the
<>-stereotyped Interaction that owns the <>-
stereotyped Message;
 derivation: points indirectly to a <>-stereotyped Signal. The indirect path by
which it points to the Signal is as follows: the Message points to a MessageOccurrenceSpecification
(a subclass of MessageEnd) via Message’s “receiveEvent” Property. The
MessageOccurrenceSpecification, in turn, points to a SendSignalEvent via
MessageOccurrenceSpecification’s “event” Property. The SendSignalEvent, in turn, points to a
10)
Signal via SendSignalEvent’s “signal” Property ;
 messageTypeDescription: captured via <>’s “messageTypeDescription”
Tag Definition;
11)
 receive: corresponds to UML Message’s “receiveEvent” Property ;
 send: corresponds to UML Message’s sendEvent Property.

10) Since in UML the binding of a Message to a Signal requires the instantiation of a number of intertwined associations,
UML tools usually provide a shortcut through the user interface that enables the modeller to effect the binding without
having to consciously instantiate each association.
11) Although the Metamodel’s “receive” Property has multiplicity 0.*, UML Message’s “receiveEvent” Property has
multiplicity 0.1, which introduces a restriction when using ISO 20022 with UML t
...