Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法.

Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法

2011/08/25CBPM '112 Outline Challenges in Business Process Management Artifact-centric Modeling Approach A Design Methodology Conclusions

2011/08/25CBPM '113 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 '114 BP Management Systems BPM system 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 '115 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 '116 Business Strategy “Be more green” “Use our differentiators” High Executive High Manager Business Architect Solution Designer Business Goals Business Architecture Business Optimization The Challenge of BPM

2011/08/25CBPM '117 A Business Component Map is a tabular view of the business components in the scope of interest controlling executing directing Business Planning Business Unit Tracking Sales Management Credit Assessment Reconciliation Compliance Staff Appraisals Relationship Management Sector Management Product Management Production Administration Product Fulfillment Sales Marketing Campaigns Product Directory Credit Administration Customer Accounts General Ledger Document Management Customer Dialogue Contact Routing Staff Administration Business Administration New Business Development Relationship Management Servicing & Sales Product Fulfillment Financial Control and Accounting Sector Planning Portfolio Planning Account Planning Sales Planning Fulfillment Planning “ Business Competencies ” : large biz area with characteristic skills and capabilities “ Business Component ” : part of enterprise that has potential to operate independently “ Accountability Level ” : scope and intent of activity and decision-making A Representative “ Model ” at Biz Manager Level

2011/08/25CBPM '118 Business Strategy “Be more green” “Use our differentiators” High Executive High Manager Business Architect Solution Designer Business Goals Business Architecture Business Optimization Business Operations Customers Partners Employees Resources IT The Challenge of BPM

2011/08/25CBPM '119 Common Model at IT Level: Data Modeling Biz Process Management System (flow mgmt, services, databases, resources, … ) System in Operation Direct, flow-based implementation Business Logic Process Modeling An Activity Flow is a (typically) graph-based specification of how activities/processes are to be sequenced

2011/08/25CBPM '1110 Operations need to be  Faithful  Measurable  Flexible Business Strategy “Be more green” “Use our differentiators” High Executive High Manager Business Architect Solution Designer Business Goals Business Architecture Business 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 Communicate !! The Challenge of BPM

2011/08/25CBPM '1111 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 versions  E.g., evolution, re-use, generic workflow with numerous specializations Data Modeling Biz Process Management System (flow mgmt, services, databases, resources, … ) System in Operation Direct, flow-based implementation Business Logic Process Modeling An Activity Flow is a (typically) graph-based specification of how activities/processes are to be sequenced

2011/08/25CBPM '1112 Typical Biz Process Modeling A bookseller example: Traditional control-centric models ID Customer Shipping Preference Payment information Confirmation Archive Fill Shopping Cart

2011/08/25CBPM '1113 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 ID Customer Shipping Preference Payment information Confirmation Archive Fill Shopping Cart Credit PayPal Check In practice, 100s to 1000s of nodes Check Inventory In-stock Handling Back-order Handling Existing Customer Login New Customer Registration Air Warehouses/ Size Ground

2011/08/25CBPM '1114 BP Analytics (Biz Intelligence) Extract-Transform-Load cust_db catalog inventory Data Warehouse Analysis activities Biz Process is missing! Transactions

2011/08/25CBPM '1115 Good models go beyond description – they support action Selecting the right model for the job matters First model – A is and B is 145678923458 Example: “Game of 15” Winner: First one to reach exactly 15 with any 3 chips Second model – 12345678923 – 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 '1116 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 automated mapping

2011/08/25CBPM '1117 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 1 st class citizens

2011/08/25CBPM '1119 Data in BP Modeling: Exclusion to Centricity Data exclusive models focus on activity flow and management  WfMC, BPMN, … Incorporating data as views complements well (but separate from) activity views  UML (object modeling and activity diagrams) Executable models integrate data and activities with low level of abstraction  BPEL Recent data-centric approaches treat both data and activities “ equally ” in a more uniformed manner  biz artifact-centric, form-based, spreadsheet-based

2011/08/25CBPM '1120 Business Artifacts [Nigam-Caswell 03] A business artifact is a key conceptual business entity that is used in guiding the operation of the business  fedex 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 '1121 Disagreed Receipts Paid Receipts Pending Receipts Archived Receipts Archived KOs Ready KOs Pending KOs Add Item Prepare & Test Quality Deliver Payment Recalculate Receipt Prepare Receipt Create Guest Check Update Cash Balance Archived GCs Closed GCs Open GCs Guest Check Artifacts Kitchen Order Receipt Cash Balance Example: Restaurant Cash Balance Activity repository

