Hajime Horiuchi, Managing Director, CBOP

99/05/20 OMG/CBOP Joint Workshop 1

Hajime Horiuchi, Managing Director, CBOP


Background of the consortium

Information Resource Schema Standardization Committee

CBOP

Synon Japan

Nippon Unisys

Hitachi

NEC

TIU etc.

INSTAC (JSA)

Retail System Development and Administration center

ARTS Asia/Pacific

OMG Japan

Supporters

Initial core membersOrigin

Dec. 1 , 1997


Members of CBOP (as of 99.04.30) 107 companies

Sterling Software

TIU

Hitachi Co.

Nippon Unisys Co.

NEC

NTT Data

Oki Electric Co.

James Martine & Co. Japan

NK-EXA

CAC

Microsoft Japan

Toshiba Information systems

Nomura Research Institute

Ken System Development

RSI

Nikki Information

Central Computer Services

Takaya Co.

Woodland Co.

OGIS Lab.

Riko Information Systems


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


Goals of CBOP

To change software

development paradigm

Information sharing

on network computing

Provide infrastructure for EDI, EC

Easy Installation of Integrated Application Package


Evolution of Information System

1960 　　 70 80 90

情報

Information productivity

Single problem solution

Business Applications

OA

Integration with DB

SIS

BPR

Enterprise Collaboration

Structured Methodologies

Data Oriented Methodologies

Object Oriented Methodologies

InterNet


New Business Requirements

Suppliers RetailersWarehousesManufacturers Customers

Min. StockMin. Stock On DemandsOn Demands ThroughputThroughput

Global Optimization

Global Optimization

SpeedSpeed

Real TimeReal Time

Manage Supply Chains

Continuous Creation of New Values


Strategic Alliance

Can not exist alone


Current trends on ReEngineering

Intra-Company Reengineering

Inter-Company Reengineering

Intra-Industry Rengineering

SIS


RFP

Typical Problem on EDI CollaborationA B

Proposal

Order

Shipping

Lack of Common Business Process ModelLack of Common Information Bases


Current EDI Standards

Standard Message

Standard Business Protocol

Company A Company B

Non Standardized Application Processing

ISO/IEC 9735(EDIFACT)


We Need !!

Conceptual Common Business Platform

rather than Computerized Software Platforms

to enable the collaboration among different enterprises


History of the Standardization

Standardization on Hardware

Standardization on Methodologies

Standardization on Interfaces & Protocols

Standardization on Information (SC32, TC154….)


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 and 　 administration•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


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


CBOP Vision


Roles of CBOP

Components Market Component Developer

ＣＢＯＰ

Components Sharing

Establishing Enabling


The Akihabara


Why Object Orientation?

Program

Codes

Data

Information or Data

Program codes

Data

Data

Software User

Information User

Object


Paradigm shift in Software Development

Assembly Line Product

ProductionOrder

Forecast

部品

ProductionOrder

Part

Part

production

Line

Part

Part

production

Line

Part

Part

production

Line

Part

Part

production

Line

Bill of

Material

Part Vender

Part Vender


Segregation in Software Business

SI Vender

Component

Vender

Tool Vender

CBOP


CBOP Roles

BO Sharing Mechanism

Business Objects

コンテンツユーザ

BO Development and Certification

Business Support

BO Library Center

Business Objects UsersBusiness Objects Vendors


Business Object Sharing Mechanism

BusinessFunctionObjectPatterns

Object Modeling Facility(UML)

Contents

Developer

Implementation

Support

Frameworks

&

Metadata

Elementary ObjectPatterns

Atomic Object

BusinessModelingFacilityBusiness Object

Package

Developers


Program CodesInheritance

Programming Technique

Design Pattern

Design Technique

Class Library

Object

Framework

Atomic Object

Target of Reuse

Aggregation

Software Reusing by OO

Common

Architecture

Enabling Mechanism


CBOP Phase 1

Basic idea of BO Guideline


Management Board

Strategy & Technology

Framework Development

TFRetail Business

Project Support TF

Business Support TF Member Service

Forum

Staff

Tools Implementation TF

President

Physical distributionPublic Utility

Forum

Forum

Human Resource

Retail Business

International Liaison

Project

Phase 1 Organization


Business Object

Business

Objects

Presentation

Objects

Platform

Objects

Development of

business system

Development of

GUI

BPR

Objects which represent entities and their relationship in the real world

Control


CBOP BO Architecture

Date Time

Atomic Object

Num. Dates

Amount Name

Item Model

Address

Tel. Num.

Comments

Business Entity Object

Customer Company Storehouse

Employee Item

Business ProcessObject

Prepare to Buy

