Upload
derek-daniels
View
220
Download
2
Embed Size (px)
Citation preview
Artifact-Centric Approach to
Business Process Modeling
Jianwen SuUniversity of California, Santa
Barbara
Artifact为中心的业务过程建模方法
2011/08/25CBPM '11 2
Outline Challenges in Business Process Management
Artifact-centric Modeling Approach
A Design Methodology
Conclusions
2011/08/25CBPM '11 3
Business (Biz) Processes A set of one or more linked activities (automated
or manual) that collectively realize a business objective or policy goal, normally within the context of an organizational structure defining functional roles and relationships
Obtaining a Permit
2011/08/25CBPM '11 4
BP Management Systems
BPMsystem
Manage and support (and control) biz models data (documents, files, …) enactments resources others (e.g. auditing)
A key enabler is suitable BP model
2011/08/25CBPM '11 5
Major Obstacles in BPM Hard to design, ad hoc solutions
Lack of hierarchical approach with good disciplines Hard to modify (evolution)
E.g., go back to the original contractor (if lucky) Hard to analyze
Biz intelligence is a growing research area Hard to interoperate
E.g., hard to get data out in Cottage Hospital at Santa Barbara, CA
A key factor for many problems:insufficient conceptual modeling
2011/08/25CBPM '11 6
Business Strategy• “Be more green”• “Use our
differentiators”
High Executive
High ManagerBusiness
ArchitectSolution Designer
Business GoalsBusiness ArchitectureBusiness
Optimization
The Challenge of BPM
2011/08/25CBPM '11 7
A Business Component Map is a tabular view of the business components in the scope of interest
controlling
executing
directingBusiness Planning
Business Unit Tracking Sales
ManagementCredit Assessment
Reconciliation
Compliance
Staff Appraisals
Relationship Management
Sector Management
Product Management
Production Administration
Product FulfillmentSales
Marketing Campaigns
Product Directory
Credit Administration
Customer Accounts
GeneralLedger
Document Management
Customer Dialogue
Contact Routing
StaffAdministration
BusinessAdministration
New Business Development
Relationship Management
Servicing & Sales
Product Fulfillment
Financial Control and Accounting
Sector Planning
Portfolio Planning
Account Planning Sales Planning Fulfillment
Planning
Fulfillment Planning
“Business Competencies”: large biz area with characteristic skills and capabilities
“Busin
ess
Component”:
part of
enterp
rise th
at
has pote
ntial t
o
operate
independently
“Acc
ou
nta
bili
ty
Level”:
sc
op
e
an
d in
ten
t of
act
ivit
y a
nd
d
eci
sion
-makin
g
A Representative “Model” at Biz Manager Level
2011/08/25CBPM '11 8
Business Strategy• “Be more green”• “Use our
differentiators”
High Executive
High ManagerBusiness
ArchitectSolution Designer
Business GoalsBusiness ArchitectureBusiness
Optimization
Business Operations
Customers
Partners
Employees
Resources
IT
The Challenge of BPM
2011/08/25CBPM '11 9
Common Model at IT Level:
Data Modeling
Biz Process Management System(flow mgmt, services, databases, resources,
…)
System inOperation
Direct, flow-based
implementation
BusinessLogic
Process Modeling
An Activity Flow is a (typically) graph-based specification of how activities/processes are to be sequenced
2011/08/25CBPM '11 10
Operations need to be Faithful Measurable Flexible
Business Strategy• “Be more green”• “Use our
differentiators”
High Executive
High ManagerBusiness
ArchitectSolution Designer
Business GoalsBusiness ArchitectureBusiness
Optimization
Business Operations
Customers
Partners
Employees
Resources
IT
Speak in terms of “Functional
Decomposition”
“Business
Components”
Speak in terms of “Workflow” “Process centric” “Activity-flow”
Hard to Communica
te !!
The Challenge of BPM
2011/08/25CBPM '11 11
Common Model at IT Level:
Data and business objects are typically an afterthought Hard for stake-holders to communicate about the big picture
People “see the trees but not the forest”Overall process can be chaotic – Cf. “staple yourself to a customer order”
Hard to manage versionsE.g., evolution, re-use, generic workflow with numerous specializations
Data Modeling
Biz Process Management System(flow mgmt, services, databases, resources,
…)
System inOperation
Direct, flow-based
implementation
BusinessLogic
Process Modeling
An Activity Flow is a (typically) graph-based specification of how activities/processes are to be sequenced
2011/08/25CBPM '11 12
Typical Biz Process Modeling A bookseller example: Traditional control-centric
models
IDCustomer
ShippingPreference
Paymentinformation Confirmation Archive
FillShopping
Cart
2011/08/25CBPM '11 13
Typical Biz Process Modeling A bookseller example: Traditional control-centric
models Multiple steps needed for each activity
Hard to reason, find useful views: missing data
IDCustomer
ShippingPreference
Paymentinformation Confirmation Archive
FillShopping
Cart
Credit
PayPal
Check
In practice, 100s to 1000s of nodes
CheckInventory
In-stockHandling
Back-orderHandling Existing
CustomerLogin
New Customer
Registration
Air
Warehouses/Size
Ground
2011/08/25CBPM '11 14
BP Analytics (Biz Intelligence) Extract-Transform-Load
cust_db
catalog
inventory
DataWarehouse Analysis
activities
Biz Process is missing!Transactions
Transactions
Transactions
2011/08/25CBPM '11 15
Good models go beyond description – they support action
Selecting the right model for the job matters
First model – A is and B is
1 4 5 6 7 8 92 3 4 5 8
Example: “Game of 15”Winner: First one to reach exactly 15 with any 3 chips
Second model –
1 2 3 4 5 6 7 8 92 3
– what is B’s move?
– B’s move is 6!
Example due to David Cohn (IBM)Can we find a “model” of business operations that is• Useful & natural for the business level stake-holders to
use• Useful & natural for mapping to the IT infrastructure
Why We Should Look for a Unifying Model
2011/08/25CBPM '11 16
A Fundamental “Theorem” of Databases Physical data independence allows us to focus
only data management issues
logical data model
physical organization(files, pages, indexes,
…)
conceptual
physical
SQL
query plan
automatedmapping
2011/08/25CBPM '11 17
Future of BPM Automate ’s
process model
data model
system (model)(databases, services,workflows, resources)
business
IT
changes
Changes to system
Reuse concepts, tools, techniques developed in CS First step: a single conceptual model for biz processes
both data and processes are 1st class citizens
2011/08/25CBPM '11 18
Outline Challenges in Business Process Management
Artifact-centric Modeling Approach
A Design Methodology
Conclusions
2011/08/25CBPM '11 19
Data in BP Modeling: Exclusion to Centricity Data exclusive models focus on activity flow and
managementWfMC, BPMN, …
Incorporating data as views complements well (but separate from) activity viewsUML (object modeling and activity diagrams)
Executable models integrate data and activities with low level of abstractionBPEL
Recent data-centric approaches treat both data and activities “equally” in a more uniformed mannerbiz artifact-centric, form-based, spreadsheet-based
2011/08/25CBPM '11 20
Business Artifacts [Nigam-Caswell
03] A business artifact is a key conceptual business
entity that is used in guiding the operation of the businessfedex package delivery, patient visit, application
form, insurance claim, order, financial deal, registration, …
both “information carrier” and “road-maps”
Very natural to business managers and BP modelers Includes two parts:
Information model:data needed to move through workflow
Lifecycle:possible ways to evolve
2011/08/25CBPM '11 21
DisagreedReceipts
PaidReceipts
PendingReceipts
ArchivedReceipts Archived
KOs
ReadyKOs
PendingKOs
Add Item
Prepare &Test Quality
Deliver
Payment
RecalculateReceipt
PrepareReceipt
CreateGuest Check
UpdateCash Balance
ArchivedGCs
ClosedGCs
OpenGCsGuest Check
Artifacts
Kitchen Order
Receipt
Cash Balance
Example: Restaurant
CashBalance
Activity
repository
2011/08/25CBPM '11 22
DisagreedReceipts
PaidReceipts
PendingReceipts
ArchivedReceipts Archived
KOs
ReadyKOs
PendingKOs
UpdateCash Balance
ArchivedGCs
ClosedGCs
OpenGCs
CashBalance
Add Item
Prepare &Test Quality
Deliver
Payment
RecalculateReceipt
PrepareReceipt
CreateGuest Check
Artifacts GC KO
RC
CB
Example: Restaurant
Guest Check
Kitchen Order
Receipt
Cash Balance
2011/08/25CBPM '11 23
Artifact Life Cycle [Nigam-Caswell 03]
An artifact life cycle captures the end-to-end processing of a specific artifact, from creation to completion and archiving
Artifact processing is a way to describe the operations of a businessDescribed byRepositories, a means for archiving artifactsTasks (activity), a localization of function
Biz operations are described by IFF (Information, Function, and Flow)
2011/08/25CBPM '11 24
Properties on Tasks [Nigam-Caswell 03]
A task performs an action and records the outcome on artifacts in its possession
A task transforms artifacts in its possession by adding/modifying content of an artifact using information in the other artifactsmultiple artifacts can reside in a task, and
their content can be arbitrarily exchanged After a task completes, it ejects all artifacts
within itno residual information: all artifacts are either
sent out or discarded
2011/08/25CBPM '11 25
Flows [Nigam-Caswell 03]
Tasks and repositories can be connected through flow connectors which may be viewed as transport pipes Through these pipes, artifacts or artifact content can be
transmitted from one place (task/repository) to another
Properties on flow: A flow connector is a directed connector between a
fromPlace and a toPlace A flow connector ensures reliable transmission of
artifacts A flow connector, when connecting a task to a
repository, provides a reliable request-response style of communication a task that sends a request to a repository is ensured to
receive one or more artifacts (or artifact content) ora NONE FOUND indication
2011/08/25CBPM '11 26
Life Cycle of Guest Check Artifact [Nigam-Caswell 03]
Human-initiated task
Triggers task when artifactor content is received
Emits artifact or content whentask is finished
Artifact is requested, updated, andreturned to the source repository
Requests and receives artifact content
Requests and receives artifactRepository Task
ADDITEMSTOGUESTCHECK
Externalagent
CashBalance
PaidGuest
Checks
ActiveGuest
Checks
Manu DailySpecials
CompleteKitchenOrder
CUSTOMER
PREPARE ITEMS
Kitchen Order CompleteKitchen Order
TENDERGUEST CHECK
CompleteGuest Check
Paid GuestCheck
Account
CREATE GUEST CHECK
ServiceRequest
GuestCheck
Manu DailySpecial
ActiveGuestCheck
Active Guest Check
Complete Guest Check
Kitchen OrderWaiter
2011/08/25CBPM '11 27
Data (Biz Objects, Documents, …) vs Artifacts They all contain data needed for business logic,
e.g., customer info, shopping cart, product catalog, …
Biz objects are not artifacts: artifacts are uniquely identified with biz process instances, biz objects are just data objects needed for biz process
Biz artifacts also contain:(Schema) Lifecycle, i.e., process (or workflow)
to evolve an artifact from creation to archive(Enactment) Runtime states of instances
(cases), i.e., containing a part of the system snapshot concerning this artifact/enactment
2011/08/25CBPM '11 28
Case Study : IBM Global Financing Finance HW, SW & services from IBM & others for clients IBM internal financing business w/ global reach
World’s largest IT financier w/ $38B asset baseFinancing >$40B IT assets / year for last 3 years125K clients across >50 countries (9% of IBM profit)
Business challengesOperations tailored to mega-deals becoming too costlyEfficiency & cost control required global performance
metricsCountry “silos” inhibited integration & annoyed clientsCurrent methods failed to produce end-to-end “tangible
model”Needed globally standard process w/ local variations
[Chao, Cohn, et al BPM 2009]
2011/08/25CBPM '11 29
How the Artifact-Centric Approach Helped In a 3-day workshop with 15 business SMEs from
IGF, a preliminary artifact design was createdAlready useful to stakeholders from different
regions as a common vocabulary 6 weeks of design refinements lead to final design
Enabled visibility into the global process and the regional variations: not possible before
A blueprint for transformation of IGF operationsVP roles assigned to pieces of top-level artifact
model Current plan: automate the global-level artifact
modelAnticipate significant improvement in efficiencyPlan to substantially augment the sales staff
2011/08/25CBPM '11 30
Outline Challenges in Business Process Management
Artifact-centric Modeling Approach
A Design Methodology
Conclusions
2011/08/25CBPM '11 31
A Data-Centric Design Methodology A three-level framework
Business Operations Model (BOM)(artifacts, activities, flow)
[Bhattacharya-Hull-S. 09]
Conceptual Flow(artifacts, services, choreography/orchestration)
Workflow(artifacts, executable services, messages)
Specification
Optimization
Execution
2011/08/25CBPM '11 32
Key Elements in BOMs Artifact information model
Represent all information needed for the biz process
Artifact (macro-level) lifecycleSpecify how an artifact evolves using e.g.,
state machines Services
Represent activities Associations
Define how and when artifacts are changed by services
2011/08/25CBPM '11 33
Artifact-Centric Design Methodology
Step 1: Business Artifacts Discoverya) Identify critical artifacts for the business
processb) Discover key stages of artifacts’ life cycles
from the scenario-based requirementsStep 2: Design of Business Operations Model (BOM)
a) Logical design of artifact schemasb) Specify services for artifacts needed for
moving artifacts through the life-cyclesc) Develop ECA rules that enable artifacts
progress in their life cyclesStep 3: Design of Conceptual Flow DiagramStep 4: Workflow Realization
2011/08/25CBPM '11 34
Business Artifact Discovery Key artifacts in Distributed Enterprise Services
1
n
1 n
n1
1
n
n1
1
n
n m
ExecutionArtifacts
ConfigurationArtifacts
BackgroundArtifacts
Customer
Site
VendorGeneric
TaskVendor
Task
Schedule(for Offered
DES Service)
OfferedDES
Service
2011/08/25CBPM '11 35
Schedule and Vendor Lifecycles Schedule
Vendor
Schedule_Planning
(&refinement)
Schedule_Approvals Archived
MajorRevisionRe-approval
Execution (&minor revision)
Planning Execution
ArchivedExecution (&minor revision)
Planning
Task_Planning
(&refinement)
TaskApprovals
2011/08/25CBPM '11 36
Data-Centric Design Methodology
Step 1: Business Artifacts Discoverya) Identify critical artifacts for the business
processb) Discover key stages of artifacts’ life cycles
from the scenario-based requirementsStep 2: Design of Business Operations Model (BOM)
a) Logical design of artifact schemasb) Specify services for artifacts needed for
moving artifacts through the lifecyclesc) Develop ECA rules that enable artifacts
progress in their lifecyclesStep 3: Design of Conceptual Flow DiagramStep 4: Workflow Realization
2011/08/25CBPM '11 37
BOM: Logical Design for Artifacts ER diagrams or other suitable modeling
approaches
supplies
m
n
gen_task_ID
stage
base_cost
typical_duration
Vendor
Generic Task
n
OfferedDES Service includes
n m
requires
m
Govt.Approval
n
uses
m
EquipmentType
n
involves
m
Labor Type
includes
m
n
offered_serv_ID
stage
description
typical_duration
Generic Task
OfferedDES Service
n
m
k
precedence
supplied_by
1
n
stage
planned_start_dateplanned_end_date
status
Vendor
Vendor TaskSchedule includesn m
requires
n
Govt.Approval
uses
n
EquipmentOrder
uses
n
Labor Spec
1 1 1
vendor_task_ID
cust_end_site_into
stage
planned_end_daterevision_checklist
exec_status
Schedule
OfferedDES Service
based_on
1 n
includes
n
Generic Task
m
Vendor task
m 1
schedule_ID
planned_start_date
approved_for_exec
n
precedence
k
Site serves n1
optimality_factor
no_vendor_available
2011/08/25CBPM '11 38
BOM: Specifying Services Create_scheduleOffered DES Service: oCustomer:
cSitesi:Has the effect of creating a schedule artifact for o, c, and si (where si is a site of c)
Create_vendor_task (Schedule: sch, Generic Task: g):Has the effect of creating a vendor task artifact that will be associated with g in sch
Adjust_task_general (Vendor task: t, Vender: v, Schedule: sch, list[Task, start_date, end_date]):Used to revise all aspects of a vendor task t during the Task_planning stage. The task t serves as the primary artifact for this service and the following ones; the other artifacts that are used as input are all reachable from the primary artifact. The list of tasks with start- and end-dates is intended to hold all tasks that are immediate successors of t according to sch
2011/08/25CBPM '11 39
Inp
uts
Outp
uts
Pre
-C
on
d.
eff
ect
BOM Service: IOPEs of Create_schedule An Offered DES Service artifact o, and specifically the listing
of used Generic Tasks, along with whether they are optional, and information about the Precedence relationships between them
A Customer artifact c, ... A Site artifact si for c, ... A new Schedule artifact sch. The data written will include
attributes schedule_ID, stage, planned_start_date, and the Generic Task portion of the includes relationship
The Site artifact si is updated … Offered DES Service artifact o must be compatible with the
infrastructure and needs of site si If true, then sch is in stage Schedule_planning If true, then sch holds a schedule skeleton (i.e., appropriate
portions of the relationship includes are filled in) If true, …
2011/08/25CBPM '11 40
BOM: ECA Rules
R1: initiate schedule
event request by performer p to create a schedule instance for Offered DES Service artifact o, Customer artifact c, and Site artifact sicondition the appropriate non-disclosure agreements (NDAs) are in place for caction invoke Create_schedule(o, c, si) by performer p where offer_manager in role(p) and qualification(p, o, region: si.region) ≥ 5
Alternative models can also be used
2011/08/25CBPM '11 41
Data-Centric Design Methodology
Step 1: Business Artifacts Discoverya) Identify critical artifacts for the business
processb) Discover key stages of artifacts’ life cycles
from the scenario-based requirementsStep 2: Design of Business Operations Model (BOM)
a) Logical design of artifact schemasb) Specify services for artifacts needed for
moving artifacts through the life-cyclesc) Develop ECA rules that enable artifacts
progress in their life cyclesStep 3: Design of Conceptual Flow DiagramStep 4: Workflow Realization
2011/08/25CBPM '11 42
Conceptual Flow Diagram (EZ-Flows)
Secondary_ Review
Payment_Processing
Preparing_Certificate
Preliminary_Decision
Receiving_ App_Form_
Preparing _file
Delivery_ Certificate
(Closing case)
CAP_App_Form_Received
Preliminary_Approval
Final_ Approval
_and_ Certificate
Repository
Database
Read only
Message
E Producing Event
E Consuming Event E
Artifact
Write (push)
Read (pull)
E2
PAF
PAF
PAF
BL
BL
PAF
BL
Ready_for_Payment
PAF
PAF
PAF
BL
BL
BL
PAF
PAF
PAF
PAF
PAF
M6: CC
E1
M1: App-Form M4: Payment
Final_Approval
PAF
M5: ANService
CAPA
Estate Preliminary Surveying
Demolition Resettlement Houses Verification
Property Management Office Confirmation . . .
Other REAB
workflowsBL BL BL
Real_Estate_ Database
E2
E3
E3
E4
E4
E5
E5
E5
E6
E7E6
M2: PD
M3: SR
M5: AN
[ArtiFlow 2009]
2011/08/25CBPM '11 43
Interpreting EZ-Flows
Event Handler
WebService
Human Service
WebService
......
Human Service
UI (Web service)
Person
Event Producer
ArtiFlow Instance Creator
MQ ServerArtiFlow
DefinitionDatabase
ArtifactDatabase
Message Queue
Flow controllerData controller
......
Task-synchronous service wrapper
Artifact Fetcher
Artifact Information Updater
Artifact Depositor
Artifact Repository Updater
Task Scheduler
ExternalDatabase
Task-asynchronous service wrapper
Task-asynchronous service wrapper
Data Wrapper
External Message
Internal Message
Alternative: Mapping to BPEL [ArtiFlow 2009]
2011/08/25CBPM '11 44
Emerging Artifact-Centric BPs
Informal model [Nigam-Caswell 03]
Systems: BELA (IBM 2005), Siena (IBM 2007),ArtiFlow (Fudan-UCSB 2010), Barcelona (IBM 2010)
Formal modelsState machines [Gerede-Bhattacharya-S. SOCA 07][Gerede-S.
ICSOC 07]Rules [Bhattacharya-Gerede-Hull-Liu-S. BPM 07][Hull et al WSFM 2010]
customerinfo cart
. . .
Artifacts (Info models)
Specification ofartifact lifecycles
2011/08/25CBPM '11 45
Declarative Biz Processes
Variation of [Bhattacharya-Gerede-Hull-Liu-S. BPM 07]
Artifacts(info
models)
Semantic services(IOPEs)
if C enable…
Condition-action rules
2011/08/25CBPM '11 46
Creating Proc. Orders
All Line Items ordered
some Proc.Order
Rejected& affectedLine Items
researched
InitiateReq.
Order
Generating Report
Reportrequested
Top ofeach hour
Reportgenerated
Data attributes Event (occurrence) attributes
Req.Ordercancelled
AssemblingRequest to begin
assembling& enough
Line Itemsto start
Assemblyfinished
Assemblycancelled
… …ID Custo
mer
Line Items
Optimal li
ne
items p
artition
Procu
rement
Ord
ers
Request new
Req. O
rder
Done alloca
ting
Line Ite
msMilestone: •Business-relevant operational objective•Expressed as event and/or condition•Has effect of closing the stage
Stage: •Cluster of activities intended to achieve one (of perhaps several) milestones•May be nested
Guard: •Has the effect of opening the stage•Expressed as event and/or condition
GSM: Requisition Order Lifecycle[Hull et al WSFM 2010]
2011/08/25CBPM '11 47
Operational Semantics in a NutshellCreating Proc. Orders
All Line Items ordered
•ID •Custo
mer
•…
•Line Ite
msOptim
al line
ite
ms
partition
Initiate Req.
Order
Assembling
Generating Report
Report requested
Top of each hour
Procu
rement
Ord
ers
Assembly finished
Report generated
Assembly abandoned
Request new
Req. O
rder
Done alloca
ting
Line Ite
ms
Data Attributes Event (occurrence)attributes
•…
Request to begin assembling and enough Line Items to start
•…
Statusattributes
•…
Stage(active or inactive)milestones
some Proc.Order
Rejected&
affected Line
Items research
ed
Req.Ordercancelled
Stylized ECA• Guard: Event/Cond -> open stage• Milestone: Event/Cond -> close stage and
set milestone status attribute to “true”
2011/08/25CBPM '11 48
some Proc.Order
Rejected&
affected Line
Items research
ed
•ID •Custo
mer
•…
•Line Ite
msOptim
al line
ite
ms
partition
Procu
rement
Ord
ers
Request new
Req. O
rder
Done alloca
ting
Line Ite
ms
Data Attributes
•…
Creating Proc. OrdersAll Line Items ordered
Planning Proc. orders
LaunchingLine Items
Launching & Sending Proc. Orders
Initiate Req.
Order
Assembling
Generating Report
Done only in first occurrence of this stage
All Line Items not in a Procurement Order have been Researched
This milestone becomes true once all Proc. Orders have been sent
Event (occurrence)attributes
•…
Statusattributes
milestones
•…
Stage(active or inactive)
This milestone becomes “compromised” if a Proc. Order is later rejected
Stylized ECA (cont.)• Milestone Invalidator: Event/Cond -> set
milestone to “false”
Nesting of Substages
2011/08/25CBPM '11 49
Creating Proc. OrdersAll Line Items ordered
Planning Proc. orders
LaunchingLine Items
Launching & Sending Proc. Orders
Initiate Req.
Order
Assembling
Generating Report
•ID •Custo
mer
•…
•Line Ite
msOptim
al line
ite
ms
partition
Procu
rement
Ord
ers
Request new
Req. O
rder
Done alloca
ting
Line Ite
ms
Data Attributes
•…
Event (occurrence)attributes
•…
Statusattributes
milestones
•…
Stage(active or inactive)
Atomic stage; has a “task” inside
• Atomic stage; has a “task” inside
• Task reads from Data Attributes, and later writes into them
some Proc.Order
Rejected&
affected Line
Items research
ed
Stylized ECA (cont.)• If open atomic stage -> invoke task• Note: task return is key incoming event –
it will close the atomic stage
Atomic Stages and Tasks
2011/08/25CBPM '11 50
Outline Challenges in Business Process Management
Artifact-centric Modeling Approach
A Design Methodology
Conclusions
2011/08/25CBPM '11 51
Brief Summary of Research Problems Verification
Temporal properties of transition systems[Gerede-S. ICSOC07] [Bhattacharya-Gerede-Hull-Liu-S. BPM07][Deutch et al ICDT09], [Damaggio-Deutsch-Vianu ICDT11] …
Interoperation [Hull-Narendra-Nigam ICSOC09]
Automated construction [Frits-Hull-S. ICDT09]
Dominance [Calvanese-De Giacomo-Hull-S. ICSOC09]
Modeling: Declarative, semantics, execution[Cangialosi-De Giacomo-De Masellis-Rosati ICSOC10]
Flexible execution [Xu-S.-Yan-Yang-Zhang CoopIS11]
Preserving Data ICs [Liu-S.-Yang CoopIS 2011]
2011/08/25CBPM '11 52
Conclusions Biz process modeling: a foundation for many BPM
issuesMany challenges: “old” and new Data-centric or data aware approaches promising
Business artifacts as the modeling foundation:Extension of business objects with
lifecycle/enactmentsMany styles of modeling approaches: declarative,
procedural, combinations Modeling is/need be explored in conjunction with
various technical issues in BP management
A longer tutorial is at BPM 2011 (next week)
2011/08/25CBPM '11 53
References[Nigam-Caswell 03] A. Nigam and N. S. Caswell. Business artifacts: An approach to
operational specification. IBM Systems Journal, 42(3):428–445, 2003[Chao, Cohn, et al, BPM 2009] T. Chao, D. Cohn, A. Flatgard, S. Hahn, M.H. Linehan, P.
Nandi, A. Nigam, F. Pinel, J. Vergo, F.Y. Wu. Artifact-Based Transformation of IBM Global Financing, Proc. BPM 2009, pages 261-277
[Bhattacharya-Hull-S. 09] K. Bhattacharya, R. Hull, and J. Su. A data-centric design methodology for business processes. In Handbook of Research on Business Process Modeling. Information Science Publishing, 2009
[ArtiFlow 2009] G. Liu, X. Liu, H. Qin, J. Su, Z. Yan, L. Zhang. Automated Realization of Business Workflow Specification. ICSOC/ServiceWave Workshops 2009 : 96-108
[Bhattacharya-Gerede-Hull-Liu-S. BPM 07] K. Bhattacharya, C. Gerede, R. Hull, R. Liu, and J. Su. Towards formal analysis of artifact-centric business process models. In Proc. 5th Int. Conf. on Business Process Management (BPM), Brisbane, Australia, September 2007
[Gerede- Bhattacharya-S. SOCA 07] C.E. Gerede, K. Bhattacharya, J. Su. Static Analysis of Business Artifact-centric Operational Models. SOCA 2007: 133-140
[Gerede-S. ICSOC 07] C.E. Gerede and J. Su: Specification and Verification of Artifact Behaviors in Business Process Models. ICSOC 2007: 181-192
[Hull et al WSFM 2010] R. Hull, E. Damaggio, F. Fournier, M. Gupta, F.T. Heath, S. Hobson, M.H. Linehan, S. Maradugu, A. Nigam, P. Sukaviriya, R. Vaculín: Introducing the Guard-Stage-Milestone Approach for Specifying Business Entity Lifecycles. WS-FM 2010: 1-24
2011/08/25CBPM '11 54
References[Fritz-Hull-S. ICDT09] C. Fritz, R. Hull, and J. Su. Automatic construction of simple artifact-
based business processes. ICDT 2009: 225-238[Deutsch et al ICDT09] A. Deutsch, R. Hull, F. Patrizi, and V. Vianu. Automatic verification
of data-centric business processes. ICDT 2009: 252-267[Damaggio-Deutsch-Vianu ICDT11] E. Damaggio, A. Deutsch, V. Vianu. Artifact systems
with data dependencies and arithmetic. ICDT 2011: 66-77[Hull-Narendra-Nigam ICSOC09] R. Hull, N.C. Narendra, A. Nigam: Facilitating Workflow
Interoperation Using Artifact-Centric Hubs. ICSOC 2009: 1-18[Cangialosi-De Giacomo-De Masellis-Rosati ICSOC10] P. Cangialosi, G. De Giacomo, R. De
Masellis, R. Rosati. Conjunctive Artifact-Centric Services. ICSOC 2010: 318-333[Xu-S.-Yan-Yang-Zhang CoopIS11] W. Xu, J. Su, Z. Yan, J. Yang, and L. Zhang. An Artifact-
Centric Approach to Dynamic Modification of Workflow Execution. Proc. Int Conf. on Cooperating Information Systems (CoopIS), 2011
[Liu-S.-Yang CoopIS11] X. Liu, J. Su, and J. Yang. Preservation of Integrity Constraints by Workflow. Proc. Int Conf. on Cooperating Information Systems (CoopIS), 2011