This Technical Specification is being developed in accordance with the UN/CEFACT/TRADE/22 Open Development Process for Technical Specifications.
This requirements document is subject to approval by the UMM Base & Foundation Module 2.0 Project Team.
This document contains information to guide in the development of the technical specification
This version: UMM Meta Model - Base & Foundation Module Version 2.0; Requirement Specification Draft (not approved) of June 19, 2007.
Project Team Lead: Christian Huemer Austria
Editing Team: Birgit Hofreiter Austria
Philipp Liegl Austria
Harry Moyer Australia
Rainer Schuster Austria
Marco Zapletal Austria
Project Team: Sylvain Bellengier France
Ed Buchinski Canada
Steve Capell Australia
William McCarthy USA
Jens Dietrich Germany
Rik Drummond USA
Keith Finkelde Australia
Glenn Miller Canada
Gunther Stuhec Germany
The views and specification expressed in this document are those of the authors and are not necessarily those of their employers. The authors and their employers specifically disclaim responsibility for any problems arising from correct or incorrect implementation or use of this specification.
Name: Christian Huemer
Company: Vienna University of Technology
Street: Favoritenstrasse 9-11/188
City, state, zip/other: 1040
Phone: +43 1 58801 18882
The goals for updating the UMM base and foundation modules to a new version 2.0 are:
- To build the UMM on top of UML 2, which is currently the most supported UML version of UML tool vendors
- To migrate all the existing UMM 1.0 concepts to the new version.
- To make the UMM more user-friendly by a simpler package structure and the use of new UML 2 concepts. The goals of the UMM base module are:
- To define a set of data types that may be shared between the UMM Foundation module and different UMM Specialization modules
- To define the fundament on which constitutive UMM specifications may based upon. The goals of the UMM foundation module are:
- To define the semantics of well-formed UMM business collaboration models.
- To define the validation rules for UMM compliant business collaboration models.
- To clarify the basic concepts that a UMM-compliant business collaboration model is based on.
- To provide an unambiguous definition for UMM business collaboration models that allows an unambiguous mapping to artifacts for deployment in a service-oriented architecture. Note, that the mapping itself is not part of UMM.
- To define a UML profile for the UMM base and foundation modules that allows UML tool vendors to customize their tools to be UMM compliant. Better tool support will lead to a growing UMM user base.
- To re-use all UMM 1.0 concepts that have proven to be useful in practice.
- To specify a more user-friendly concept for the mapping of roles participating in business transactions and business collaborations.
- To provide a closer relationship between process modeling and date modeling - i.e., modeling of the business information that is exchanged in a process.
- To enrich UMM's requirements engineering by introducing conceptual data modeling in the business requirements view.
- To enrich the semantics of a business transaction by allowing different response types.
- To provide a formal binding between the response document in a business transaction and its result in terms of a business entity states as well as between the result of a business transaction and its impact on the process flow on the business collaboration level.
The technical specifications for the UMM base and foundation modules 2.0 are guided by the following key requirements derived from the above goals:
- Map the existing stereotypes of the UMM base and foundation modules (which are based on UML 1.4 base classes) to UML 2 base classes. Map the OCL constraints existing in the UMM foundation module 1.0 to the extension mechanisms of UML 2.
- The UMM base module contains only stereotypes that will be used in the UMM foundation module or are used in any UMM specialization module that currently exists or is under development.
- The UMM foundation module defines only those modeling concepts that are considered as fundamental to deliver a UMM compliant model. This means it delivers concepts to structure the domain and to gather the requirements in that domain. These concepts must ensure that one is able to derive business collaborations and to provide a choreography of business information exchanges - which are captured by another set of UMM concepts. Furthermore, the UMM foundation module provides basic concepts to define the structure of the information exchanges, which also provides an extension point for more advanced modeling of information structures using the UML profile for core components (UPCC, formerly known as BCSS). Additional advanced modeling concepts shall be covered in specialization and extension modules.
- The UMM foundation module is directed towards the business operational view of Open-edi. This means it is independent of certain implementation technologies used in SOAs like Web Services and ebXML or whatever comes up in the future. However, the UMM compliant business collaboration models must be defined in a way that allows a mapping to an implementation technology of choice. Such a mapping is not part of the UMM foundation module. It is a candidate for a specialization/extension module.
- Today, the UML is the most commonly supported modeling language by modeling tools. In order to use the broad range of tools, a UMM business collaboration model must be a special kind of UML model. Thus, the UMM foundation module is based on the UML meta model. In fact, it provides a UML Profile consisting of stereotypes, tagged definitions and constraints.
- In order to support a broad adoption of the UMM-modeling approach the formal descriptions of the UMM shall be supplemented by a set of examples that show UMM compliant artifacts.
- The UML profiles for the UMM base and foundation modules will be based on the UML meta-model version 2.1.1. Using another UML meta-model as a basis for the development of a UMM compliant business collaboration model will not deliver correct results.
- The basic concepts of the UMM and the way they relate to each other shall be described and explained by means of a meta model.
- Different specialization and extension modules might extend the foundation module in order to define additional semantics to the minimum semantics required to create a UMM compliant business collaboration model.
- UN/CEFACT Modeling Methodology (UMM) Meta Model - Base Module Version 1.0, Technical Specification, 2006-10-06 http://www.unece.org/cefact/umm/UMM_Base_Module.pdf
- UN/CEFACT Modeling Methodology (UMM) Meta Model - Foundation Module Version 1.0, Technical Specification, 2006-10-06 http://www.unece.org/cefact/umm/UMM_Foundation_Module.pdf
- Unified Modeling Language Specification (UML), Version 2.1.1 http://www.omg.org/docs/formal/07-02-05.pdf http://www.omg.org/docs/formal/07-02-06.pdf
- Open-edi Reference Model. ISO/IEC 14662, 2004 http://standards.iso.org/ittf/PubliclyAvailableStandards/c037354_ISO_IEC_14662_2004(E).zip
- UML Profile for Core Components (BCSS), Candidate for Version 1.0 http://www.untmg.org/index.php?option=com_docman&task=docclick&Itemid=137&bid=34&limitstart=0&limit=5
- Core Components Technical Specification (CCTS), Version 2.01 http://www.unece.org/cefact/ebxml/CCTS_V2-01_Final.pdf
- Resources-Events-Agents (REA) Specialization Module for UMM
- Business Requirements Specification (BRS), Version 1 Release 5 http://www.cen.eu/uncefactforum/ICG/Documents/ICG%20Home/Business%20Requirements%20Specification%20V1r5%20approved.zip
Copyright © UN/CEFACT 2007. All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to UN/CEFACT except as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by UN/CEFACT or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and UN/CEFACT DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.