1 / 30

Purpose of the Japanese NWI Proposal

This proposal aims to establish a common framework for classifying and identifying enterprise objects across different domains and organizations worldwide. It aims to facilitate information exchange, evaluate business performance, and investigate business modeling changes. The proposal addresses the need for a common business object architecture for collaboration among enterprises.

lmitten
Download Presentation

Purpose of the Japanese NWI Proposal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Purpose of the Japanese NWI Proposal Hajime Horiuchi Japan, Email: hori@tiu.ac.jp URL: //www.cbop.gr.jp SC32 WG2　NWI

  2. Change the Title !! Framework for Classification & Identification of Enterprise Objects Global classification & Identification of Enterprise Business Objects SC32 WG2　NWI

  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. SC32 WG2　NWI

  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 SC32 WG2　NWI

  5. Problems to be addressed SC32 WG2　NWI

  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 SC32 WG2　NWI

  7. Current Status of Collaboration ISO/IEC 9735(EDIFACT) Company A Company B Standard Message Standard Business Protocol Non-standardized Application Processing SC32 WG2　NWI

  8. We Need !! Common Business Objects and Its Architecture, rather than Computerized Software Platforms, to enable the collaboration among different enterprises SC32 WG2　NWI

  9. Sharing EBO Infrastructure Common Framwork of Meta Model Standard Modeling Facilities Standard Business Model Common Modeling Constructs Standard Interface EBO Distributed Object Platform SC32 WG2　NWI

  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. SC32 WG2　NWI

  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 SC32 WG2　NWI

  12. Software Component Mart //copmonentsource.com //componentRegistry.com SC32 WG2　NWI

  13. Component Mart Component users Component DBs Metadata Component search Evaluation and verification XML Billing for component use Component registration Component Buy and Sell SC32 WG2　NWI 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 SC32 WG2　NWI

  15. Component Development Component Developers Repository Search facility Pattern Library Dev. tool services EAI tool services Component Library Quality Information Disclosure Service SC32 WG2　NWI

  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 SC32 WG2　NWI

  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 SC32 WG2　NWI

  18. Framework of Meta Model A Specific categorization of meta data to cope with the needs SC32 WG2　NWI

  19. For Efficient Business Collaboration Common Meta model Common Modeling Facility Common Modeling Constructs Common Constructs Business Model Business protocol Business Objects Software Component Company B Company A Processes Standard Messages Standard Protocol SC32 WG2　NWI

  20. Types of Meta-model Concepts Resources / Environments Processes Events Model / Components Targets Notations Representation Rules Regulations Methodologies 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 Exchange Meta Model Use of Model SC32 WG2　NWI

  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 SC32 WG2　NWI

  22. The Scope of the Proposal Meta-Meta Model Naming Scheme Terminology & Taxonomy Modeling Facilities Modeling Language (e.g. UML) Business Modeling Rules Business Object Framework Business Function Object Patterns Common Atomic Objects 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 SC32 WG2　NWI

  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 Meta Object Value Domain Meta data Business Object Components Meta data Use & Exchange Models / Components SC32 WG2　NWI

  24. Object Implementation Pattern Interface Pattern GUI Pattern EDI Message Pattern Memento CBOP EBO Architecture Business Object Pattern (Static & Dynamic) Strategy Role Played Master/Detail Member Guard Trade Check Business Process Object Interface Tool Implemented Object Implement- ation Tool External Interface Plug-in Object EDI Order Message Prepare to Buy Order GUI Checking Order Selecting Estimation Screen Receiving Verification Getting Estimation 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 SC32 WG2　NWI Date Time Name Address Amount Comments Tel. Num. Num. Dates Count Item Model : 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 BOV (Business Operational View) Atomic Object Code Sets Country Product Code Location Country Code FSV (Functional Service View) ISO/IEC11179Specification and Standardization of Data Elements SC32 WG2　NWI

  26. Project Approach SC32 WG2　NWI

  27. However, OMG/ SC7 SC32/WG2 SC32/WG1 W3C MOF/XMI Metadata Meta Model Meta Model XML Schema Modeling Facilities 11179 FOV/BOV UML XML Data Elements Business Scenario Object Models Every thing SC32 WG2　NWI

  28. Consortia discussing Meta model CBOP KCSC OMG ETeMII JINI Consortium ActiveX Consortium Metadata Initiative SC32 WG2　NWI

  29. Is it Possible ? An ideal approach Consortia SC32/ WG2 The Project OMG RFP CBOP Standard Development Coordination of Consortia KCSC OAG Submissions Editor ETeMII SC7 Etc. SC32 WG2　NWI

  30. Thank You hori@tiu.ac.jp http://www.cbop.gr.jp SC32 WG2　NWI

More Related