ISO/IEC JTC 1/SC 32 N 0690 Date: 2001-10-01

REPLACES: --

ISO/IEC JTC 1/SC 32

Data Management and Interchange

Secretariat: United States of America (ANSI)

Administered by Pacific Northwest National Laboratory on behalf of ANSI

DOCUMENT TYPE Other Document (open) TITLE Rationale Presentation for the NWI: Framework for Registering Business

Objects SOURCE National Body - Japan PROJECT NUMBER STATUS Attachment to 32N0687 - Proposal for a New Work Item (NWI for

standardization work; Framework for Registering Business Objects ) REFERENCES 32N0687 ACTION ID. COM REQUESTED ACTION

DUE DATE Number of Pages 35 LANGUAGE USED English DISTRIBUTION P & L Members

SC Chair WG Conveners and Secretaries

Douglas Mann, Secretariat, ISO/IEC JTC 1/SC 32 Pacific Northwest National Laboratory *, 901 D Street, SW., Suite 900, Washington, DC, 20024-2115, United States of America Telephone: +1 703 379 6915 x 111; Facsimile; +1 703 379 8934; E-mail: MannD@battelle.org available from the JTC 1/SC 32 WebSite http://www.jtc1sc32.org/ *Pacific Northwest National Laboratory (PNL) administers the ISO/IEC JTC 1/SC 32 Secretariat on behalf of ANSI

1

Rationale for the NWI

Japan National Body,ISO/IEC JTC1 SC32

September, 2001

Annex-1

2

Framework for Registering Business Objects

Title of the NWI :

3

Introduction

This NWI proposal is intending to initiate a new standardization activity within ISO/IEC JTC1 SC32, which focuses on the common view to metadata and metamodels for categorizing and structuring enterprise business objects, extending ISO/IEC 11179 and MOF (Meta object Facility) which will be proposed to ISO by OMG.

The enterprise objects which consist of both information elements and process elements, should be used, not only in the software development efforts of a particular organization, but also, in the interchanging and sharing them among different organizations by the means, such as Electronic Commerce (EC), Electronic Data Interchange (EDI), to materialize effective business collaborations.

4

Business ObjectsBusiness Objects : (by MOU BO Summit Meeting, Nov. 2000)The Summit accepted that business objects could be defined as:

•representing persons, places, things or concepts in a business domain•packaging business procedures, policy and constraints around business data•independent of applications•sharable across industries •reusable

Type of Business Object:

•Business Scenario

•Business Process Model

•Business Entity profile

•Business entity Relationship (Business Object Model)

•Business Information

•Software Components

5

Collaborations between Businesses

Due to the proliferation of Internet and E-business, following types of collaboration became indispensable to current vivid enterprises.

•Efficient exchanging of information contents among different domains and different organizations across countries.

•Effective investigation mechanism of proprietary components in both software and information content, by asking for each components to declare their ingredients with specifying standard elements.

•Evaluating business performance of the enterprise.

•Effective investigation of a business model and its change which might cause information system changes.

6

Sharable Business Objects

Software Components

Object Frameworks

Business Object Model

Information Views

Software

Business Scenario & Process Models

Models Views

Documents

Sharable Business Objects

7

Sharing BO through the Registration

Software Components

Object Frameworks

Business Object Model

Information Views

Software

Business Scenario & Process Models

Models Views

Documents

Sharable Business Objects

Common Modeling Constructs

Common Identification & Classification

Common Modeling Facility

Registration

RegistrationUML

Technology Standard Group

Domain Dependent Standard Group

Business Collaboration

Common Exchange Specification

XML Spec.

Registration or Use of BO

8

Needs for Standard Metamodel

Software Components

Object Frameworks

Business Object Model

Information Views

Software

Business Scenario & Process Models

Models Views

Documents

Sharable Business Objects

Common Modeling Constructs

Common Identification & Classification

Common Modeling Facility

Registration

RegistrationUML

Technology Standard Group

Domain Dependent Standard Group

Business Collaboration

Common Exchange Specification

XML Spec.

Use of BO

Infrastructure for sharing

9

Roles of Metamodel

