Yeast: a general purpose event-action system

Dept. of Software Eng Res., AT&T Bell Labs., Murray Hill, NJ
IEEE Transactions on Software Engineering (Impact Factor: 2.59). 11/1995; DOI: 10.1109/32.469456
Source: IEEE Xplore

ABSTRACT Distributed networks of personal workstations are becoming the
dominant computing environment for software development organizations.
Many cooperative activities that are carried out in such environments
are particularly well suited for automated support. Taking the point of
view that such activities are modeled most naturally as the occurrence
of events requiring actions to be performed, we developed a system
called Yeast (Yet another Event Action Specification Tool). Yeast is a
client server system in which distributed clients register event action
specifications with a centralized server, which performs event detection
and specification management. Each specification submitted by a client
defines a pattern of events that is of interest to the client's
application plus an action that is to be executed in response to an
occurrence of the event pattern; the server triggers the action of a
specification once it has detected an occurrence of the associated event
pattern. Yeast provides a global space of events that is visible to and
shared by all users. In particular, events generated by one user can
trigger specifications registered by another user. Higher level
applications are built as collections of Yeast specifications. We use
Yeast on a daily basis for a variety of applications, from deadline
notification to software process automation. The paper presents an in
depth description of Yeast and an example application of Yeast, in which
Yeast specifications are used to automate a software distribution
process involving several interdependent software tools

  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The growing number of business process solutions demands the need of platforms enabling developers to build management applications in a more efficient manner. This paper describes an adaptive platform, called BPSM (Business Process Solution Management), for managing business process solutions. A business process solution touches many enterprise entities: multiple business processes, different organizations, various execution platforms, multiple trading partners, and constantly changing business context. To build platforms for business process solutions is difficult. To develop platforms for managing business process solutions poses an even greater challenge. The BPSM platform is our response to this challenge by creating an adaptive environment so that developers can leverage it to build management applications in the domain of business process solution management. The framework of BPSM will be presented in this paper, covering three kinds of decomposition for business process solution management: horizontal decomposition, vertical decomposition and grid decomposition. A language for management policy called Management Commitment Language (MCL) will be presented. This paper will also account why BPSM is a commitment-governed management (CGM) platform. The architectural framework of BPSM will be described in the form of Q&A style and architectural patterns. Finally, a BPSM-based Supply Chain Management system is presented for illustrating the strength of this platform.
    Electronic Commerce Research - ECR.
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: ok she wanted was a short bike-ride away. Our basic position is that the current".comization" phase of the internet represents an early state in the movement towards making P2Pcommerce fully electronic. Another revolution awaits, we believe.2 Current state of e-commerceThink quickly about how many brandnames of detergent you know about. Most people will probablyrecall 3 or 4 major national brand names, stocked by all major national department chain-stores. Thereare many others--- at my...
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Publish/subscribe services, specifically notification serv-ers, are used as the middleware for the implementation of a large set of collaborative software engineering tools. With their popularization, many notification servers are being developed to support specific application domains. At the same time, general-purpose notification servers provide a large set of functionality for a broad set of ap-plications. As a result, developers face the dilemma of choosing between application-specific or general-purpose notification servers. In both cases, however, the set of features provided by the servers are neither extensible nor configurable, hindering the use of these infrastructures in different application domains, making it difficult to add support for new functionality. In this work, we describe a more flexible approach – a customizable, extensible and dynamic architecture for notification services, which al-lows the configuration of the notification service to differ-ent application domains. The design and implementation of the system are discussed, as well as configuration ex-amples.