Information Management Metamodel IMM

1

• Information Management Metamodel (IMM)
• Initial Submission Presentation
• ad/06-11-06
• Response to RFP ab/05-12-02
• December 6, 2006
• By
• IMM Submission Team

2
Agenda

• IMM Submission Team
• Rational behind IMM
• IMM Overview
• Relationship with other OMG Standards
• IMM Components
• Next Steps

3
IMM Submission Team

• Submitters
• 88solutions
• Adaptive
• Data Access
• Embarcadero Technologies
• International Business Machines (IBM)
• KDM Analytics
• MEGA International
• No Magic, Inc.
• Sandpiper Software, Inc.
• MetaMatrix, Inc.
• Supporters
• EWSolutions
• CubeModel Inc
• VISA
• Steve Fogel
• MetLife
• Computer Associates

4
Rationale Behind IMM

• Common Warehouse Metamodel successful, mature and
  stable
• Widespread and increasing adoption by vendors and
  customers for metadata interchange
• Most widely for relational database information.
• Uptake hampered by CWMs name
• UML vendors and end users have used UML for data
  and XML modeling
• Defined proprietary profiles
• No interoperability of models
• One aim of Information Management Metamodel is to
  bridge gap between UML, data and XML modeling
  worlds

5
IMM Rationale contd..

• IMM will address the needs of Information
  Management. This includes the scope of the
  existing Common Warehouse Metamodel (CWM)
  standard but is extended to cover the following
  areas
• Metamodel for Information Management (IMM)
• UML2 Profile for Relational Data Modeling, with a
  mapping to the IMM metamodel and SQL DDL
• UML2 Profile for Logical (Entity Relationship)
  Data Modeling, with a mapping to the IMM
  metamodel
• UML2 Profile for XML Data Modeling, with a
  mapping to the IMM metamodel and XML Schema
• UML2 Profile for Record Modeling, with a mapping
  to the IMM metamodel and COBOL Copybooks
• A standardized Information Engineering data
  modeling notation with a mapping to the IMM
  metamodel

6
IMM Overview
7
Relationship of IMM with other OMG Standards
SBVR
ITPM
OSM
ODM
BPDM
IMM (CWM)
KDM
UML2.0
MOF QVT
MOF M2T
MOF2.0
XMI
8
Relationship with SBVROne option for Conceptual
Models
Talks about recorded information and buckets
that hold data
Talks about real business things
Two-Way Negotiation
BusinessCustomer
IT Supplier
Semantics of Business Vocabulary Business Rules
Business Requirements
Class-of-Platform Independent Model
Data Store Type Independent
(Business Language Policy Resources)
Logical Data Model General Data
Storage Optimizations
MOF XMI using SBVR XSD
Class-of-Platform Specific Model / Platform
Independent Model
Relational Database Vendor Independent
Business Process NEED to KNOW NEED to
RECORD Information Content Specs
External Design
Physical Data Model Relational Data
Storage Optimizations
Platform Specific Model
Relational Database Vendor Specific
RequirementsSatisfied
RDMBS System Table Rows Relational
Vendor-Specific Optimizations

• ABOUT the Business
• FOR Business purposes
• FROM a Business perspective
• IN the actual language used by Business staff
• BY the Business

Business Model
Information System Model
9
Overview of Initial Submission

• Relational
• Metamodel from Eclipse
• Profile developed
• XML Schema metamodel
• Metamodel from XMI spec/Eclipse
• Profile
• Entity relationship
• Metamodel and profile developed
• LDAP

10
IMM Components ER Metamodel
11
IMM Components ER Modeling UML2.0 Profile
12
IMM Components Relational Metamodel
Class Diagram SQLModel / Main
13
IMM Components Relational Metamodel
Class Diagram Schema 
14
Relational Modeling UML 2.0 Profile
Diagrams Overview
15
Relational Modeling UML 2.0 Profile
Class Diagram Tables Views
16
Relational Modeling UML 2.0 Profile
Class Diagram Operations
17
XML Data Modeling Metamodel

• From Eclipse/XMI Specification (chapter 8)

18
XML Data Modeling UML 2.0 Profile
19
XML Data Modeling UML 2.0 Profile
20
IMM Components LDAP Metamodel

• The LDAP package describes data accessible
  through Lightweight Directory Access Protocol
  (LDAP)
• The LDAP package is primarily based on the LDAP
  standard sections concerning the Directory
  Information Models
• The Directory Information Base is composed of a
  set of entries organized hierarchically into the
  Directory Information Tree (DIT)
• An entry consists of a set of attributes that
  hold information about the object that the entry
  represents.

• An attribute is made up of an attribute
  description (a type and zero or more options)
  with one or more associated values

21
IMM Components LDAP Profile
22
Need for EXPRESS Integration

• EXPRESS (ISO 10303-11) is the predominant
  modeling language in product modeling and product
  lifecycle management
• EXPRESS currently on a separate island
• EXPRESS integration desired for complete
  enterprise information integration

23
MEXICO Project
MOF2 based EXPRESS Integration and Co-existence

• Objectives
• EXPRESS Metamodel
• Mapping EXPRESS to UML and other modeling
  languages using QVT

24
MEXICO Integration in IMM

• Benefits
• Reuse of the IMM infrastructure
• Supporting full integration of product
  model information into a larger information
  environement

25
Packages to be brought forward from CWM with
little change

• Record (but UML Profile to be added)
• Multidimensional
• OLAP
• ETL Transformations
• Warehouse Processes and Operations
• Information Visualization
• Data Mining Package will be moved out and if
  there is interest the subject of a separate RFP

26
Next Steps

• Flesh out set of specific metamodels
• OODB
• Express
• Integrate and rationalize metamodels
• Integrate with external metamodels
• Fully leverage UML2 for profiles
• Formally defined transformations
• Profile to metamodel (QVT)
• Metamodel to language e.g. SQL (M2T)
• Data Modeling Notation
• CWM Migration
• Proof of concept
• Already using Eclipse
• Feedback from community
• DAMA
• Users
• Tool vendors