Foreword

Introduction

1Scope

2Normative references

3Terms and definitions

4Workflow activities overview

5Scope level

5.1General

5.1.1Purpose

5.1.2Key topics

5.1.3Main activities

5.1.4Deliverables

5.2Activities

5.2.1Define business context

5.2.2Define BusinessProcesses

5.3Guidelines

6Conceptual level

6.1General

6.1.1Purpose

6.1.2Key topics

6.1.3Main activities

6.1.4Deliverables

6.2Activities

6.2.1Define business model

6.2.2Define BusinessTransactions

6.2.2.1Overview

6.2.2.2Define BusinessProcessTrace

6.2.2.3Define MessageTransportMode

6.2.2.4Define Participants

6.2.2.4.1Establish whether there is a central system

6.2.2.5Define BusinessRoleTraces

6.2.2.6Define MessageTransmission(s)

6.3Guidelines

7Logical level

7.1General

7.1.1Purpose

7.1.2Key topics

7.1.3Main activities

7.1.4Deliverables

7.2Activities

7.2.1Define the MessageSet

7.2.2Compose MessageDefinition

7.2.2.1Overview

7.2.2.2Create a MessageDefinition

7.2.2.3Define MessageComponentTypes

7.2.2.4Define DataTypes

7.2.2.5Mapping between the Business Layer and the Message Layer

7.3Constraints

7.3.1Inheritance

7.3.2Normalized MessageDefinitions

7.3.3Normalization

7.3.4Non-Constraint preference

7.3.5Sibling constraints

7.3.6Value derivation

7.3.7Versions versus flavours

7.3.8Modelling associations between MessageComponent Types.

7.4Guidelines

7.4.1BusinessTransactions

7.4.2MessageInstance style

7.4.3Party Neutral MessageInstance

7.4.4MessageInstance granularity

7.4.5How to handle bi-directional relations

7.4.6Factorize

7.4.7How to define an ExternalSchema

7.4.8How to enforce canonical form for date or time related user-defined DataTypes

8Physical level

8.1General

8.1.1Purpose

8.1.2Key topics

8.1.3Main activities

8.1.4Deliverables

8.2Activities

8.2.1Create syntax scheme

9Conventions

9.1Constraints

9.2Naming

9.2.1General

9.2.2Generic rules applicable to all Repository Concepts

Annex AApplied UML diagrams (normative)

A.1Correct UML Diagram to use in different cases

Bibliography