Sharable Business Objects

Common Modeling Constructs

Common Identification & Classification

Metamodels

consistconsist

Describe & Register

Standard Meta-Metamodel

10

Business Object Registry

Standard Metameta model

Common Identification & Classification

Metamodel for Mapping Models

Metamodel for Registering Objects

Common Model Constructs

Common Domain Specific Business Objects

Metamodel Framework

11

What should be done for Metamodel Standardization

12

Cross domain sharing of the business objects

Today, a lot of industrial standard groups, such as, ebXML, UN/CEFACT, OASIS, EAN, CPFR, UCC, Rosetta-net, GCI, OMG etc. are in charge of the development of domain specific business models or model elements.

Not only in the retailing business, in the every business domain, such as manufacturing, medical, banking, etc, the sharing and the exchanging various types of business objects (business information, business scenario, business process model, business software components), are recognized as a key success factor to materialize effective business collaborations.

However, due to lack of the mechanism which enables the effective and efficient sharing and exchanging those domain specific business objects, there must be fudge duplications and inconsistencies of the business object specifications, and also unnecessary transformation or translation work to keep a cross industrial collaboration.

It must be urgent for both ISO and industrial domain specific consortia, to establish a common normative framework to keep the harmonization in the enterprise business modeling and the interchanges of business object specifications.

13

Organizations for domain specific business objects & metamodel standard

OMGTransportationISO JTC1 SC36 IEEEEducationISO TC250 HL7, OMGMedical

ISO TC184 OMG Manufacturing DTFISA

Manufacturing

TC68 SWIFT, XBRL, OMGBanking / Finance

GCI, EAN, UCC, VICSRetailing

ISO TC154 UN/CEFACT, OASIS ebXML, OMG

Organization

E-Commerce

Domain

14

X

X

XBR L

X

X

XXX

X

X

G C I

X

X

X

O M G

XX

E A N

X

X

UN/CEFACT（TMWG)

XXXXXDomain Models

Methodology

X

X

ISO TC 68

XXXXInterchange format

Xcodes

XXXXXXInformation Elements

X

X

ISOSC32

SCOR

CP FR

RosettaNet

E b XM L

ARTS

ISO TC 184

ISO TC 154

Business Identification

Information View

XMetamodel

XXXXBest Practices

XXXXBusiness Protocols

Issue

Organization

Standard Organizations and their Concerns

15

What are NeededIn the Markets:• An Unified Metamodel Framework which enables Interchange & Sharing

of the various types of enterprise business objects, in E-Commerce, E-Business, EDI, and the business collaborations, such as SCM, e-CRM, etc..

In the Vender or Exchanger Folks:• An Unified Registering Scheme which allows the those who want to

develop sharable enterprise business objects and those who want to access appropriate normative models, modeling constructs and objects in the development of the “easy to collaborate business systems”.

In the Standardizations:• An Unified Metamodel Framework which establishes the harmonization

of the different views to the modeling and the Interchanging of the enterprise business object, which were proposed by the individual domains of the standardization

• A Normative Scheme which enables the appropriate reference and access to pre-existing business object standards, to help new standard development activities, which were been taken place within ISO or outside of ISO.

16

Long Term Trends on the Data Interchange Standardization

data elements specification

modeling facility specification

meta model specification for Registration & Interchange

JTC1 SC32 (IS 11179)

format spacification TC154, TC184

JTC1 SC7 (UML)

domain model specificaiton

Metamodeling facility specification

code and value domain

common Modeling Constructs

Identification & classification

ebXML, OMG, GCI

OMG (MOF)

OMG, TC154(BSR,)

TC68

???

17

Purpose of the NWI

18

Objectives of the NWI

�Establish a consensus on the common generic metamodel framework to enable registering various types of business objects.

�Extending Current IS11179 series standards to enable the representation of complicate business objects

�Extending MOF to represent a generic meta-metamodel and metamodels

�Provide a generic mapping mechanism to enable the exchanging of models which are defined by different facilities or concepts.

Establish a common Metamodel Framework for registering and sharing of business objects

19

Application of the MM Framework

•Data Elements

•Entity Profile

