Presentation (1.51 MB)

18
Austrian Research Centers GmbH - ARC 7. Juni 2022 Modeling inter- organizational business processes Rainer Schuster Studio Digital Memory Engineering UN/CEFACT's Modeling Methodology and UN/CEFACT's Core Components

description

 

Transcript of Presentation (1.51 MB)

Page 1: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC 10. April 2023

Modeling inter-organizational business processes

Rainer Schuster

Studio Digital Memory Engineering

UN/CEFACT's Modeling Methodology andUN/CEFACT's Core Components

Page 2: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

Why business process modeling?

Combining two worlds of SOA invitation for a dialogue between e-business world and geo-spatial world finding commonness reference architectures, intersections between different domains etc.

our contribution business process standards and business information standards from a

major international standardization initiative

2

April 10, 2023

Page 3: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

3

April 10, 2023

Business process classification

Business-to-Business (B2B) common business processes e.g. request geo data from geo data provider often no long term relationships established need for a flexible and scalable architecture

Business-to-Government (B2G) should work like B2B e.g. Waste Management, Governmental Aids, Financial Services

Business

Government

Citizen

G2G

B2C

C2CB2B

G2CB2G

Page 4: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

4

10. April 2023

We are going to talk about …

UN/CEFACT‘s Modeling Methodology (UMM)&

Core Components

Page 5: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

5

April 10, 2023

UN/CEFACT – United Nations Center for Trade, Facilitation and Electronic Business

UN/EDIFACT

ebXML

UMM & CC

UN Layout Key

1970

1980

1990

2000

2010

Page 6: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

6

April 10, 2023

UN/CEFACT‘s Modeling Methodology (UMM)

Customizing UML for modeling B2B Independent of the IT platform, concentrates on business semantics Describes a choreography from a global perspective UML Profile: Stereotypes, Tagged Values, Constraints on top of the UML

Meta Model ~ 40 stereotypes defined in the meta model

UMMUMM

BDVBusiness

Domain View

BDVBusiness

Domain View

BRVBusiness

Requirements View

BRVBusiness

Requirements View

BTVBusiness

Transaction View

BTVBusiness

Transaction View

Page 7: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

7

April 10, 2023

ad Announce Waste Transport

Responder :Notifiee

«BusinessTransactionSwimlane»

Requestor :Notifier

«BusinessTransactionSwimlane»

«RequestingInformationEnvelope»

:WasteMovementFormEnvelope

«RespondingBusinessActivity»Process Waste Movement Form

«RequestingBusinessActivity»Notify Waste Transport

«InformationEnvelope»

:WasteMovementResponseEnvelope

[Success][Failure]

ad Manage Waste Transport

«BusinessTransactionActivity»Announce Transport Arrival

«BusinessTransactionActivity»Announce Waste Transport

UMM by example - BTV

BTUC

BCUC

<<mapsTo>>

<<mapsTo>>

ud Manage Waste Transport

Notifier Notifiee

«BusinessCollaborationUseCase»Manage Waste

Transport

«BusinessTransactionUseCase»Announce

Transport Arrival

«BusinessTransactionUseCase»Announce Waste

Transport

«include»«include»

«participates»«participates»

Page 8: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

Capture the requirements of an inter-organizational business process from a global perspective

Establish a common UML based model describing the business process Use the model to automatically derive machine executable code (BPEL or

BPSS) for a service oriented architecture (SOA) add core component logic (business information)

8

April 10, 2023

Advantages through the usage of UMM

Business Partner A

Business Partner B

Capture Requirements

Core Components

Automatically derive

BPELBPSS

Service Oriented

Architecture

use in

UMM-Model

<XML>

Page 9: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

9

April 10, 2023

Standardizing the exchanged data

SOAP message

Importer

announce waste transport

announce transport arrival

check waste statusEnterprise Application

Exporter

Enterprise Application

Enterprise Application

Enterprise Application

WSDL

WSDLWSDL

WSDL

WSDL

SOAP message

SOAP message

UDDI registry

Page 10: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

10

April 10, 2023

Standardizing the exchanged data

SOAP message

Importer

announce waste transport

announce transport arrival

check waste statusEnterprise Application

Exporter

Enterprise Application

Enterprise Application

Enterprise Application

WSDL

WSDLWSDL

WSDL

WSDL

SOAP message

SOAP message

UDDI registry

SOAP Message

SOAP Body

SOAP Header

Message Body

Page 11: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

11

April 10, 2023

Core Components Problem domain

Information exchanged in business processes in a service oriented context

UN/CEFACT provides a generic solution Core Components Technical Specification (CCTS) Almost no tool support possible - CCTS are standardized as spread

sheets

UML profile for core components Seamless integration into UML modeling tools possible Seamless integration into e.g. process specific models possible (UMM) ARC are actively participating in the standardization

Page 12: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

12

April 10, 2023

Core Components

Are the central building blocks of the Core Component Technical Specification (CCTS)

Platform independent Used to create shared libraries of interoperable business documents The ontological base of the CCTS is the United Nations Trade Data

Element Dictionary (UN/TDED) Initially started as part of ebXML standards suite Now a dedicated project independent of ebXML

Page 13: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

13

April 10, 2023

A Core Component Example

«ACC»TransportMeans

«BCC»+ Identification: Identifier [0..*]+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»TransportMode

«BCC»+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»Party

