An Execution Model for Active Data Base Management Systems

Hsu, Meichun; Ladin, Rivka; McCarthy, Dennis R.

doi:10.1016/b978-1-4832-1313-2.50020-2

Cited by 68 publications

(26 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We will also show that the CPLEX rule execution model maps nicely to a subset of an execution model proposed recently [HLM88] in the context of the Hipac system, a High Performance Active Database under development at Computer Corporation of America, although these two models were designed independently. This gives some evidence to the generality of the model proposed in [HLM88]. However, we also observe the need for the Hipac model to be extended and refined.…”

Section: Introductionmentioning

confidence: 94%

Rule execution in CPLEX: A persistent objectbase

Hsu

Cheatham

1988

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Section: Introductionmentioning

confidence: 94%

Rule execution in CPLEX: A persistent objectbase

Hsu

Cheatham

1988

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

“…The IBM Research teams behind [2], [22] and the MDBT and BELA work have now joined with others to form Project ArtiFact TM , which is focused on creating a next-generation artifact-centric meta-model, that can better address emerging challenges such as enabling rich flexibility within a BOM, gracefully handling numerous BOM versions as a business evolves, enabling the coherent specification of a generic BOM with many specializations (as might arise in a global organization with regional variations), and incorporating rich capabilities for representing how people are involved with business operations. The ECA approach for specifying system behavior first appeared in [7,12], where it was used to specify the behavior of "active" database management systems. Reference [11] provides a general framework for specifying a variety of execution semantics for ECA and other kinds of active database systems.…”

Section: Suggested Additional Readingmentioning

confidence: 99%

A Data-Centric Design Methodology for Business Processes

Bhattacharya¹,

Hull²,

Su³

Handbook of Research on Business Process Modeling

View full text Add to dashboard Cite

This chapter describes a design methodology for business processes and workflows that focuses first on "business artifacts", which represent key (real or conceptual) business entities, including both the business-relevant data about them and their macro-level lifecycles. Individual workflow services (a.k.a. tasks) are then incorporated, by specifying how they operate on the artifacts and fit into their lifecycles. The resulting workflow is specified in a particular artifact-centric workflow model, which is introduced using an extended example. At the logical level this workflow model is largely declarative, in contrast with most traditional workflow models which are procedural and/or graph-based. The chapter includes a discussion of how the declarative, artifact-centric workflow specification can be mapped into an optimized physical realization.

show abstract

“…Whereas, active databases have been found to provide a framework to capture the occurrence of database & external events and also provide timely response to these events.The basic constructs provided in Active Database for maintaining the integrity constraints are ECA (Event-ConditionAction) rules. The ECA rules are defined on the state of database and monitors the database events occurring due to transaction execution [3]. In the following sections, we discuss the construct required to model a long duration transaction with full and partial aborts and the mechanism for enforcement of temporal constraints, maintaining the deadlines and early detection of aborting transaction.…”

Section: Introductionmentioning

confidence: 99%