loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Seventh International Enterprise Distributed Object Computing Conference (EDOC'03)
Identifying requirements for Business Contract Language: a Monitoring Perspective
Brisbane, Queensland, Australia
September 16-September 19
ISBN: 0-7695-1994-6
ASCII Text
x 
 
S. Neal, J. Cole, P. F. Linington, Z. Milosevic, S. Gibson, S. Kulkarni, "Identifying requirements for Business Contract Language: a Monitoring Perspective," Enterprise Distributed Object Computing Conference, IEEE International, pp. 50, Seventh International Enterprise Distributed Object Computing Conference (EDOC'03), 2003.
 
 
BibTex
x
 
@article{ 10.1109/EDOC.2003.1233837,
author = {S. Neal and J. Cole and P. F. Linington and Z. Milosevic and S. Gibson and S. Kulkarni},
title = {Identifying requirements for Business Contract Language: a Monitoring Perspective},
journal ={Enterprise Distributed Object Computing Conference, IEEE International},
volume = {0},
year = {2003},
isbn = {0-7695-1994-6},
pages = {50},
doi = {http://doi.ieeecomputersociety.org/10.1109/EDOC.2003.1233837},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Enterprise Distributed Object Computing Conference, IEEE International
TI - Identifying requirements for Business Contract Language: a Monitoring Perspective
SN - 0-7695-1994-6
SP
EP
A1 - S. Neal,
A1 - J. Cole,
A1 - P. F. Linington,
A1 - Z. Milosevic,
A1 - S. Gibson,
A1 - S. Kulkarni,
PY - 2003
KW - null
VL - 0
JA - Enterprise Distributed Object Computing Conference, IEEE International
ER -
 
S. Neal, University of Kent
J. Cole, University of Queensland
P. F. Linington, University of Kent
Z. Milosevic, University of Queensland
S. Gibson, University of Queensland
This paper compares two separately developed systems for monitoring activities related to business contracts, describes how we integrated them and exploits the lessons learned from this process to identify a core set of requirements for a Business Contract Language (BCL). Concepts in BCL needed for contract monitoring include: the expression of coordinated concurrent actions; obliged, permitted and prohibited actions; rich timeliness expressions such as sliding windows; delegations; policy violations; contract termination/renewal conditions and reference to external data/events such as change in interest rates. The aim of BCL is to provide sufficient expressive power to describe contracts, including conditions which specify real-time processing, yet be simple enough to retain a human-oriented style for expressing contracts.
Citation:
S. Neal, J. Cole, P. F. Linington, Z. Milosevic, S. Gibson, S. Kulkarni, "Identifying requirements for Business Contract Language: a Monitoring Perspective," edoc, pp.50, Seventh International Enterprise Distributed Object Computing Conference (EDOC'03), 2003
Usage of this product signifies your acceptance of the Terms of Use.