«BCC»+ Access Rights: Code [0..*]+ Classification: Code [0..*]+ Description: Text [0..*]+ Identification: Identifier [0..*]+ Language: Code [0..*]+ Name: Text [0..*]+ Role: Code [0..*]+ Type: Code [0..*]

«ACC»MovementForm

«BCC»+ TransportNumber: Identifier+ IdentificationNumber: Identifier

«ACC»Period

«BCC»+ Complete: Date Time [0..1]+ Description: Text [0..*]+ Duration: Measure [0..*]+ End: Date Time [0..1]+ Identification: Identifier [0..*]+ Inclusive: Indicator [0..1]+ Open: Indicator [0..1]+ Season: Code [0..*]+ Start: Date Time [0..1]

+Movement

«ASCC»

+Carrier

«ASCC»

+Transport

«ASCC»

+Movement

«ASCC»

Page 14: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

14

April 10, 2023

Business Information Entities

«ABIE»Waste_MovementForm

«BBIE»+ TransportNumber: IdentifierNumber+ IdentificationNumber: IdentifierNumber

«ABIE»Period

«BBIE»+ End: DateTime+ Start: DateTime

«ABIE»TransportMeans

«BBIE»+ Identification: Identifier

«ABIE»TransportMode

«BBIE»+ Type: Text+ TypeCode: Code

«ABIE»Party

«BBIE»+ Description: Text+ Identification: PartyIdentifier

+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»

Page 15: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

15

April 10, 2023

Interdependency between Core Components and Business Information Entities

«ACC»TransportMeans

«BCC»+ Identification: Identifier [0..*]+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»TransportMode

«BCC»+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»Party

«BCC»+ Access Rights: Code [0..*]+ Classification: Code [0..*]+ Description: Text [0..*]+ Identification: Identifier [0..*]+ Language: Code [0..*]+ Name: Text [0..*]+ Role: Code [0..*]+ Type: Code [0..*]

«ACC»MovementForm

«BCC»+ TransportNumber: Identifier+ IdentificationNumber: Identifier

«ACC»Period

«BCC»+ Complete: Date Time [0..1]+ Description: Text [0..*]+ Duration: Measure [0..*]+ End: Date Time [0..1]+ Identification: Identifier [0..*]+ Inclusive: Indicator [0..1]+ Open: Indicator [0..1]+ Season: Code [0..*]+ Start: Date Time [0..1]

+Movement

«ASCC»

+Carrier

«ASCC»

+Transport

«ASCC»

+Movement

«ASCC»

«ABIE»Waste_MovementForm

«BBIE»+ TransportNumber: IdentifierNumber+ IdentificationNumber: IdentifierNumber

«ABIE»Period

«BBIE»+ End: DateTime+ Start: DateTime

«ABIE»TransportMeans

«BBIE»+ Identification: Identifier

«ABIE»TransportMode

«BBIE»+ Type: Text+ TypeCode: Code

«ABIE»Party

«BBIE»+ Description: Text+ Identification: PartyIdentifier

+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»

Core Components (CC) Business Information Entities (BIE)

BIEs are derived from CCs by restriction

Page 16: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

16

April 10, 2023

Derivation of XSD artifacts

«ABIE»Waste_MovementForm

«BBIE»+ TransportNumber: IdentifierNumber+ IdentificationNumber: IdentifierNumber

«ABIE»Period

«BBIE»+ End: DateTime+ Start: DateTime

«ABIE»TransportMeans

«BBIE»+ Identification: Identifier

«ABIE»TransportMode

«BBIE»+ Type: Text+ TypeCode: Code

«ABIE»Party

«BBIE»+ Description: Text+ Identification: PartyIdentifier

+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»

Business Information Entities (BIE)

UN/CEFACTNaming and Design Rules

<xsd:complexType name="Waste_MovementForm"> <xsd:sequence> <xsd:element name= "TransportNumber" type="udt1:IdentifierNumber"/> <xsd:element name="IdentificationNumber" type="udt1:IdentifierNumber"/> <xsd:element name="Waste_Transport_Period" type="bie1:PeriodType"/> <xsd:element name="Waste_Movement_TransportMeans" type="bie1:TransportMeansType"/> <xsd:element name="Waste_Carrier_Party" type="bie1:PartyType"/> <xsd:element name="Waste_Movement_TransportMode" type="bie1:TransportModeType"/> </xsd:sequence></xsd:complexType>

Page 17: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

17

April 10, 2023

Conclusion & Summary

We showed how

UMM can be used to model inter-organizational business processes

the UML Profile for Core Components can be used to model the information exchanged in an inter-organizational business process

the UMM Add-In developed by ARC supports the modeler in modeling UMM and CCTS

we expect that a dialogue between the geo-spatial and the e-business modeling initiatives could result in improvements and wider international acceptance of SOA standards

Page 18: Presentation (1.51 MB)

Austrian Research Centers GmbH - ARC

18

April 10, 2023

Thank you for your attention<Lecturer>

<Name>Rainer Schuster</Name><Company>Austrian Research Centers - Research Studios Austria</Company><Department>Intelligent Business Process Management Group</Department><Address>

<Street>Thurngasse 8/20</Street><ZIP>1090</ZIP><City>Vienna</City><Country>Austria</Country>

</Address><Contact>

<Telephone>+43 1 585 0537 12 </Telephone><Email>[email protected]</Email><Email>[email protected]</Email>

<Http>http://ummaddin.researchstudio.at</Http></Contact><? Presentation status=“questions” ?>

</Lecturer>