Getting Estimation

Registrationof Trader

Order

Managing Stock

Receiving Verification

Business TaskObject

Checking Order

Selecting Trader

External Interface

EDI Order Message

Selecting Estimation Screen

Selecting Trader Screen

Reexamining Appointed Date Screen

Implemen-tationTool

DataAccess

ObjectManagemen

t

Interface

ToolGUI

Communi-

cation

StrategyStrategy

GuardGuard

Business Object Pattern (Static & Dynamic)

TradeTrade

Role PlayedRole Played Master/Detail

Master/Detail

: Pattern Application

: Dependency of use-used

ObjectImplementatio

n PatternMementoMemento

Business Objects

CheckCheck

Selecting Estimation

: Composition

MemberMember

Interface Pattern

GUI PatternGUI Pattern

EDI Message PatternEDI Message Pattern

EDITransla-

tor

Imp

lemen

ted O

bject

FundamentalData Type

Reexamining Appointed Date

Count


Implementable BO Framework

Conceptual BO Framework

Executable BO

　　　　 Business Model

Levels of the Standardization

ORB Technologies

Object Modeling

Technologies

Application Modeling technologies

Business Domain Business Technologies

Fw/ ＴＦ

ＰＳ /ＴＦ

Ｐｒｏｊｅｃｔｓ

Ｉｍｐｌｅｍｅｎｔｏｒｓ


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)　　　　　　　　　　　　　　　　　　　


Atomic Object & Normative Codes

UML

Dom

ain Specific B

O P

atterns

Basic elem

entary BO

P

atterns

Enterprise Applications

Enterprise Specific Domain

Object Model

BO Guideline


OrdrDate ShipDateCustName EmpName

OrderQty ShipQty

Qty

Price SalesAmount

Money

OrdrNumber CustNumber ItemNumber

AmntRec

DatePersonName

Atomic Object

Human PlaceThings


Pattern Hierarchy

Retail Business Object ModelDomain

Specific Object

Model

Trade clearance inventory Invoice

BusinessFunctionPattern

Application

Pattern

Sales Report

Inventorymanagement

One to OneMarketing

Basic ElementaryPattern

Party Role Detail Summary…

…


Object Patterns

Reality

CapturingAnalysis

Patterns

BO Model

TuningDesign

Patterns

Tuned BO Model

M. Fowler

Gamma,

Coad, Pree


Party

Person

Organization

Party

TelePhone Number

address

Email

M. Fowler, Analysis Patterns


Accountability

Person

Organization

Party

Accoutability

Type

Accoutability

Time Period

M. Fowler, Analysis Patterns


Elementary BO PatternsPartyParty

Object1Object1 Object2Object2 Object3Object3

(1) Party

OrganizationOrganization

(2) Organization

parent

children DeadlineStartTimeTermOfValidityIsValid()

DeadlineStartTimeTermOfValidityIsValid()

(3) Deadline

(4) Category

Object/attr = category.attr

Object/attr = category.attr

Categoryattr

Categoryattr

category

(5) Summary

SummarySummarysummary

(6) Detail

MasterMaster

detail

DetailDetail

master

(7) RelationshipObject

Object1Object1 Object2Object2

(8) RoleObject = RelationshipObject +

Playerattr

Playerattr StageStage

playerRelationshipObject

$MethodOver(o1, o2)

RelationshipObject

$MethodOver(o1, o2)

o1 o2

ObjectAmount$Count(oSummary)$TotalAmount(oSummary)

ObjectAmount$Count(oSummary)$TotalAmount(oSummary)

RoleObject/attr = player.attr [added]$MethodOver(oPlayer, oStage)

RoleObject/attr = player.attr [added]$MethodOver(oPlayer, oStage)

stage

itembuyer

TradeStartTimeContractTimeDetailCount()TotalAmount()$TradeCountByBuyer(oBuyer)$DetailCountsByBuyer(oBuyer)

TradeStartTimeContractTimeDetailCount()TotalAmount()$TradeCountByBuyer(oBuyer)$DetailCountsByBuyer(oBuyer)

BuyerBuyerdetailmaster

TradeItem/UnitPrice = item.UnitPrice/attr = item.attrStartTimeEndTimeTimeOfValidityCount [added]Amount() [added]IsEffective()$IsInTrade(oItem)

TradeItem/UnitPrice = item.UnitPrice/attr = item.attrStartTimeEndTimeTimeOfValidityCount [added]Amount() [added]IsEffective()$IsInTrade(oItem)

ItemUnitPriceattr

ItemUnitPriceattr

(9) Trade = Detail + RoleObject + Summary + Deadline +


BFOP（ Business Function Patterns)

