Identifying requirements for Business Contract Language: a Monitoring Perspective

  • Authors:
  • S. Neal;J. Cole;P. F. Linington;Z. Milosevic;S. Gibson;S. Kulkarni

  • Affiliations:
  • -;-;-;-;-;-

  • Venue:
  • EDOC '03 Proceedings of the 7th International Conference on Enterprise Distributed Object Computing
  • Year:
  • 2003

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper compares two separately developed systemsfor monitoring activities related to business contracts,describes how we integrated them and exploits the lessonslearned from this process to identify a core set ofrequirements for a Business Contract Language(BCL). Concepts in BCL needed for contract monitoringinclude: the expression of coordinated concurrent actions;obliged, permitted and prohibited actions; rich timelinessexpressions such as sliding windows; delegations; policyviolations; contract termination/renewal conditions andreference to external data/events such as change in interestrates. The aim of BCL is to provide sufficient expressivepower to describe contracts, including conditions whichspecify real-time processing, yet be simple enough to retaina human-oriented style for expressing contracts.