Purpose of the Japanese NWI Proposal

1
Purpose of the Japanese NWI Proposal

• Hajime Horiuchi
• Japan,

Email hori_at_tiu.ac.jp URL
//www.cbop.gr.jp
2
Change the Title !!
Framework for Classification Identification
of Enterprise Objects

• Global classification Identification of
  Enterprise Business Objects

3
The benefits of the Meta-Model reference model

• Provide common bases for exchanging information
  contents among different domains and different
  organizations across countries.
• Provide common bases for effective evaluation
  mechanism of proprietary components, by asking
  for each components to declare their ingredients
  with specifying standard elements.
• Provide common bases for evaluating business
  performance of the enterprise.
• Provide common bases for effective investigation
  of business modeling and its change which might
  cause software system changes.
•  

4
Classification Identification of
Enterprise Business Objects

• Common view to the metadata for categorizing and
  structuring business objects or enterprise
  objects, extending ISO/IEC 11179 Specifications.
  
• The enterprise objects which consist of both
  information and process elements

5
Problems to be addressed
6
Current status of System Collaboration
Company A
Company B
Business Applications
Business Applications
Non-business Applications
Non-business Applications
Development Tools
Development Tools
Distribute Object Platform
Distribute Object Platform
DBMS?OLTP
DBMS?OLTP
OS
OS
Network
7
Current Status of Collaboration
ISO/IEC 9735(EDIFACT)
Company A
Company B
Standard Message
Standard Business Protocol
Non-standardized Application Processing
8
We Need !!
Common Business Objects and Its
Architecture, rather than Computerized Software
Platforms, to enable the collaboration among
different enterprises
9
Sharing EBO Infrastructure
Common Framwork of Meta Model
Standard Modeling Facilities
Standard Business Model
Common Modeling Constructs
Standard Interface
EBO
Distributed Object Platform
10
Confusions in the Meta Concept
Which is correct ?
type
description
format
relationship
instance
set
set
set

• A clear definition of the meta concept should be
  provided.
• A normative hierarchy of the meta data should be
  defined.
• Sets of normative constructs should be provided.

11
Why so many consortia discuss Meta

• Business Collaborations caused by Internet
• Sharing Exchanging of data processes among
  different Organizations
• Common Software Components for quick building
  of system

12
Software Component Mart
//copmonentsource.com //componentRegistry.com
13
Component Mart
Component users
Component DBs
Metadata
Component search
Evaluation and verification
XML
Billing for component use
Component registration
Component Buy and Sell
Component vendors
14
To accelerate component business
Common Meta Model
End users
Normative Modeling Facilities
Solution providers
Normative domain models
Components
Normative Constructs
Application service providers
Component vendors
15
Component Development
Component Developers
Repository
Pattern Library
Search facility
Dev. tool services
EAI tool services
Component Library
Quality Information Disclosure Service
16
For enabling EAI
Legacy Appl.
Tool from vendor 1
Tool from vendor 2
Tool from vendor 3
Application Integration Tool
Repository
Components
EAI Enterprise Application Integration
17
CBOP Tool integration project
(Government sponsored project )
Members

• Sterling Software
• Computer Associates
• Rational
• Ken Systems Development
• OGIS Research
• Nikki Information Systems
• JNT Systems

Repository
Library
Patterns
Meta data
Frameworks
Objects
AnalysisTools
Modeling Tools
Design Tools
Development Tools
18
Framework of Meta Model

• A Specific categorization of meta data to cope
  with the needs

19
For Efficient Business Collaboration
Common Meta model
Common Modeling Facility
Common Modeling Constructs
Common Constructs
Business Model
Software Component
Business Objects
Business protocol
Company B
Company A
Standard Messages
Processes
Standard Protocol
20
Types of Meta-model
Concepts Resources / Environments Processes Event
s Model / Components
Targets
Notations Representation Rules Regulations Methodo
logies Tools

• Common Instances
• Atomic Objects
• Framework
• Patterns
• Modeling Constructs
• Profiles(Patterns)