•Process Profiles

•Object Patterns

•UML Profiles

•XML Profiles

•Value domains

•Code Values

•Identification scheme

•Ontologies

: Describe

•Business Scenario

•Business Protocols

•Business Process Models

•Business Collaboration Models

•Business Object Models

•Business Software Components

Standard Meta-metamodel

Common Identification & Classification

Metamodel for Mapping Models

Metamodel for Registering Objects

Common Model Constructs

Common Domain Specific Business Objects

Metamodel Framework

20

Scope of the NWI

IS 11179 as a Standard Defining Scheme

Standard Meta-Metamodel

Metamodel for Mapping

Metamodel for Registering Objects

MOF as a Metamodeling Facility

Extend

Metamodel Framework UML & XML

Compliant

Extend

21

Potential Registers

GCI

CPFR UN/CEFACT ANSI/X12 TC184TC154 OMGTC68BSRUDDI

Agreed Registration Procedure

Standard Meta-metamodel

Common Identification & Classification

Metamodel for Mapping Models

Metamodel for Registering Objects

Common Model Constructs

Normative Domain Specific Business Objects

Metamodel Framework

XBRL

22

Potential End Users

Standard Meta-metamodelNormative Identification & Classification Metamodel for

Mapping Models

Metamodel for Registering Objects

Normative Model Constructs

Normative Domain Specific Business Objects

(Business Scenario, Process Models, Protocols, )

ebXML

Community

GCI Community

OMG

Community

Exchanger

Exchanger Exchanger

BO Registry

23

How to Proceed NWI

24

MM for Common Elementary BO

MM for Common Modeling Constructs

MM for Domain Specific Business process Models

Meta-metamodel for Registering BO

MOF(OMG)

Core Components (ebXML)

BSR(TC154) CBO(OMG)

Atomic objects (CBOP)

MM for Mapping Models

CWM(OMG)

Business Process (ebXML)UML profiles (OMG)

ISO TC184SC5

Process pattars(ebXML)BO Patterns (CBOP)Business Process (UCC, EAN,GCI)

Business Protocols(TC154)Domain Models (OMG)

ISO TC64

MM for Identification & Classification

W3C

Candidates Standards to be referred

KIF+CG

IS11179 (SC32WG2)

UML MM (OMG)

UMM (TMWG)

CD15944-2 (SC32WG1)

25

Scheme for Sharing Objects

Basic Defining Scheme (11179 +X)

Modeling Facilities (UML)Modeling Constructs

Models

Software Components

MetaModels (UML/MM + MOF +X)

Views

MetaMeta Models (MOF +CWM+X )

MetaModeling Facilities (MOF) MetaModel

Interchange Facilities (XMI)

Identification & C

lassification

(Ontology)

Registration Procedure

: Based On : Describe

26

MOF-based metamodel and UML profile

• Using a restricted subset of the UML notation• Providing common style of describing metamodel• A metamodel at M2 level is as an abstract syntax of models at M1level• A model at M1level is an expression of the metamodel• UML profile (stereotype, tagged values etc.) is as additional

constraints for metamodel• Mapping between the metamodel and the UML profile is needed as a

basis for the development of tools• Enable exchanging metamodel/model/data between tools

27

Objective of MOF+• Preserving MOF• Enhancing the facilities:

– specifying relationships • among MOF-based metamodels (of each standard)• between M2 level and M1level

– classifying and registering (based on ISO/IEC 11179-3 rev.)• namespaces of each metamodel and UML profile• patterns as a model instance

– defining mapping between MOF-based metamodels• a part of metamodel at M2 level• a part of model or data at M1 level

28

Required Extension for MOF and 11179-3

• Extension for Composite Object Support– Data Element Concept = Namespace:

• Name of ModelElement to be classified, e.g. Stereotype name, paatern name, component name etc.

– Conceptual Domain = TypedModelElement:• Specification of Typed ModelElement, e.g. metamodel,

profile, standard etc.– Value Domain = ModelInstance:

• Represented Model Instance of Typed Model Element, e.g. pattern, stereotyped element, etc.

– Data Element = ModelElement:• Concrete ModelElement provided with specific Model

