Cultural Heritage in REGional NETworksCultural Heritage in REGional NETworks

REGNETREGNET

T2.4: Business Process Re-engineering

July 2002 REGNET review

2

Global visionGlobal vision

Four viewpoints:Business (process): T1.6Information system (functions, macroscopic flows): T2.4Software systems (software, component, project,…): T2.2Physical systems: Infrastructure and enterprise network elements (hardware machines, …): T2.2

Business representation

IS representation

Zone 1

Zone 2

FLUX

Zone 3

Software systems representation

Physical infrastructure representation

BTS

July 2002 REGNET review

3

Objectives (1/2)Objectives (1/2)

1. Complete and detailed specifications of the selected processes to be implemented in the version 2 of REGNET System.

PARTNERS : MUSEUM : TINC and MUS. ARCHIVE and LIBRARY : IMAC and AIT. ART GALLERY : ICCS .

July 2002 REGNET review

4

Objectives (2/2)Objectives (2/2)

2. Translation of the specifications provided in UML language (class diagram).

3. Prepare ebXML deployment

PARTNER :

UML Modelling : VALT.

July 2002 REGNET review

5

Methodology (1/3)Methodology (1/3)

• The previous step - Business Processes Modelling : In the WP1 (task T1.6), we defined, organised and mapped (use case diagram) the business of the cultural heritage domain.This organizational context for the system is presented in the deliverable D3.

July 2002 REGNET review

6

Methodology (2/3)Methodology (2/3)

• The 1st step – The detailed specifications use cases of REGNET’s System :

• The content providers selected the use cases to be implemented in the version 2 of REGNET.

• Then, for each use case or sub use case, the workflow of the dialog between the actors and the REGNET’s System was expressed.

July 2002 REGNET review

7

Methodology (3/3)Methodology (3/3)

• 2nd step : the object oriented model.

• From the use cases specifications, the domain (or sub-domain) model is built.

Class diagram which could be completed by collaboration diagrams.

July 2002 REGNET review

8

Museum domainMuseum domain

Collection Management Class

Tourism Class

Education class

Recreational economics class

Services Class

The Museum Domain has been splitted into 5 sub-domains

For each sub-domains Use Cases have been specified

July 2002 REGNET review

9

Use Case SpecificationsUse Case Specifications

Auctioneer

(from Business actors)

Collector

(from Business actors)

Cultural institution

(from Business actors)

borrow an object

acquire an object

dispose of an object

lend out an object

Curator

(from Museum Actors)

Insurance Company

(f rom Business actors)

insure an object

manage an exhibition Publishing company

(from Business actors)

July 2002 REGNET review

10

InComingLoan- enteredDate- enteredBy

OutGoingLoan- deactivatedDate- deactivatedBy

LoanExtension- extensionEndDate- description

Notes

LoanAgreement- availability

Loan- loanNumber- loanPurpose- startDate- endDate- displayStartDate- displayEndDate- requestedBy- dateRequest- approvedBy- dateApproval- lender

0..n0..n

0..n

1

0..n

1

is marks with

11

is governed byLoanRequestState

LoanRequest- startDate- endDate

1 0..11 0..1

results

1 0..11 0..1

results

11

LoanRequestRejected- reason

LoanRequestAccepted

From Use Case to Class From Use Case to Class Diagram Diagram ( i.e. : Loan Category)( i.e. : Loan Category)

Attribut

Concept

Association

July 2002 REGNET review

11From Class Diagram to From Class Diagram to CategoryCategory

Exhibition<<category>> Location

<<category>>

Exhibition Location1 11 1is held at

July 2002 REGNET review

12Example of Categories Example of Categories identified from Collection identified from Collection Management Use CasesManagement Use Cases

Object<<category>>

Loans<<category>>

Shipping<<category>>

Holds information about the objects in the collection, including: cataloguing, registration, location, valuations

Tracks incoming and outgoing loans, and links directly to Constituents and Objects categories.

Arrangements for moving objects from one location to another, linked directly to Loan and Exhibition Categories

July 2002 REGNET review

13T2.4 - Business PROCESS (Re-T2.4 - Business PROCESS (Re-engineering).engineering).

Next step: integration of Business Processes into ebXML registry

July 2002 REGNET review

14

Query about Company X

Request Company X’s Scenario

Company X’s Scenario

Company X’s Profile

Submit CPA

Accept CPA

ebXML BP Model

ebXML BO Library

ebXML BP Model

ebXML BO Library

Request ebXML specifications1

ebXML specifications detail

3

2

Build local system implementation

Register scenarios and implementation detailsRegister company business profile

6

7

8

9

10

Confirm profile and scenarios accepted

11

45

12 Scenarios

Profiles

Specifications

July 2002 REGNET review

15Request Loan

Application Form

Query Object information

Sign and send Loan Agreement

Schedule Object Receipt

Receive Object

Return Object

Request Loan

Check loan conditions

Receive and sign Loan Agreement

Analyse loan request

[ Failure ]

[ Success ]

UN/CEFACT UMM:Business Processas activity diagram

LenderBorrower

July 2002 REGNET review

16

