Merging application-centric and data-centric approaches to support transaction-oriented multi-system workflows

Breitbart, Yuri; Deacon, Andrew; Schek, Hans-Jörg; Sheth, Amit P.; Weikum, Gerhard

doi:10.1145/163090.163095

Cited by 80 publications

(40 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It has been subsequently used by a n umber of researchers Breitbart et al, 1993, Rusinkiewicz and Sheth, 1995, Krishnakumar and Sheth, 1995, Georgakopoulos et al, 1995, Tang and Veijalainen, 1995, Leymann et al, 1996. Transactional work ows involve the coordinated execution of multiple related tasks that require access to HAD systems and support selective use of transactional properties for individual tasks or entire work ows.…”

Section: Transactional Workflowsmentioning

confidence: 99%

“…Some of the apparent w eaknesses of work ow models that need to be addressed by the work ow community include the lack of a clear theoretical basis, unde ned correctness criteria, limited support for synchronization of concurrent w ork ows, lack o f i n teroperability, scalability a n d a vailability, and lack of support for reliability in the presence of failures and exceptions Breitbart et al, 1993, Jin et al, 1993, Georgakopoulos et al, 1995, Alonso and Schek, 1996, Kamath and Ramamritham, 1996, Leymann et al, 1996, Alonso et al, 1996a. In addition, a successful work ow-enabled solution should address many of the growing user needs that have resulted from: emerging and maturing infrastructure technologies and standards for distributed computing such as the World Wide Web, Common Object Request Broker Architecture OMG, 1995b], Distributed Common Object Model (DCOM), ActiveX, Lotus Notes, and Java.…”

Section: Introductionmentioning

confidence: 99%

“…There exists a strong school of thought, primarily comprised of researchers from the database community, w h i c h views a work ow model as an extension of ATMs , Chen and Dayal, 1996, Biliris et al, 1994, Weikum, 1993, Wachter and Reuter, 1992. However, it has also been observed Breitbart et al, 1993, Alonso et al, 1996b, Worah and Sheth, 1996 that ATMs have limited applicability in the context of work ows due to their inability to model the rich requirements of today's organizational processes adequately.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Transactions in Transactional Workflows

Worah¹,

Sheth²

1997

Advanced Transaction Models and Architectures

View full text Add to dashboard Cite

Work ow management systems (WFMSs) are nding wide applicability in small and large organizational settings. Advanced transaction models (ATMs) focus on maintaining data consistency and have p r o vided solutions to many problems such as correctness, consistency, and reliability in transaction processing and database management e n vironments. While such concepts have yet to be solved in the domain of work ow systems, database researchers have proposed to use, or attempted to use ATMs to model work ows. In this paper we survey the work done in the area of transactional work ow systems. We then argue that work ow requirements in large-scale enterprise-wide applications involving heterogeneous and distributed environments either di er or exceed the modeling and functionality support provided b y A TMs. We propose that an ATM is unlikely to provide the primary basis for modeling of work ow applications, and subsequently work ow management. W e discuss a framework for error handling and recovery in the METEOR2 WFMS that borrows from relevant w ork in ATMs, distributed systems, software engineering, and organizational sciences. We h a ve also presented various connotations of transactions in real-world organizational processes today. Finally, w e point out the need for looking beyond ATMs and using a multi-disciplinary approach for modeling large-scale work ow applications of the future.

show abstract

Section: Transactional Workflowsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Transactions in Transactional Workflows

Worah¹,

Sheth²

1997

Advanced Transaction Models and Architectures

View full text Add to dashboard Cite

show abstract

“…Applications of WFMS can be found in various publications, see Alonso (1994), Blumenfeld {1993), Breitbart (1993), Jablonski (1995), Medina-Mores (1992), Georgakapoulos (1994). Two of them are described in the following in more detail since they have interesting characteristics, which are very important in the area of enterprise integration.…”

Section: Examples Of Workflow Applicationsmentioning

confidence: 99%

Workflow-Management-Systems as enterprise engineering tools

Bußler

1996

Modelling and Methodologies for Enterprise Integration

View full text Add to dashboard Cite

Workflow-Management is a growing research area in computer science. It focuses on the modeling of coarse grain abstract processes called workflows as well as on software architectures and systems for their execution.Enterprise Integration (EI) deals besides other aspects with enterprise or business processes which are a description of complex tasks within an enterprise involving humans or machines, data and applications. Since business processes developed by techniques of EI should finally be enacted to actively drive the enterprise an execution mechanism is required. We argue that Workflow-Management-Systems (WFMS) are a technology which can be deployed as enterprise engineering tools in order to enact enterprise processes.

show abstract

“…Today a transition from data-centered to process-aware systems takes place [23]. The current trend towards service-oriented software architectures [3] increases the need for flexible application service composition.…”

Section: Process Management Systemsmentioning

confidence: 99%

Schema Evolution in Process Management Systems

SpringerReference

View full text Add to dashboard Cite

Continuously arising new trends in information technology and developments at the (e-business) market let companies crave for automated business process support. Process management systems offer the promising possibility to (electronically) define, control, and monitor business processes. However, if this technology shall be applicable in practice it must be possible to change running business processes even at runtime. Basically, such process changes can take place at two levels -the process type level and the process instance level. If a process type is modified a new version of the respective process type schema is created. Then, at minimum, the process instances running according to the old process type schema version must be able to finish without being disturbed. However, this simple versioning approach is only sufficient for short-running business processes. For long-running ones like, for example, car leasing contracts or medical treatment processes which may last from 3 up to 5 years, it must be possible to apply the process type changes to the collection of running process instances as well but without causing inconsistencies or errors in the sequel. Apart from process schema evolution and change propagation a flexible process management system must also enable instance-specific (ad-hoc) changes, for example, if exceptional situations occur. If then a process type change takes place the challenging question arises how to adequately deal with the interplay of process type and process instance changes.

show abstract

Merging application-centric and data-centric approaches to support transaction-oriented multi-system workflows

Cited by 80 publications

References 10 publications

Transactions in Transactional Workflows

Transactions in Transactional Workflows

Workflow-Management-Systems as enterprise engineering tools

Schema Evolution in Process Management Systems

Contact Info

Product

Resources

About