Learn More
The business artifact (a.k.a. business entity) approach to modeling and implementing business operations and processes is based on a holistic marriage of data and process and enables a factoring of business operations based on key business-relevant conceptual entities. The recently introduced Guard-Stage-Milestone (GSM) artifact meta-model provides a(More)
A promising approach to managing business operations is based on business arti-facts, a.k.a. business entities (with lifecycles) [8, 6]. These are key conceptual entities that are central to guiding the operations of a business, and whose content changes as they move through those operations. A business artifact type is modeled using (a) an information(More)
Case Management is emerging as an important paradigm for Business Process Management. The Guard-Stage-Milestone (GSM) model is a recent case management approach that substantially influences OMG's emerging Case Management Modeling Notation standard. We study the problem of outsourcing part of a GSM schema to another party, and develop a formal framework(More)
Business processes (BPs) can be designed using a variety of model-ing languages and executed in different systems. In most BPM applications, the semantics of BPs needed for runtime management is often scattered across BP models, execution engines, and auxiliary stores of workflow systems. The inability to capture such semantics in BP models is the root(More)
The business artifact (a.k.a. business entity) approach to modeling and implementing business operations and processes, unlike the traditional process-oriented approach, is based on a holistic marriage of data and process, and enables a factoring of business operations based on key business-relevant conceptual entities that progress through the business.(More)
—An important omission in current development practice for business process (or workflow) management systems is modeling of data & access for a business process, including relationship of the process data and the persistent data in the underlying enterprise database(s). This paper develops and studies a new approach to modeling data for business processes:(More)
In most BPM systems (a.k.a. workflow systems), the data for process execution is scattered across databases for enterprise, auxiliary local data stores within the BPM systems, and even file systems (e.g., specification of process models). The interleaving nature of data management and BP execution and the lack of a coherent conceptual data model for(More)