OrgStructure

Belonging

ＢＯＦＰ :EnterpriseOrg ＢＯＦＰ： MetaOrg

Orgstructure

MetaOrg

Belonging

<Org>

TimePeriod

OrgStrctr

<Dept>

<Employee>

Belong

<EnterPrizeORG>

OrgStructure

Belonging

Parametric Collaboration

<EnterpriseORG>

TimePeriod

Belonging

<Employee>

OrgStructure

［部門］

［組織］

Apply(Explosion)

* *

*

1

* *

*

11

*

*

11

1

**


Tools Implementation Task Force

Pattern

FrameworkMeta Data

Analysis Design Development

Repository BO Library

Atomic Objects

Specification

Tools


Sponsored By Government

• Standardization of Atomic Objects

• Development Common Business Object Platform

• Standardization of Business Object Protocol


CBOP Phase 2


Organization in Phase2President

Exec. Board

Mg’t Board

Acad

emic L

iaison

Research

& S

urvey

Com

pon

ent R

euse

Prom

ote

Con

sum

er Ob

ject

Bu

siness S

up

port

International Liaison

Tools Im

plem

entation

Exec Hearing Committee

Project Review Committee

Organization

BO

Standardization


More Business Oriented

Component Reuse Promote Task ForceCBOP Standard BO

Actual Platform(ATLAS)

CBOP member

CBOP member

Component

Actual Platform(JB)

CBOP member

CBOP member

Component

Reusing

ATLAS Consortium JavaBeans Consortium

Exchanging

Component Development

Customer

CoolPlex

CBOP Standard BO CBOP Standard BO

CBOP


　　　 Distributed Object Platform （ CORBA,ActiveX,JBE)

Transaction Monitor DBMSCommon Services

Business Component

Business Component

Business Component

　　　 Workflow manager

Workflow

ＡＰＩ

　　　　 Standard Business Component Protocol

Standardization of Business Component Protocol


Cooperation

CBOP Japan Information Processing & Development Center

Retail System Development Center

Japan Standards Administration

ＩＳＯ / ＩＥＣ　ＪＴＣ１

ＥＡＮ

ＵＣＣ

OMG

Japan Information Service Association

ＥＲＰ Study & Reserch Forum

ＪＥＣＡＬＳ

Consortium for Distributed Object

ＡＰＱＣ

ＳＣＣ

Information Technology Consortium Co.


BFOP Development Project

12/APR/1999

IT Innovation Inc,. Synergy Research Corp.


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


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 constructi

on 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 organi

zed 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 lo

gic 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 referen

cing to BFOPs.– Managers and developers can identity the pre-requisites in their behavior, policies and business rules before starting devel

opment efforts.

• Promote inter-enterprise collaborations– BFOPs give the modeling foundation for inter-enterprise collaborations such as EC and SCM(Supply Chain Management)


BFOP Architecture

BFOP:Organization Structure

BFOP:Employee Assignment

BFOP Structure BFOP: Organization(SS)

Organization Structure

Organization(SS)

Employee Assignment

<Organization>

Period

OrganizationStructure

<Department>

<Employee>

Assignment

<EnterpriseOrg>

Organization Structure

Employee Assignment

Parametric Collaboration

< EnterpriseOrg >

Period

Assignment

< Employee >

OrganizationStructure

［ Department ］

［ Organization ］

Unfold

* *

*

1

* *

*

11

*

*

11

1

**


The directions in BFOP application

BFOP Structure

Extension to other industries such as

Financial Accounting and Manufacturing

Extension to other industries such as

Financial Accounting and Manufacturing

Applied to Data Centric Approach and/or Object-Oriented Analysis and Design

Applied to Data Centric Approach and/or Object-Oriented Analysis and Design

・ Java, C++, VisualBasic, Enterprise JavaBeans・ Component-based Development Tool ｓ such as COOL:Plex

・ Java, C++, VisualBasic, Enterprise JavaBeans・ Component-based Development Tool ｓ such as COOL:Plex

・ Application Package Business ・ System Integration Business

・ Application Package Business ・ System Integration Business

BFOP PackageBFOP Package

BFOP Implemented Software Component

BFOP Implemented Software Component

Application

Basic

Implementation

The result from the activity CBOP Phase 1(The whole sale industry)


BFOP　 LIST

Layer No. Pattern name oＤｅｓｃｒｉｐｔｉｎ

1010 Master & Detail A Detail refers to zero or one Master. A Master should be referred by many Details. For example Customer - Order , Item Type - Item.

1020 Association An Association class exists between two classes. Stock - Warehouse and Item.

1030 Association- 3 An Association exists for three classes. Price - Item , Supplier , Period.

