Technical Framework Technical Framework Technical Framework - PowerPoint PPT Presentation

Technical Framework Technical Framework Technical Framework Supporting eBusiness eBusiness Standards Standards Supporting eBusiness Standards Supporting Christian Huemer TMG Chair

Requirements for interoperability between enterprises • Which documents are exchanged between enterprises? • Common definition of the artifacts which are exchanged between enterprises • Business document standards • CCTS, UPCC, NDR, UCM • How are documents exchanged between enterprises? • Common definition in which order documents are exchanged • Global process choreography • UMM, REA, (UCM in the future) 2

Meta Model sickness Health warning • If you want to learn modeling, it is not a good idea to start with the meta model • If you are an experienced modeler the meta model serves as reference • A tool builder must implement the meta model to provide the modeling environment for the modeler 3

Overview of Core Component related UN/CEFACT specifications Core Component Technical UML Profile for Core Specification (CCTS) Components (UPCC) Core Data Type Catalogue based on conforms to derive use core component definitions Core Component Library (CCL) XML-Schema conforms to Naming and Design Rules (NDR) 4 define unambiguous derivation rules

UN/CEFACT’s Core Components – Definition of reusable building blocks • Semantic building blocks for the definition of business document data • Context free – reuse in multiple business sectors • Customization of generic core components to specific business sectors and application domains 5

UN/CEFACT’s Core Components – Reuse of building blocks Core Components Business document 6

Creation and use of building blocks UN/CEFACT Core Component Library (CCL) Company A Company C Company B Company X 7

Reduction of complexity through reusable document Article building blocks Article ID Description Price Color Weight Catalog_Article Order_Article Invoice_Article Article ID Description Price Color Weight Contextualization by omitting non-used elements 8

LineItem ACC - Number - BCC : Text CDT Core components in one slide - Amount : Quantity - BCC CDT • Identification of objects • Identification of object properties - ASCC - item Article ACC • Two types of properties - BCC - ArticleNumber : Text CDT • Simple properties (text, number, date) : CDT Text - Description - BCC • Complex properties (other objects) - Price - BCC : CDT Amount - Color : Text CDT - BCC CDT - BCC : Quantity - Weight • Object type = A ggregate C ore C omponent • Simple Property = B asic C ore C omponent • Simple Property Data Type = C ore D ata T ype • Complex Property = AS ociation C ore C omponent 9

From Core Components to Business Information Entities • Core Components act as conceptual models that are used to define business information entities (BIE) • Business Information entities are created • by the application of context • by restricting a generic core component • Business Information Entities and Core Components are complementary in many respects • A Business Information Entity must always be based on a Core Component Core Business based on Component Information Entity 10

ABIE LineItem - BBIE - Number : Text BDT - Amount : Quantity - BBIE BDT Business Information Entities in one slide • Core Components in a specific context - item - ASBIE • Qualifiers help to distinguish BIEs Article ABIE - BBIE Text BDT • Two different type of properties - Chemical_ArticleNumber : - Description - BBIE : BDT Text • Simple properties (text, number, date) - Price - BBIE : Amount BDT • Complex properties (other objects) • Object type = A ggregate B usiness I nformation E ntity • Simple Property = B asic B usiness I nformation E ntity • Simple Property DT = B usiness D ata T ype • Complex Property = AS ociation B usiness I nformation E ntity 11

Overview of Core Component related UN/CEFACT specifications Core Component Technical UML Profile for Core Specification (CCTS) Components (UPCC) Core Data Type Catalogue based on conforms to derive use core component definitions Core Component Library (CCL) XML-Schema conforms to Naming and Design Rules (NDR) 12 define unambiguous derivation rules

A UML Profile for Core Components (UPCC) • UPCC goals • Define UML Profile for CCTS to allow for an unambiguous representation of Core Components in UML • Support validation of structure and semantics of CCTS compliant information models • Provide an unambiguous basis for the derivation of XML Schema artifacts • Make CCTS information modeling available to a broad user community • Help to improve model interchange between UML tools of different vendors 13

Overview of Core Component related UN/CEFACT specifications Core Component Technical UML Profile for Core Specification (CCTS) Components (UPCC) Core Data Type Catalogue based on conforms to derive use core component definitions Core Component Library (CCL) XML-Schema conforms to Naming and Design Rules (NDR) 14 define unambiguous derivation rules