Conversion UML -> XMLConversion UML -> XMLBusiness process definitionsXML Schema and DTD generationPopulate classification scheme

XML Schema

XMI(MOF.DTD)

TransformationRules

XML Process Definition

Populate Classification

Scheme

July 2002 REGNET review

17

<?xml version="1.0" encoding="UTF-8"?><!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Dubois (Valtech) --><ProcessSpecification version="1.0" uuid="" name="Simple" xmlns="http://www.ebxml.org/BusinessProcess" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ebxml.org/BusinessProcessD:\Projets\CPPETB~1\ebBPSS.xsd">

<BusinessDocument name="Loan Application Form Request"/><BusinessDocument name="Loan Application Form"/><BusinessDocument name="Request ACK"/><BusinessDocument name="Loan ACK"/><BusinessDocument name="Loan rejection"/><BusinessDocument name="Object Information Request Form"/><BusinessDocument name="Object Description"/><BusinessDocument name="Loan Agreement"/><BusinessDocument name="Loan Agreement Receipt ACK"/><BusinessDocument name="Loan Agreement ACK"/><BusinessDocument name="Receipt Schedule"/><BusinessDocument name="Receipt Schedule ACK"/><BusinessDocument name="Shipment Notification"/><BusinessDocument name="End of business Document"/><!--**** The Binary Collaborations ****--><BinaryCollaboration name="BorrowLend">

<InitiatingRole name="Borrower"/><RespondingRole name="Lender"/><BusinessTransactionActivity name="Request Loan Application Form" businessTransaction="Request Loan Application Form"

fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/><BusinessTransactionActivity name="Request Loan" businessTransaction="Request Loan" fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/><BusinessTransactionActivity name="Analyse Loan Request" businessTransaction="Analyse Loan Request" fromAuthorizedRole="Lender"

toAuthorizedRole="Borrower"/><BusinessTransactionActivity name="Query Object Information" businessTransaction="Query Object Information" fromAuthorizedRole="Borrower"

toAuthorizedRole="Lender"/><BusinessTransactionActivity name="Sign and Send Loan Agreement" businessTransaction="Sign and Send Loan Agreement"

fromAuthorizedRole="Borrower" toAuthorizedRole="Lender"/> ……

BPSS: XML versionBPSS: XML version

July 2002 REGNET review

18CPPCPP

<?xml version="1.0" encoding="UTF-8"?><!-- edited with XML Spy v4.3 U (http://www.xmlspy.com) by Dubois (Valtech) --><tp:CollaborationProtocolProfile xmlns:tp="http://www.ebxml.org/namespaces/tradePartner" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" tp:schemaLocation="http://www.ebxml.org/namespaces/tradePartnerD:\Projets\CPPETB~1\cpp-cpa-v1_0.xsd">

<tp:PartyInfo><tp:PartyId>123456789</tp:PartyId><tp:PartyRef/><tp:CollaborationRole tp:id="N00">

<tp:ProcessSpecification tp:name="BorrowLend" xlink:type="simple" xlink:href="http://www.MuseumURL/BorrowLend.xml"/><tp:Role tp:name="Borrower"/><tp:ServiceBinding tp:channelId="N04" tp:packageId="N0402">

<tp:Service>IssueRequestForLoan</tp:Service></tp:ServiceBinding>

</tp:CollaborationRole><tp:Certificate tp:certId="N03">

<ds:KeyInfo/></tp:Certificate><tp:DeliveryChannel tp:channelId="N04" tp:transportId="N05" tp:docExchangeId="N06">

<tp:Characteristics/></tp:DeliveryChannel><tp:Transport tp:transportId="N05">

<tp:SendingProtocol>HTTP</tp:SendingProtocol><tp:ReceivingProtocol>HTTP</tp:ReceivingProtocol><tp:Endpoint tp:uri="http://www.museumURL/servlets/ebXMLHandler"/>

</tp:Transport><tp:DocExchange tp:docExchangeId="N06">

<tp:ebXMLBinding/></tp:DocExchange>

</tp:PartyInfo><tp:Packaging tp:id="N0402">

<tp:ProcessingCapabilities tp:parse="true" tp:generate="true"/><tp:SimplePart tp:mimetype="text/xml"/>

</tp:Packaging></tp:CollaborationProtocolProfile>

July 2002 REGNET review

19

Registry systems can give you information about many types of ebXML and even non-ebXML documents.

- CPP’s and CPA’s- Business Process Documents (BPSS, others)- Core Components and CC Aggregates- Business Information Entities and Aggregates- DTD’s and Schemas (Assembly documents)- Programming artifacts

ebXML RegistryebXML Registry

July 2002 REGNET review

20

Negotiating an agreementNegotiating an agreement

Find registry and search for partnersExamine CPPAscertain compatibility of business process and technical specificationsProduce Collaboration Protocol Agreement

Conditions under which two partners will conduct business transactions together

Modify application

July 2002 REGNET review

21

ebXML registry deploiementebXML registry deploiement

We have deployed ebxmlrr registry (open source initialy from SUN): http://ebxmlrr.sourceforge.netPreliminary populated by some business processesOne of the first implementation in Europe