建立过程数据和持久数据的对应关系.PDF

建立过程数据和持久数据的对应关系 Bridging Persistent Data and Process Data Jianwen Su (苏建文) University of California at Santa Barbara Outline Activity  data-centricity  artifact  Lessons from practice  BP as a Service  Extending the artifact concept: Help from data integration? (or not)  Cross reference paths The updatability requirement  Isolation of process “footprints” or dataprints  Many challenges ahead  Conclusions CBPM 13 2013/08/29 2 Traditional BP Modeling Activity-centric, focusing on control flow (e.g. BPMN) Mainly aiming at business management in general (instead of software design/development) e.g., resource planning, logistics  Missing data is a key reason for hindering software design and management, many miserable stories including Hangzhou Housing Management Beauru Kingfore Corporation (KFC, Beijing) RuiJing hospital (Shanghai) Cottage hospital (Santa Barbara, CA) IBM Global Financing (IGF) CBPM 13 2013/08/29 3 Four Kinds of Data  Business data: essential for business logic − Examples: items, shipping addresses  Enactment status: the current execution snapshot − Examples: order sent, shipping request made  Resource usage and state needed for service execution − Examples: cargo space reserved, truck schedule to be determined  Correlation between processes instances − Example: 3 warehouse fulfillment process instances for Jane’s order  Need models that include both activities and data CBPM 13 2013/08/29 4 Four Classes of BP Models  Data agnostic models: data mostly absent – WF (Petri) nets, BPMN, UML Activity Diagrams, …  Data-aware models: da