Static Analysis of Business Artifact-centric Operational Models

Business artifacts are the core entities used by businesses to record information pertinent to their operations. Business operational models are representations of the processing of business artifacts. Traditional process modeling approaches focus on the actions taken to achieve a certain goal (verb-centric). Business artifact-centric modeling starts by identifying what is acted upon (noun-centric), and constructs business operational models by identifying the tasks/actions that business actors execute to add business value. In this paper, we identify important classes of properties on artifact-centric operational models. In particular, we focus on persistence, uniqueness and arrival properties. To enable a static analysis of these properties, we propose a formal model for artifact-centric operational models. We show that the formal model guarantees persistence and uniqueness. We prove that, while checking an arrival property is undecidable in general, under a restricted version of the formalism, an arrival property can be checked in EXPTIME.

[1]  Liying Sui,et al.  A system for specification and verification of interactive, data-driven web applications , 2006, SIGMOD Conference.

[2]  Anil Nigam,et al.  Business artifacts: An approach to operational specification , 2003, IBM Syst. J..

[3]  Michael A. Jackson,et al.  Business Process Implementation - Building Workflow Systems , 1997 .

[4]  Sebastián Uchitel,et al.  Model-based verification of Web service compositions , 2003, 18th IEEE International Conference on Automated Software Engineering, 2003. Proceedings..

[5]  Jianwen Su,et al.  Dynamic Constraints and Object Migration , 1991, Theor. Comput. Sci..

[6]  Frank Leymann,et al.  Business process management with FlowMark , 1994, Proceedings of COMPCON '94.

[7]  Jos Warmer,et al.  The object constraint language , 1998 .

[8]  Robert E. Strom,et al.  Typestate: A programming language concept for enhancing software reliability , 1986, IEEE Transactions on Software Engineering.

[9]  Holger Schlingloff,et al.  Modeling and Model Checking Web Services , 2005, LCMAS.

[10]  Anastasia Ailamaki,et al.  Scientific workflow management by database management , 1998, Proceedings. Tenth International Conference on Scientific and Statistical Database Management (Cat. No.98TB100243).

[11]  M. Z. Muehlen,et al.  Workflow Management Coalition , 2000 .

[12]  Roger King,et al.  A database design methodology and tool for information systems , 1985, TOIS.

[13]  Amit P. Sheth,et al.  An overview of workflow management: From process modeling to workflow automation infrastructure , 1995, Distributed and Parallel Databases.

[14]  Emina Torlak,et al.  A type system for object models , 2004, SIGSOFT '04/FSE-12.

[15]  Jianwen Su,et al.  Declarative workflows that support easy modification and dynamic browsing , 1999, WACC.

[16]  John Mylopoulos,et al.  A language facility for designing database-intensive applications , 1980, TODS.

[17]  Katsumi Tanaka,et al.  Computation-tuple sequences and object histories , 1986, TODS.

[18]  Patrick Valduriez,et al.  Distributed and parallel database systems , 1996, CSUR.

[19]  Sheila A. McIlraith,et al.  Simulation, verification and automated composition of web services , 2002, WWW.

[20]  Xiang Fu,et al.  Analysis of interacting BPEL web services , 2004, WWW '04.

[21]  Santhosh Kumaran,et al.  A model-driven approach to industrializing discovery processes in pharmaceutical research , 2005, IBM Syst. J..

[22]  Masatoshi Yoshikawa,et al.  Behavior Analysis of Object-Oriented Databases: Method Structure, Execution Trees, and Reachability (Extended Abstract) , 1989, FODO.

[23]  Serge Abiteboul,et al.  Method schemas , 1990, PODS.

[24]  Franck van Breugel,et al.  Modelling and verifying web service orchestration by means of the concurrency workbench , 2004, SOEN.