The Open-edi Reference Model ISO 14662 Business Transactions UN/CEFACT's Modeling Business Operational View Business Operational comply Methodology (UMM) with View Business aspects related standards UML Profile for Core of business transactions Components covered (UPCC) viewed by as transformed to Functional Service View comply Information technology XML Schema with Functional Service aspects of business Web Services View transactions Windows Workflow related standards covered … by

Transformation concepts Business Information Entity Concept XML Schema Construct xsd:simpleType OR Business Data Type (BDT) xsd:complexType Basic Business Information Entity (BBIE) xsd:element Local Declaration xsd:complexType Aggregate Business Information Entity (ABIE) xsd:element Global Declaration Association Business Information Entity (ASBIE) xsd:element Local Declaration 16

Resulting XML files Business Document Definitions Root XML Schema File includes includes BIE XML Schema File includes BDT XML Schema File Basic Business Information Entity (BBIE) Business Data Type (BDT) Association Business Information Entity (ASBIE) Aggregate Business Information Entity (ABIE) 17

Example for a business document schema D D O C e n e d n a L b a y f r r i i i D e n e d n A B E ︵ « » f i i I M A « » B E m L b a y A + a h e d B E B ︶ ︳ E r r c L b a y u s n e s s n o a o n n y I i W t t r r r M m m I i i I f t i t i t F a e o e e n o s v r t t W m C L b a y a s e o n s g n e n r r : : t t M i i A S A « » ︳ ︳ 1 * . . W W + a e d e n a o n a e d e n e 0 s c s * t I t f t : t I t f r [ . . ] i i i i i A S B E « » I ︳ W + a s e n c u d e d 1 * t I . . l A B E ︵ « » ︶ I m B E B ︳ E L b a y u s n e s s n o a o n n y L b a y r r r r r I i i I f t i t i t i : : W m m C a s e o n s g n e n e t t I t i B B E « » ︳ ︳ I W W W M C + a e ︳ h a g e a b e e g h a e e a u e ︳ 0 s s s r r * t l i t : t [ . . ] ︳ W W m D C + ︳ V F A ︳ W a s e e c a e d a u e o a a g e a s e o u n 0 1 m r r r r t l l i : t t [ . . ] + a s e p o a o n r t I t t i W W m m D V C A + ︳ F ︳ a s e e c a e d a u e o u s o s a s e o u n 0 1 t r r t : t t [ . . ] l l W W m D V S A A B E + a e ︳ e a e d a u e F o a ︳ a e o u n 0 1 A S B E ︵ « » s c s c s s « » 1 t r r t t t : t t [ . . ] I l l i i I W W m D T B E B E + a e ︳ e e n u o n a ︳ e e 0 L b a u ︶ n e n o ︳ a o n n s v y s c s s x y s s s y r r * ︳ r r r t l i I t t i : t t [ . . ] I i i I f t i t i t W W W m M G W C ︳ V ︳ + a s e o s s o u e a s e e a s u e 0 L b a y a s e o u n y * r r + a e T a n r r r t l : t [ . . ] s s i : : t t r t i t W W W G M + ︳ ︳ a s e o s s e g h a s e e a s u e 0 * t r t : t r [ . . ] i B B E W W A S B E « » ︳ ︳ « » I + a e ︳ d e n a o n a e ︳ d e n e 0 I 0 s c s * * . . t I t f t : t I t f r [ . . ] i i i i i W W ︳ W W + a e ︳ d e n a o n a ︳ e d e n e 0 m s c s r * t I t f t : t I t f [ . . ] + a e ︳ n o a o n a e T e ︳ 0 i i i i i s s x r * t I f t i : t t [ . . ] W W W E m + N a s e x p o T W W + a e a e a e e 0 m t r t s s x * ︳ V ︳ A t : t t [ . . ] + a s e n s u a n c e a u e a s e o u n 0 1 r t I l : t t [ . . ] W W m A 18 + ︳ ︳ a s e n v o c e a s e o u n 0 * A S B E t I : t t [ . . ] « » i 1 I W W W M N + a e e e g h a e e a u e 0 s s s * t t t : t r [ . . ] i O S 0 1