1040 Dynamic Hierarchical Structure It's same as tree structure. Organization of company.

1050 Direct ed G ra p hIt's same as network structure. Route of delivery.

1060 DAG(Assiclic Directed Graph) This is extended from DAG. This is not allowed loop. Built of Material.

1070 Header & Detail Parent and children. Order - Order Line . Bank - Branch.

1080 Stock & Flow This is restricted DAG. This does not have multiple levels. Transpotation - Location. Currency - Excange Rate.

1090 Period Period has From Date and To Date. Otherwise From (To) Date and Period notify TO (From) Date.

1110 Transaction Recor dMany Transactions are summarized by one Time Bucket . Sales - Closing Period.Sale Balance - Financial year.

2010 Correspondent - Transaction Correspondent has many Transactions.

2020 Item- Stock- Place Item and Stock Place keep Stock. As Stock Place , Warehouse , Rack or Lot number are available.

2030 Employee Assignment An Employee can be assinged multiple sections.

2040 Organization Structure Organization can be kept in each period.

2050 Transaction- Transaction Line- Item A Transaction can handle many Items , because of Item Line. Shipping Header - Shipping Detail - Item.

2060 Sales Order- Sales Order Line- Item This is specialized 2050 for sales order.

2070 Purchase Order- Purchase Order Line- Item This is specialized 2050 for purchase order.

2080 Closing Many Transactions are summarized by one Time Bucket. And these summary becomes Closing.

2090 Paying or Receiving Paying (Receiving) are summarized by Paying (Receiving) Date.

2100 Settl e me n t Closing and Paying(Receiv ing ) are r el a t ed by Pe ri o d , a n d ke e p ba l a nc e .

2110 Settlement for Receiving Closing for sales. Invoice will be issued.

2120 Settlement for Paying Closing for Purchase.

2130 Sales Order & Purchase Order(SS) Sales Order and Purchase Order are related by same Item.

2140 Tranpo r t (S S ) Transportation from one place to another one place. Shipping , Goods Receiving , Moving between two Warehouses , etc.

2150 Direct Tranport(SS) Purchase Order will be created by Sales Order. These Shipping and Receiving will be related automatically.

2160 Item Information(SS) Who supply , how to make order , etc.

2170 Daily Inventory(SS) Balance of Input and Output for Item is summarized by each period.

2180 Settlement for Receiving & Paying(SS) Paying and Receiving are related by one Period.

2190 Organization(SS) Organization and Assignment by Period.

2200 Product Configuration(SS) Set Item configuration.

3010 Price by Correspondent Item Price is defined by Customer(or Supplier).

3020 Price by Period Item Price is defined by Date.

3030 Price by Correspondent／Ｐｅｒｉｏｄ Item Price is defined by Customer(or Supplier) by Date.

3040 Employee- Role Employee can have muitiple rolls.

3050 Employee Role Difinition(SS) Roll has an object what is managed. Purchase by supplier. Sales by area. Support by Item.

OPTION

UNIT

BASIC


BFOP Example: 1080 Stock & Flow

n BFOP Id: 1080n BFOP Name: Stock & Flown BFOP Substitution: Nonen Parameters: <Source>,<Flow>,<Sink>n Rev. 1

<Flow>

-<flowQuantity> : Quantity

<Source> <Sink>

1..11..1

Stock

-<initialLevel> : Quantity-<accumulatedInput> : Quantity-<accumulatedOutput> : Quantity /<currentLevel> : Quantity

addFlow(flow:Flow)post

flow.source.accumulatedInput = flow.source.accumulatedInput@pre + flow.flowQuantityflow.sink.accumulatedOutput = flow.sink.accumulatedOutput@pre + flow.flowQuantity

removeFlow(flow:Flow)post

flow.source.accumulatedInput = flow.source.accumulatedInput@pre @pre - flow.flowQuantityflow. sink.accumulatedOutput = flow. sink.accumulatedOutput@pre - flow.flowQuantity「「


Pattern & Components

Industry

Primatives Technology

Foundation

BusinessFundamentals

Operational

BO Standard DevelopingTask Force

BO Standard DevelopingTask Force

ComponentsTask Force

ComponentsTask Force

Tool ImplementationTask Force

Tool ImplementationTask Force


Thank You

[email protected]

http://www.cbop.gr,jp


======= SPONSORS =======

(in alphabetical order)

CBOP-OMG Joint Workshopon Business Objects

May 20, 1999Tokyo, Japan

======= SUPPORTERS ======= Japan Information Service Industry Association The Distribution Systems Research Institute

Documents

Hajime Horiuchi, Managing Director, CBOP