REGNET Meeting Sofia T2.4

1
T2.4 Business Process Re-engineering
2
Global vision
Business representation

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

FLUX
Zone 2
Zone 3
Zone 1
IS representation
Software systems representation
Physical infrastructure representation
3
Objectives (1/2)

• 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 .

4
Objectives (2/2)

• Translation of the specifications provided in UML
  language (class diagram).
• Prepare ebXML deployment
• PARTNER
• UML Modelling VALT.

5
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.

6
Methodology (2/3)

• The 1st step The detailed specifications use
  cases of REGNETs 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
  REGNETs System was expressed.

7
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.

8
Museum domain
The Museum Domain has been splitted into 5
sub-domains
For each sub-domains Use Cases have been specified
9
Use Case Specifications
10
From Use Case to Class Diagram ( i.e. Loan
Category)
Attribut
Concept
Association
11
From Class Diagram to Category
12
Example of Categories identified from Collection
Management Use Cases
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
13
T2.4 - Business PROCESS (Re-engineering).

• Next step integration of Business Processes into
  ebXML registry

14
Museum X
Request ebXML specifications
1
2
ebXML specifications detail
ebXML Repository
Register scenarios and implementation
details Register company business profile
ebXML Software
4
ebXML BO Library
5
Confirm profile and scenarios accepted
3
ebXML BP Model
Specifications
Build local system implementation
Profiles
Query about Company X
12
7
Accept CPA
9
Scenarios
Company Xs Profile
Submit CPA
8
6
Request Company Xs Scenario
11
Company Xs Scenario
10
ebXML Software
ebXML BO Library
Museum Y
ebXML BP Model
15
Borrower
Lender
UN/CEFACT UMM Business Process as activity
diagram
16
Conversion UML -gt XML

• Business process definitions
• XML Schema and DTD generation
• Populate classification scheme

XML Schema
XML Process Definition
Transformation Rules
XMI (MOF.DTD)
Populate Classification Scheme
17
BPSS XML version
lt?xml version"1.0" encoding"UTF-8"?gt lt!--
edited with XML Spy v4.3 U (http//www.xmlspy.com)
by Dubois (Valtech) --gt ltProcessSpecification
version"1.0" uuid"" name"Simple"
xmlns"http//www.ebxml.org/BusinessProcess"
xmlnsxsi"http//www.w3.org/2001/XMLSchema-instan
ce" xsischemaLocation"http//www.ebxml.org/Busin
essProcess D\Projets\CPPETB1\ebBPSS.xsd"gt ltBusi
nessDocument name"Loan Application Form
Request"/gt ltBusinessDocument name"Loan
Application Form"/gt ltBusinessDocument
name"Request ACK"/gt ltBusinessDocument
name"Loan ACK"/gt ltBusinessDocument name"Loan
rejection"/gt ltBusinessDocument name"Object
Information Request Form"/gt ltBusinessDocument
name"Object Description"/gt ltBusinessDocument
name"Loan Agreement"/gt ltBusinessDocument
name"Loan Agreement Receipt ACK"/gt ltBusinessDocu
ment name"Loan Agreement ACK"/gt ltBusinessDocumen
t name"Receipt Schedule"/gt ltBusinessDocument
name"Receipt Schedule ACK"/gt ltBusinessDocument
name"Shipment Notification"/gt ltBusinessDocument
name"End of business Document"/gt lt!-- The
Binary Collaborations --gt ltBinaryCollaboratio
n name"BorrowLend"gt ltInitiatingRole
name"Borrower"/gt ltRespondingRole
name"Lender"/gt ltBusinessTransactionActivity
name"Request Loan Application Form"
businessTransaction"Request Loan Application
Form" fromAuthorizedRole"Borrower"
toAuthorizedRole"Lender"/gt ltBusinessTransaction
Activity name"Request Loan" businessTransaction"
Request Loan" fromAuthorizedRole"Borrower"
toAuthorizedRole"Lender"/gt ltBusinessTransaction
Activity name"Analyse Loan Request"
businessTransaction"Analyse Loan Request"
fromAuthorizedRole"Lender" toAuthorizedRole"Borr
ower"/gt ltBusinessTransactionActivity
name"Query Object Information"
businessTransaction"Query Object Information"
fromAuthorizedRole"Borrower" toAuthorizedRole"Le
nder"/gt ltBusinessTransactionActivity name"Sign
and Send Loan Agreement" businessTransaction"Sign
and Send Loan Agreement" fromAuthorizedRole"Borr
ower" toAuthorizedRole"Lender"/gt
18
CPP
lt?xml version"1.0" encoding"UTF-8"?gt lt!--
edited with XML Spy v4.3 U (http//www.xmlspy.com)
by Dubois (Valtech) --gt lttpCollaborationProtocol
Profile xmlnstp"http//www.ebxml.org/namespaces/
tradePartner" xmlnsxsi"http//www.w3.org/2001/XM
LSchema-instance" xmlnsxlink"http//www.w3.org/1
999/xlink" xmlnsds"http//www.w3.org/2000/09/xml
dsig" tpschemaLocation"http//www.ebxml.org/nam
espaces/tradePartner D\Projets\CPPETB1\cpp-cpa-v
1_0.xsd"gt lttpPartyInfogt lttpPartyIdgt123456789lt
/tpPartyIdgt lttpPartyRef/gt lttpCollaborationR
ole tpid"N00"gt lttpProcessSpecification
tpname"BorrowLend" xlinktype"simple"
xlinkhref"http//www.MuseumURL/BorrowLend.xml"/gt
lttpRole tpname"Borrower"/gt lttpServiceBi
nding tpchannelId"N04" tppackageId"N0402"gt
lttpServicegtIssueRequestForLoanlt/tpServicegt lt
/tpServiceBindinggt lt/tpCollaborationRolegt ltt
pCertificate tpcertId"N03"gt ltdsKeyInfo/gt
lt/tpCertificategt lttpDeliveryChannel
tpchannelId"N04" tptransportId"N05"
tpdocExchangeId"N06"gt lttpCharacteristics/gt
lt/tpDeliveryChannelgt lttpTransport
tptransportId"N05"gt lttpSendingProtocolgtHTTPlt
/tpSendingProtocolgt lttpReceivingProtocolgtHTTP
lt/tpReceivingProtocolgt lttpEndpoint
tpuri"http//www.museumURL/servlets/ebXMLHandler
"/gt lt/tpTransportgt lttpDocExchange
tpdocExchangeId"N06"gt lttpebXMLBinding/gt lt/
tpDocExchangegt lt/tpPartyInfogt lttpPackaging
tpid"N0402"gt lttpProcessingCapabilities
tpparse"true" tpgenerate"true"/gt lttpSimpleP
art tpmimetype"text/xml"/gt lt/tpPackaginggt lt/tp
CollaborationProtocolProfilegt
19
ebXML Registry

• Registry systems can give you information about
  many types of ebXML and even non-ebXML documents.
• - CPPs and CPAs
• - Business Process Documents (BPSS, others)
• Core Components and CC Aggregates
• Business Information Entities and Aggregates
• DTDs and Schemas (Assembly documents)
• Programming artifacts

20
Negotiating an agreement

• Find registry and search for partners
• Examine CPP
• Ascertain compatibility of business process and
  technical specifications
• Produce Collaboration Protocol Agreement
• Conditions under which two partners will conduct
  business transactions together
• Modify application

21
ebXML registry deploiement

• We have deployed ebxmlrr registry (open source
  initialy from SUN) http//ebxmlrr.sourceforge.net
  
• Preliminary populated by some business processes
• One of the first implementation in Europe