2011/08/25CBPM '1122 Disagreed Receipts Paid Receipts Pending Receipts Archived Receipts Archived KOs Ready KOs Pending KOs Update Cash Balance Archived GCs Closed GCs Open GCs Cash Balance Add Item Prepare & Test Quality Deliver Payment Recalculate Receipt Prepare Receipt Create Guest Check Artifacts GCKO RCCB Example: Restaurant Guest Check Kitchen Order Receipt Cash Balance

2011/08/25CBPM '1123 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 business Described by  Repositories, a means for archiving artifacts  Tasks (activity), a localization of function Biz operations are described by IFF (Information, Function, and Flow)

2011/08/25CBPM '1124 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 artifacts  multiple artifacts can reside in a task, and their content can be arbitrarily exchanged After a task completes, it ejects all artifacts within it  no residual information: all artifacts are either sent out or discarded

2011/08/25CBPM '1125 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) or a NONE FOUND indication

2011/08/25CBPM '1126 Life Cycle of Guest Check Artifact [Nigam-Caswell 03] Human-initiated task Triggers task when artifact or content is received Emits artifact or content when task is finished Artifact is requested, updated, and returned to the source repository Requests and receives artifact content Requests and receives artifact Repository Task ADD ITEMS TO GUEST CHECK External agent Cash Balance Paid Guest Checks Active Guest Checks Manu Daily Specials Complete Kitchen Order CUSTOMER PREPARE ITEMS Kitchen Order Complete Kitchen Order TENDER GUEST CHECK Complete Guest Check Paid Guest Check Account CREATE GUEST CHECK Service Request Guest Check ManuDaily Special Active Guest Check Complete Guest Check Kitchen Order Waiter

2011/08/25CBPM '1127 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 '1128 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 base  Financing > $40B IT assets / year for last 3 years  125K clients across > 50 countries ( 9% of IBM profit) Business challenges  Operations tailored to mega-deals becoming too costly  Efficiency & cost control required global performance metrics  Country “ silos ” inhibited integration & annoyed clients  Current 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 '1129 How the Artifact-Centric Approach Helped In a 3-day workshop with 15 business SMEs from IGF, a preliminary artifact design was created  Already 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 operations VP roles assigned to pieces of top-level artifact model Current plan: automate the global-level artifact model  Anticipate significant improvement in efficiency  Plan to substantially augment the sales staff

2011/08/25CBPM '1131 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 '1132 Key Elements in BOMs Artifact information model  Represent all information needed for the biz process Artifact (macro-level) lifecycle  Specify 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 '1133 Artifact-Centric Design Methodology Step 1 : Business Artifacts Discovery a) Identify critical artifacts for the business process b) Discover key stages of artifacts’ life cycles from the scenario-based requirements Step 2 : Design of Business Operations Model (BOM) a) Logical design of artifact schemas b) Specify services for artifacts needed for moving artifacts through the life-cycles c) Develop ECA rules that enable artifacts progress in their life cycles Step 3 : Design of Conceptual Flow Diagram Step 4 : Workflow Realization

2011/08/25CBPM '1134 Business Artifact Discovery Key artifacts in Distributed Enterprise Services 1 n 1 n n1 1 n n1 1 n nm Execution Artifacts Configuration Artifacts Background Artifacts Customer Site Vendor Generic Task Vendor Task Schedule (for Offered DES Service) Offered DES Service

2011/08/25CBPM '1135 Schedule and Vendor Lifecycles Schedule Vendor Schedule_ Planning (&refinement) Schedule_ Approvals Archived Major Revision Re-approval Execution (& minor revision) PlanningExecution Archived Execution (& minor revision) Planning Task_ Planning (&refinement) Task Approvals

2011/08/25CBPM '1136 Data-Centric Design Methodology Step 1 : Business Artifacts Discovery a) Identify critical artifacts for the business process b) Discover key stages of artifacts’ life cycles from the scenario-based requirements Step 2 : Design of Business Operations Model (BOM) a) Logical design of artifact schemas b) Specify services for artifacts needed for moving artifacts through the lifecycles c) Develop ECA rules that enable artifacts progress in their lifecycles Step 3 : Design of Conceptual Flow Diagram Step 4 : Workflow Realization

2011/08/25CBPM '1137 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 Offered DES Service includes n m requires m Govt. Approval n uses m Equipment Type n involves m Labor Type includes m n offered_ serv_ID stage description typical_ duration Generic Task Offered DES Service n m k precedence supplied_by 1 n stage planned_ start_date planned_ end_date status Vendor Vendor Task Schedule includes n m requires n Govt. Approval uses n Equipment Order uses n Labor Spec 11 1 vendor_ task_ID cust_end_ site_into stage planned_ end_date revision_ checklist exec_ status Schedule Offered DES 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 n 1 optimality_ factor no_vendor _available