Instance.

29

Metamodel Framework

30

ISO/IEC 11179 Specification and Standardization of Data Elements

FOP (Function Object Pattern)

Domain SpecificProcess Objects

Domain SpecificProcess Objects Domain Specific

Plug-inObjects

Domain SpecificPlug-inObjects

Domain Specific Entity Objects

Domain Specific Entity Objects

Atomic Object

Comm

on Instance (Dom

ain non-specific)

Actual Enterprise O

bjectsActual Patterns

DomainSpecificPatterns

DomainSpecificPatterns

BasicPatterns

BasicPatterns

LocationLocation Product Code

Product Code CountryCountry

CodeSets

CodeSets

Country Code

Country Code

Metmodel for Enterprise Object ModelFSV(FunctionalServiceView)

FSV(FunctionalServiceView)

BOV(BusinessOperational View)

BOV(BusinessOperational View)

FOF (Function Object Framework)

unfoldUMLUML

UMLProfile forSpecificPurpose(Metamodel)

UMLProfile forSpecificPurpose(Metamodel)

Modeling Facility

Modeling Constructs

Metamodel of Enterprise Business Object Metamodel of Enterprise Business Object

Element ConceptElement Concept

31

Extension of 11179 for Model Specification

31

Classifications on Modeling Element Concept

Namespace

Model Element Model Instance

Typed Model Element

xxModelElement(s)

Metamodel/Profile

Defined PatternsDefined Patterns

Stereotyped Elements

Stereotyped Elements

Template/Pattern Name(s)

ModelElementName

Metamodel/Profile

yyModelElement

Classified by Domain, Viewpoint etc.

(based on ISO/IEC 11179-3rev)

specified

represented

provided

1..1

0..*

0..*

1..1

1..1

1..1

1..1 1..1

1..1

1..1

1..1 1..*

1..1

1..1

1..1

1..*

32

Extension of MOF Metamodel

6

TagImport

GeneralizableElement

Package

Feature

TypeｄElement

Parameter

Constant TypeAlias

<<MofAttribute>>Attribute Reference

AssociationEndClassifier

Association DataType Class

BehavioralFeatureStructuralFeature

Operation

<<MofExeption>>Exception

MetaModelElement

Pattern

ModelClassifier

ModelAssociation

ViewPoint

ModelReference

Classification

Modelinstance

TypedModelElement

ModelAssociationEnd

Constraint

ModelElement

Namespace

Component FrameworkCollaboration

MapTargetMapSource Map

33

Metamodel for Metamodel Mapping (OMG CWM)TransformationMap

/classifierMap : ModelElement

Classifier(from Core)

ClassifierFeatureMapfunction : ProcedureExpressionfunctionDescription : StringclassifierToFeature : Boolean/classfier : Classifer/feature : Feature/classifierMap : ClassifierMap

1..**

Feature(from Core)

1..**

+cfMap

+cfMap

FeatureMapfunct ion : ProcedureExpressionfunct ionDescript ion : Str ing/source : Feature/target : FeatureclassifierMap : Classi fierMap

Feature(from Core)

1..*

* 1..*

*

ClassifierMapfunct ion : ProcedureExpressionfunct ionDescription : Str ing/source : Classi fier/target : Classi fier/tranformationMap : Namespace/featureMap : FeatureMap/cfMap : ClassifierFeatureMap

0..1

*

+/namespace 0..1

+/ownedElement *

0..1

*

+classi fierMap

0..1

+cfMap*

0..1

*

+classiferMap0..1

+featureMap*

Classi fier(from Core)

1..**

1. .**

+classifier

*

*

1..*

1..*

+featureMap

+featureMap

+feature

+source

+target

*

*

1..*

1..*

+classi fierMap

+classi fierMap*

*

+source

+target

1. .*

1..*

34

Sub projects for NWI

Framework for Registering Business Object Project

Metamodel Architecture

Extension of Defining Facility & Modeling Facility（ 11179, MOF, XMI）

MM for Identification & Classification scheme

MM for Normative Modeling Constructs

Registration Procedure

MOF/XMI PAS Editing