Constructs
Facility
Meta Model
Owner Validity Registering Attributes
Model / Components
Exchange Models Development of software Exchange
Components
Use of Model
Exchange Meta Model
21
Necessary contents of the Framework

• Meta object for Naming scheme
• Meta object for Terminologies and Taxonomy scheme
• Meta object for Identification scheme of various
  Business Objects
• Meta object for Modeling Facilities
• Meta object for Modeling Constructs
• Normative Atomic Objects
• Normative Value Domain
• Normative Modeling Patterns as profiles
• Meta object for Registering

22
The Scope of the Proposal
Meta-Meta Model
Naming Scheme
Terminology Taxonomy
Modeling Language (e.g. UML) Business
Modeling Rules Business Object Framework
Business Function Object Patterns Common
Atomic Objects
Modeling Facilities
Meta data
Meta data
Modeling Constructs
Meta data
Meta data
Meta data
Business Object Business Protocol Business
Process Model
Meta data
Meta data
Model
Meta data
Meta data
Software
Business Object Components
Meta data
Use Exchange Models / Components
23
Meta-model representation extending 11179
Meta-Meta Model
Meta Object Concept
Conceptual Domain
Modeling Language (e.g. UML) Metadata
Exchange Format Business Object Framework
Business Function Object Patterns Common
Atomic Objects
Meta data
Meta data
Meta data
Meta data
Meta data
Business Object Business Protocol Business
Process Model
Meta data
Meta data
Meta data
Value Domain
Meta Object
Meta data
Business Object Components
Meta data
Use Exchange Models / Components
24
CBOP EBO Architecture
Business Object Pattern (Static Dynamic)
Strategy
Role Played
Master/Detail
Guard
Member
Trade
Check
Business Process Object
Interface Tool
Implemented Object
Plug-in Object
External Interface
Implement- ation Tool
EDI Order Message
Prepare to Buy
Order
GUI
Checking Order
Selecting Estimation Screen
Getting Estimation
Receiving Verification
Data Access
Selecting Estimation
EDI Transla- tor
Selecting Trader Screen
Selecting Trader
Registration of Trader
Managing Stock
Reexamining Appointed Date Screen
Reexamining Appointed Date
Communi- cation
Object Management
Business Entity Object
Business Objects
Customer
Company
Storehouse
Employee
Item
Pattern Application
Atomic Object
Dependency of use-used
Fundamental Data Type
Date Time
Amount
Name
Address
Comments
Num. Dates
Item Model
Tel. Num.
Count
Composition
25
Common Instance (Domain
non-specific)
Actual Patterns
Met model for Enterprise Object Model
FOP (Function Object Pattern)
Modeling Facility
Domain Specific Patterns
Basic Patterns
UML
unfold
Actual Enterprise Objects
FOF (Function Object Framework)
UML Profile for Specific Purpose
Domain Specific Plug-in Objects
Domain Specific Process Objects
Modeling Constructs
Domain Specific Entity Objects
Atomic Object
BOV (Business Operational View)
Code Sets
Product Code
Country
Location
Country Code
FSV (Functional Service View)
ISO/IEC 11179 Specification and Standardization
of Data Elements
26
Project Approach
27
However,
OMG/ SC7
SC32/WG2
SC32/WG1
W3C
MOF/XMI
Metadata
Meta Model
Meta Model
XML Schema
Modeling Facilities
11179
UML
FOV/BOV
XML
Business Scenario
Data Elements
Object Models
Every thing
28
Consortia discussing Meta model
CBOP KCSC OMG ETeMII JINI Consortium ActiveX
Consortium Metadata Initiative
29
Is it Possible ?
An ideal approach
Consortia
SC32/ WG2
The Project
OMG
RFP
CBOP
Coordination of Consortia
Standard Development
KCSC
OAG
Submissions
Editor
ETeMII
SC7
Etc.
30
Thank You

• hori_at_tiu.ac.jp
• http//www.cbop.gr.jp