2011/08/25CBPM '1138 BOM: Specifying Services Create_schedule   Offered DES Service: o  Customer: c  Site   si  : 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 '1139 Inputs Outputs Pre- Cond. effect 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 '1140 BOM: ECA Rules R 1 : initiate schedule event request by performer p to create a schedule instance for Offered DES Service artifact o, Customer artifact c, and Site artifact si condition the appropriate non-disclosure agreements (NDAs) are in place for c action 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 '1141 Data-Centric Design Methodology Step 1 : Business Artifacts Discovery a) Identify critical artifacts for the business process b) Discover key stages of artifacts’ life cycles from the scenario-based requirements Step 2 : Design of Business Operations Model (BOM) a) Logical design of artifact schemas b) Specify services for artifacts needed for moving artifacts through the life-cycles c) Develop ECA rules that enable artifacts progress in their life cycles Step 3 : Design of Conceptual Flow Diagram Step 4 : Workflow Realization

2011/08/25CBPM '1142 Conceptual Flow Diagram (EZ-Flows) [ArtiFlow 2009]

2011/08/25CBPM '1143 Interpreting EZ-Flows Alternative: Mapping to BPEL [ArtiFlow 2009]

2011/08/25CBPM '1144 Emerging Artifact-Centric BPs Informal model [Nigam-Caswell 03] Systems: BELA (IBM 2005), Siena (IBM 2007), ArtiFlow (Fudan-UCSB 2010), Barcelona (IBM 2010) Formal models  State machines [Gerede-Bhattacharya-S. SOCA 07][Gerede-S. ICSOC 07]  Rules [Bhattacharya-Gerede-Hull-Liu-S. BPM 07][Hull et al WSFM 2010] customer info cart... Artifacts (Info models) Specification of artifact lifecycles 

2011/08/25CBPM '1145 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 '1146 Creating Proc. Orders All Line Items ordered some Proc. Order Rejected & affected Line Items researched Initiate Req. Order Generating Report Report requested Top of each hour Report generated Data attributes Event (occurrence) attributes Req. Order cancelled Assembling Request to begin assembling & enough Line Items to start Assembly finished Assembly cancelled …… ID Customer Line Items Optimal line items partition Procurement Orders Request new Req. Order Done allocating Line Items Milestone: 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 '1147 Operational Semantics in a Nutshell Creating Proc. Orders All Line Items ordered ID Customer … Line Items Optimal line items partition Initiate Req. Order Assembling Generating Report Report requested Top of each hour Procurement Orders Assembly finished Report generated Assembly abandoned Request new Req. Order Done allocating Line Items Data Attributes Event (occurrence) attributes … Request to begin assembling and enough Line Items to start … Status attributes … Stage (active or inactive) milestones some Proc. Order Rejected & affected Line Items research ed Req. Order cancelled Stylized ECA Guard: Event/Cond -> open stage Milestone: Event/Cond -> close stage and set milestone status attribute to “true”

2011/08/25CBPM '1148 some Proc. Order Rejected & affected Line Items research ed ID Customer … Line Items Optimal line items partition Procurement Orders Request new Req. Order Done allocating Line Items Data Attributes … Creating Proc. Orders All Line Items ordered Planning Proc. orders Launching Line 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 … Status attributes 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 '1149 Creating Proc. Orders All Line Items ordered Planning Proc. orders Launching Line Items Launching & Sending Proc. Orders Initiate Req. Order Assembling Generating Report ID Customer … Line Items Optimal line items partition Procurement Orders Request new Req. Order Done allocating Line Items Data Attributes … Event (occurrence) attributes … Status attributes milestones … Stage (active or inactive) 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 '1151 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 '1152 Conclusions Biz process modeling: a foundation for many BPM issues  Many challenges: “ old ” and new  Data-centric or data aware approaches promising Business artifacts as the modeling foundation:  Extension of business objects with lifecycle/enactments  Many 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 '1153 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 '1154 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

Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法.

Similar presentations

Presentation on theme: "Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法.

Similar presentations

Presentation on theme: "Artifact-Centric Approach to Business Process Modeling Jianwen Su University of California, Santa Barbara Artifact 为中心的业务过程建模方法."— Presentation transcript:

Similar presentations

About project

Feedback