550 likes | 566 Views
Hajime Horiuchi, Managing Director, CBOP. Background of the consortium. INSTAC (JSA) Retail System Development and Administration center ARTS Asia/Pacific OMG Japan. CBOP. Dec. 1 , 1997. Supporters. Synon Japan Nippon Unisys Hitachi NEC TIU etc.
E N D
Hajime Horiuchi, Managing Director, CBOP OMG/CBOP Joint Workshop
Background of the consortium INSTAC (JSA) Retail System Development and Administration center ARTS Asia/Pacific OMG Japan CBOP Dec. 1 , 1997 Supporters Synon Japan Nippon Unisys Hitachi NEC TIU etc. Information Resource Schema Standardization Committee Origin Initial core members OMG/CBOP Joint Workshop
Members of CBOP (as of 99.04.30) 107 companies Toshiba Information systems Nomura Research Institute Ken System Development RSI Nikki Information Central Computer Services Takaya Co. Woodland Co. OGIS Lab. Riko Information Systems Sterling Software TIU Hitachi Co. Nippon Unisys Co. NEC NTT Data Oki Electric Co. James Martine & Co. Japan NK-EXA CAC Microsoft Japan OMG/CBOP Joint Workshop
Time line of the consortium Consortium Launching: 1997.12.01 Phase 1: 1998.04 --> 1999.03 Phase 2:1999.04 -->2001.03 Phase 3: TBD OMG/CBOP Joint Workshop
Goals of CBOP To change software development paradigm Information sharing on network computing Standard Business Object Easy Installation of Integrated Application Package Provide infrastructure for EDI, EC OMG/CBOP Joint Workshop
Evolution of Information System Object Oriented Methodologies Information productivity Data Oriented Methodologies Structured Methodologies 情報 BPR OA Enterprise Collaboration SIS Business Applications InterNet Single problem solution Integration with DB 70 90 1960 80 OMG/CBOP Joint Workshop
New Business Requirements Speed Global Optimization Continuous Creation of New Values Real Time Manage Supply Chains Suppliers Manufacturers Warehouses Retailers Customers On Demands Throughput Min. Stock OMG/CBOP Joint Workshop
Strategic Alliance Can not exist alone OMG/CBOP Joint Workshop
Current trends on ReEngineering Intra-Industry Rengineering Inter-Company Reengineering Intra-Company Reengineering SIS OMG/CBOP Joint Workshop
Typical Problem on EDI Collaboration B A RFP Proposal Order Shipping Lack of Common Business Process Model Lack of Common Information Bases OMG/CBOP Joint Workshop
Current EDI Standards ISO/IEC 9735(EDIFACT) Company A Company B Standard Message Standard Business Protocol Non Standardized Application Processing OMG/CBOP Joint Workshop
We Need !! Conceptual Common Business Platform rather than Computerized Software Platforms to enable the collaboration among different enterprises OMG/CBOP Joint Workshop
History of the Standardization Standardization on Information (SC32, TC154….) Standardization on Interfaces & Protocols Standardization on Methodologies Standardization on Hardware OMG/CBOP Joint Workshop
Information Related Standardization Activities in ISO • IEC/TC 3: Documentation and graphical symbols • IEC/SC 3B: Documentation • IEC/SC 3D: Data sets for libraries • IEC/TC 52: Printed circuits • IEC/TC 56: Dependability • IEC/TC 93: Design automation • ISO/ TC 46: Information and documentation • ISO/ TC 68: Banking, securities and other financial services • ISO/ TC 154: Processes, data elements and documents in commerce, industry andadministration • ISO/ TC 184: Industrial automation systems and integration • ISO/ TC 184/SC 4: Industrial data • ISO/IEC JTC 1: Information technology • ISO/IEC JTC 1/SC 2: Coded character sets • ISO/IEC JTC 1/SC 24: Computer graphics and image processing • ISO/IEC JTC 1/SC 27: IT Security techniques • ISO/IEC JTC 1/SC 31: Automatic identification and data capture techniques • ISO/IEC JTC 1/SC 32: Data management and Interchange • ISO/IEC JTC 1/SC 34: Document description and processing languages OMG/CBOP Joint Workshop
Information Related Standard Activities outside of ISO • OMG: BO Initiative • HLSG CALS (HLSGC): High Level Steering Group on CALS • IAeG: Inter-Agency Working Group for Coordinated Open edi Standards Developnt • ICC: International CALS Congress • IETF: Internet Engineering Task Force • ITU: International Telecommunication Union • JSWG: Joint Syntax Working Group (EDIFACT) • TMB: Technical Management Board • UN/CEFACT: United Nations/ Centre for the Facilitation of Procedures and Practices for • Administration, Commerce and Transport OMG/CBOP Joint Workshop
CBOP Vision OMG/CBOP Joint Workshop
Roles of CBOP Components Sharing Components Market Component Developer Establishing Enabling CBOP OMG/CBOP Joint Workshop
The Akihabara OMG/CBOP Joint Workshop
Why Object Orientation? Information User Software User Program Codes Information or Data Object Data Program codes Data Data OMG/CBOP Joint Workshop
Paradigm shift in Software Development Production Order Forecast Assembly Line Product Production Order 部品 Part Part Part Part Bill of Material Part production Line Part production Line Part production Line Part production Line Part Vender Part Vender OMG/CBOP Joint Workshop 11
SI Vender CBOP Tool Vender Component Vender Segregation in Software Business OMG/CBOP Joint Workshop
CBOP Roles BO Library Center BO Development and Certification BO Sharing Mechanism Business Support Business Objects コンテンツユーザ Business Objects Users Business Objects Vendors OMG/CBOP Joint Workshop
Business Object Sharing Mechanism Object Modeling Facility(UML) Business Function Object Patterns Elementary Object Patterns Implementation Support Frameworks & Metadata Atomic Object Contents Developer Developers Business Modeling Facility Business Object Package OMG/CBOP Joint Workshop
Software Reusing by OO Target of Reuse Enabling Mechanism Inheritance Program Codes Aggregation Programming Technique Class Library Design Pattern Design Technique Common Architecture Framework Object Atomic Object OMG/CBOP Joint Workshop
CBOP Phase 1 Basic idea of BO Guideline OMG/CBOP Joint Workshop
Phase 1 Organization President Management Board Staff International Liaison Strategy & Technology Business Support TF Member Service Project Support TF Framework Development TF Tools Implementation TF Forum Project Forum Retail Business Physical distribution Forum Public Utility Human Resource OMG/CBOP Joint Workshop Retail Business
Business Object Objects which represent entities and their relationship in the real world BPR Business Objects Development of business system Presentation Objects Development of GUI Platform Objects Control OMG/CBOP Joint Workshop
Object Implementation Pattern Interface Pattern GUI Pattern EDI Message Pattern Memento CBOP BO Architecture Business Object Pattern (Static & Dynamic) Strategy Role Played Master/Detail Member Guard Trade Check Business Process Object Interface Tool Implemented Object Implemen- tation Tool External Interface Business Task 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 Date Time Name Address Amount Comments Tel. Num. Num. Dates Count Item Model OMG/CBOP Joint Workshop : Composition
Levels of the Standardization Business Domain Business Technologies Projects Business Model Application Modeling technologies PS/TF Conceptual BO Framework Object Modeling Technologies Fw/TF Implementable BO Framework ORB Technologies Implementors Executable BO OMG/CBOP Joint Workshop
Phase 1 Products • CBOP BO Guideline (CBOP-DS) • Legal Guideline on Component Sharing (CBOP-WD) • Business Function Object Patterns(CBOP-WD) • 5 Domain Object Models(CBOP-WD) OMG/CBOP Joint Workshop
BO Guideline Domain Specific BO Patterns UML Basic elementary BO Patterns Enterprise Applications Enterprise Specific Domain Object Model Atomic Object & Normative Codes OMG/CBOP Joint Workshop
Atomic Object CustName EmpName OrdrDate ShipDate PersonName Date OrderQty ShipQty AmntRec SalesAmount Price Qty Money OrdrNumber Things Human Place CustNumber ItemNumber OMG/CBOP Joint Workshop
Pattern Hierarchy Application Pattern Sales Report Inventory management One to One Marketing Domain Specific Object Model Retail Business Object Model Business Function Pattern Trade clearance inventory Invoice … Basic Elementary Pattern Party Role Detail Summary … OMG/CBOP Joint Workshop
Object Patterns Reality Analysis Patterns M. Fowler Capturing BO Model Gamma, Coad, Pree Design Patterns Tuning Tuned BO Model OMG/CBOP Joint Workshop
M. Fowler, Analysis Patterns Party TelePhone Number Person Party address Organization Email OMG/CBOP Joint Workshop
M. Fowler, Analysis Patterns Accountability Accoutability Type Person Accoutability Party Organization Time Period OMG/CBOP Joint Workshop
Deadline StartTime TermOfValidity IsValid() Object Amount $Count(oSummary) $TotalAmount(oSummary) RoleObject /attr = player.attr [added] $MethodOver(oPlayer, oStage) RelationshipObject $MethodOver(o1, o2) Object /attr = category.attr Trade StartTime ContractTime DetailCount() TotalAmount() $TradeCountByBuyer(oBuyer) $DetailCountsByBuyer(oBuyer) Item UnitPrice attr Category attr Player attr TradeItem /UnitPrice = item.UnitPrice /attr = item.attr StartTime EndTime TimeOfValidity Count [added] Amount() [added] IsEffective() $IsInTrade(oItem) Elementary BO Patterns (1) Party (3) Deadline (2) Organization Party children Organization parent Object1 Object2 Object3 (6) Detail (5) Summary (4) Category master detail category summary Master Detail Summary (8) RoleObject = RelationshipObject + a (7) RelationshipObject player o1 o2 stage Object2 Object1 Stage (9) Trade = Detail + RoleObject + Summary + Deadline + a buyer detail item master Buyer OMG/CBOP Joint Workshop
BFOP(Business Function Patterns) OrgStructure BOFP:EnterpriseOrg BOFP:MetaOrg <Org> OrgStructure [組織] 1 1 Orgstructure <EnterPrizeORG> * * [部門] OrgStrctr Belonging * Parametric Collaboration 1 TimePeriod MetaOrg Apply(Explosion) Belonging <EnterpriseORG> * * <Employee> <Dept> Belonging 1 1 * * * Belonging Belong OrgStructure * * <Employee> 1 TimePeriod OMG/CBOP Joint Workshop
Tools Implementation Task Force Repository BO Library Pattern Framework Meta Data Atomic Objects Design Development Analysis Specification Tools OMG/CBOP Joint Workshop
Standardization of Atomic Objects Development Common Business Object Platform Standardization of Business Object Protocol Sponsored By Government OMG/CBOP Joint Workshop
CBOP Phase 2 OMG/CBOP Joint Workshop
Organization in Phase2 President Exec Hearing Committee Exec. Board Project Review Committee Mg’t Board International Liaison Organization Academic Liaison Research & Survey Consumer Object Tools Implementation BO Standardization Business Support Component Reuse Promote OMG/CBOP Joint Workshop
More Business Oriented Component Reuse Promote Task Force CBOP Component Development CBOP Standard BO CBOP Standard BO CBOP Standard BO ATLAS Consortium JavaBeans Consortium Component Component Reusing Exchanging Customer CBOP member CBOP member CBOP member CBOP member Actual Platform(ATLAS) Actual Platform(JB) CoolPlex OMG/CBOP Joint Workshop
Workflow Workflow manager Standard Business Component Protocol Business Component Business Component Business Component API Transaction Monitor Common Services DBMS Distributed Object Platform(CORBA,ActiveX,JBE) Standardization of Business Component Protocol OMG/CBOP Joint Workshop
Cooperation OMG ISO/IEC JTC1 Japan Standards Administration Consortium for Distributed Object Japan Information Processing & Development Center CBOP JECALS Retail System Development Center ERPStudy & Reserch Forum Japan Information Service Association EAN APQC Information Technology Consortium Co. UCC SCC OMG/CBOP Joint Workshop
BFOP Development Project 12/APR/1999 IT Innovation Inc,.Synergy Research Corp. OMG/CBOP Joint Workshop
What is BFOP • BFOP: Business Function Object Pattern • A set of package which defines common business application logic as design patterns. • Design Pattern: A reusable group of objects with data structure and behavior • Package: A logical model of each design pattern in UML(Unified Modeling Language) • BFOPs are organized in a hierarchical manner so that it can represent any level of business logic from an elementary one to a whole application system. • UML 1.3 Parametric Collaboration gives the technical foundation for modeling BFOPs. • BFOPs have been developed in CBOP BO Standardization Div., and 35 BFOPs in whole sale industry are currently available as the result from the activity in CBOP phase 1. • The expected activities in Phase 2: • Refine Phase 1 BFOPs • Extend to the problem domains other than whole sale industry • Promote implementation activities in CBOP member organizations OMG/CBOP Joint Workshop
BFOP Advantages • Save time and cost in business application development • Users can reduce their efforts in analysis and design by logically integrate BFOPs. • By implementing BFOPs in appropriate environments, users can drastically save their time and cost in software construction stage. ( The infrustructure for distributing software components is a MUST) • A specific business organization can easily obtain its own application system meeting their needs by assembling a proper set of BFOPs and changing their parameters if any. • Realize better quality in software products • Developers can refer to the pre-defined data structure and object behavior in common BO design patterns in a well organized structure to avoid wasting time with mistakes and trial-and-errors. • Implementers can reduce the volume of total lines of code in software by using BFOPs which isolate one type business logic in one place. • Realize better skills of engineers • Novice can learn skilled engineers’ know-how represented in BFOPs. • Support BPR • In the early system analysis stage, managers can identify the business functions they need and those they do not by referencing to BFOPs. • Managers and developers can identity the pre-requisites in their behavior, policies and business rules before starting development efforts. • Promote inter-enterprise collaborations • BFOPs give the modeling foundation for inter-enterprise collaborations such as EC and SCM(Supply Chain Management) OMG/CBOP Joint Workshop
BFOP Architecture BFOP:Organization Structure BFOP Structure BFOP: Organization(SS) <Organization> Organization Structure [ Organization] 1 1 Organization Structure <EnterpriseOrg> * * [ Department] OrganizationStructure Employee Assignment * Parametric Collaboration 1 Period Organization(SS) Unfold BFOP:Employee Assignment * * < EnterpriseOrg > < Employee > <Department> Employee Assignment 1 1 * * * Assignment Assignment OrganizationStructure * * <Employee> 1 Period OMG/CBOP Joint Workshop
The directions in BFOP application The result from the activity CBOP Phase 1 (The whole sale industry) BFOP Structure Extension to other industries such as Financial Accounting and Manufacturing Application Basic Applied to Data Centric Approach and/or Object-Oriented Analysis and Design BFOP Package ・Java, C++, VisualBasic, Enterprise JavaBeans ・Component-based Development Tools such as COOL:Plex Implementation ・Application Package Business ・System Integration Business BFOP Implemented Software Component OMG/CBOP Joint Workshop