a framework for realizing artifact centric business processes in soa
DESCRIPTION
TRANSCRIPT
Kan Ngamakeur, Sira Yongchareon, and Chengfei Liu
Faculty of Information and Communication Technologies
Swinburne University of Technology
Australia
A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 2
Introduction Artifact centric process model Motivation
A framework for realizing Artifact-centric model Executable Artifact-centric model Architecture of ACP system Evaluation
Conclusion & future works
Outline
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 3
Introduction: Artifact-centric model Most traditional workflow models are based on activity -
centric perspective During the recent years, an artifact-centric approach to
business process modeling has been introduced as a promising paradigm(Nigam, A. IBM SYSTEMS JOURNAL 2003)
helps communicating the business intent for consolidating business operations across organizations
facilitates the process of business transformation provides higher level of flexibility of workflow enactment and
evolution
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 4
Introduction : Business artifacts Artifacts and their lifecycle - online ordering process example
The ordering process starts when a customer places an order to the retailer for a particular product and pays the invoice.
After completion of Payment, the retailer creates a shipment and delivers the order to the customer
Lifecycle modelData model
Shipment
Orderr1
Creating_shipping
shippedclosedr10
Add_order_itemr3
r2
billedr4
Processing_order_itemr5
Creating_shipping
r6
Ready_for_shippingr7
In_shippingr9 r8
Invoice
unpaid paidr3
Ready_for_shipping
Shipping completed
Waiting_for_ship_itemr7
In_shippingr8r9
r4 r5
OrderIDCustomerName
OrderItem[]GrandTotalCustomer Address
Order
InvoiceIDOrderID
InvoiveDateBillingAddress
TotalAmontPaid
Invoice
ShipIDOrderID
CustomerNameShippingAddress
ShipStartDateShipEndDate
Shipment
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 5
Introduction : Associations & Tasks Business rules – to associate artifacts and Services
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 6
Introduction: Artifact-centric model 4-Dimensional Framework for Artifact-Centric Business
Process Modeling (Hull, R., CoopIS 2008)
Business artifacts Macro Lifecycles Services (Tasks) Associations
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 7
Motivation Existing approach Model Transformation
approach for realizing the artifact-centric model so called ArtiFlow (Liu et al. ICSOC 2010 )
fd Mapped & run on
Artifact-centric Activity-centric
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 8
Motivation Advantage of An existing framework
Fast to implement the workflow model
Drawbacks of An existing framework Loss of information
Business rules are split and mapped to control flows Less flexibility
Tasks are locked up by control flows Monitoring and tracking can not be achieved directly
Need Sophisticated technique involving data gathering and processing
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 9
Our Approach Our approach for realizing artifact-centric process
model. Direct mapping between artifact-centric conceptual model
and executable model No model transformation(not artifact to activity-centric)
Advantages Flexibility No information loss Monitoring and tracking can be achieved directly
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 10
Issues Given artifact-centric process models
How to define an executable model based on an artifact-centric conceptual model ?
How to execute an artifact-centric executable model?
How to manage instances created during the model execution?
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 11
Realization framework
Our Proposed Framework for realizing Artifact-centric process model
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 12
ACP Executable Model: Artifact Schema
<xsd:complexType name="artifactType"> <xsd:sequence> <xsd:element name="attributes" type="attributesType" minOccurs = "1" maxOccurs = "1" /> <xsd:element name="states" type="statesType"
minOccurs = "1“ maxOccurs = "1" /> </xsd:sequence> <xsd:attribute name="name" type="xsd:string" use="required" /></xsd:complexType>
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 13
ACP Executable Model: Rule Schema
<xsd:complexType name="ruleType"> <xsd:sequence> <xsd:element name="onEvent" type="onEventType" maxOccurs = "1" minOccurs = "1" /> <xsd:element name="preCon" type="preconType" maxOccurs
= "1" minOccurs = "1" /> <xsd:element name="do" type="doType" maxOccurs = "1"
minOccurs = "1" /> </xsd:sequence> <xsd:attribute name="name" type="xsd:string" use="required"/></xsd:complexType>
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 14
ACP Executable Model: Service Schema<xsd:complexType name="serviceType"> <xsd:attribute name="name" type="xsd:string" use="required" /> <xsd:attribute name="inputMessage" type="xsd:string" use="required" /> <xsd:attribute name="outputMessage" type="xsd:string" use="required" /> <xsd:attribute name="operation" type="xsd:string" use="required" /> <xsd:attribute name="port" type="xsd:string" use="required"/> <xsd:attribute name="location" type="xsd:anyURI" use="required"/> <xsd:attribute name ="namespace" type ="xsd:anyURI" use="required" /></xsd:complexType>
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 15
ACP Executable Model Sample of An executable Model: Online Ordering
process
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 16
Running Instances Class Diagram of ACP Running Instances
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 17
Running Instances
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 18
Running Instances: Log File Sample log file from an online order example
<log process_id="order_process-P1"> <record no="1"> <timestamp>Dec 4, 2011 2:47:49 PM</timestamp> <ruleId>r01-createOrder:R1</ruleId> <serviceId>system</serviceId> <pre_artifact> <order id="" state="start"> <orderId>null</orderId> <orderItem>null</orderItem> <quantity>null</quantity> <customerAddress>null</customerAddress> <customerName>null</customerName> <grand_total>null</grand_total> <amount_paid>null</amount_paid> <order_item_submit_date>null</order_item_submit_date> <order_item_complete_date>null</order_item_complete_date> </order> </pre_artifact> <post_artifact> <order id="order:c001" state="open_for_item"> <orderId>c001</orderId> <orderItem>msi notebook</orderItem> <quantity>2</quantity> <customerAddress>1/24 Belmont Ave Nth </customerAddress> <customerName>Kan Ngamakeur</customerName> <grand_total>null</grand_total> <amount_paid>null</amount_paid> <order_item_submit_date>null</order_item_submit_date> <order_item_complete_date>null</order_item_complete_date> </order> </post_artifact> </record>
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 19
Architecture of ACP system
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 20
Architecture of ACP system: Components Process Deployer is used to deploy ACP Model definition file. Business Rule Engine provides a rule evaluating functionality. Process Controller is used to manage instances of a process
based on rule engine‘s command. Web Service Controller is used to invoke web services to
process artifact data. Artifact Controller is used to manage and update artifact Front-end UI Interface, is used to manage web-based
interactions between ACP system and users
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 21
Architecture of ACP system
Process Controller
Business Rule Engine
Precondition of rule e.g.
r1 is satisfied
Rule Instance of R1
Artifact Instance of Order
Service Instance of createOrder
Artifact Controller
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 22
Evaluation
Criteria ACP realization on activity-centric system
ACP realization on artifact-centric system
Realization procedure
Needs to have a conversion from ACP model to another procedural execution language (e.g., BPEL).
Direct and automatic realization.
Flexibility and Changes management
less flexibility More flexibility
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 23
Evaluation
Criteria ACP realization on activity-centric system
ACP realization on artifact-centric system
Verification and conformance checking
Needs to have separate (possibly automatic) verification on both ACP model and procedural model.
Single model verification.
Monitoring and Reporting
Needs to have a retransformation from the implementation specification back to its model specification.
Direct and consistent monitoring and reporting at both model level and instance (of task and data) level.
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 24
Conclusion & Future works Realization Framework of Artifact-centric process
model
Direct Approach No loss of information, flexibility, direct monitoring
and tracking Future Works
Extends the framework to support interoperability Add Monitoring and tracking to our ACP system
Kan Ngamakeur : A Framework for Realizing Artifact-Centric Business Processes in Service-Oriented Architecture
The 17th International Conference on Database Systems for Advanced Applications 15-18 April, 2012, Busan, South Korea 25
Thank you