This document describes the modelling workflow, complementing ISO 20022‑1 and ISO 20022‑2. The modelling workflow describes the required steps a modeller follows in order to develop and maintain standardized BusinessTransactions and InterfaceDefinitions/MessageSets.
This document does not describe the permissible artefacts and/or documents to be submitted to the Registration Authority (this information is contained in ISO 20022‑7).
Examples are provided only to illustrate the modelling methodology and are not normative.
Apply a "bird's eye view". At the Scope level, it is recommended to concentrate on the business and avoid discussing the solution or even the communication problem. This means that it is assumed that there is no communication problem and each of the BusinessRoles has a perfect knowledge of and access to all information manipulated within its BusinessProcess. It should be remembered that a "good" BusinessProcess adds tangible business value.
Focus mainly on BusinessProcesses that provide a lot of added value, by eliciting BusinessComponents or BusinessRoles. It is not advisable to become immersed in details, e.g. "cancel", "modify", "create", error handling, at this stage. For example, the description of an "Interbank Transfer" BusinessProcess elicits business terms like "Account", "Credit", etc. The description of the "Cancel Interbank Transfer" has no specific added value and should not be considered at this stage. These details are elaborated during the Conceptual level and the Logical level, when BusinessTransactions and MessageSets are defined.
Concentrate on functional roles, rather than on real-life actors. For example, it is important at this stage to identify the role "Buyer", but it is not yet important to identify whether the buyer is an individual or a corporate or financial institution.
Depending on the useful level of detail, one can decide to decompose a BusinessProcess into more detailed BusinessProcesses.
Roles should only be associated to the most detailed BusinessProcesses, i.e. the lowest level.
Business terms are captured as key BusinessComponents (accompanied by a short and clear description, to remove possible ambiguities), that are elaborated further at the Conceptual level or refer to existing BusinessComponents in the ISO 20022 Data Dictionary.
ISO 20022-3