A Model for Visual Specification of E-contracts

Martínez, Enrique; D́ıaz, Gregorio; Cambronero, M. Emilia; Schneider, Gerardo

doi:10.1109/scc.2010.32

Cited by 19 publications

(20 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Introduced by Martínez et al [2], C-O Diagrams provide a means for visualising normative texts containing the modalities of obligation, permission and prohibition. They allow the representation of complex clauses describing these norms for different signatories, as well as reparations describing what happens when obligations and prohibitions are not fulfilled.…”

Section: C-o Diagramsmentioning

confidence: 99%

“…-pouring : all of 8 -p o u r E n o u g h C r e di t : when abort is not done and variable paid not less than 10 first pouri ngProce ss : pourCoffee : if chooseCoffee is done machine is required to pour coffee otherwise see refund or pourC offeeMil k : if c h o o s e C o f f e e Mi l k is done machine is required to pour coffee and milk otherwise see refund , then giveChange : if variable paid greater than 10 machine is required to give change 9 -noPour : if variable paid less than 10 machine mustn ' t pour anything 10 -refunding : re fu n dN ot En o ug h : if variable paid less than 10 machine is required to refund money and refundAbort : if abort is done machine is required to refund money 11 refund : machine is required to refund money 6 Related work C-O Diagrams may be seen as a generalisation of CL [9,10,11] in terms of expressivity. 2 In a previous work, Angelov et al introduced a CNL for CL in the framework AnaCon [7]. AnaCon allows for the verification of conflicts (contradictory obligations, permissions and prohibitions) in normative texts using the CLAN tool [12].…”

Section: Classificationmentioning

confidence: 99%

See 1 more Smart Citation

A CNL for Contract-Oriented Diagrams

Camilleri

Paganelli

Schneider

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. We present a first step towards a framework for defining and manipulating normative documents or contracts described as ContractOriented (C-O) Diagrams. These diagrams provide a visual representation for such texts, giving the possibility to express a signatory's obligations, permissions and prohibitions, with or without timing constraints, as well as the penalties resulting from the non-fulfilment of a contract. This work presents a CNL for verbalising C-O Diagrams, a web-based tool allowing editing in this CNL, and another for visualising and manipulating the diagrams interactively. We then show how these proof-ofconcept tools can be used by applying them to a small example.

show abstract

Section: C-o Diagramsmentioning

confidence: 99%

Section: Classificationmentioning

confidence: 99%

A CNL for Contract-Oriented Diagrams

Camilleri

Paganelli

Schneider

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Martinez et al [13] also provides a visual language to compose web services with a particular focus on concepts that are closer to the business analyst vocabulary. Nevertheless they do not address the problem of run-time evolutions that could occur.…”

Section: B Contracts At the Business Layermentioning

confidence: 99%

Controlling the Evolution of Product-Based Collaboration Contracts

Khalfallah¹,

Figay²,

Barhamgi³

et al. 2013

2013 IEEE International Conference on Services Computing

View full text Add to dashboard Cite

The literature on product-based workflow design considers only static collaborative environments where the product model is static and does not change. However the possible evolution of the product model and thus its impact on the collaborative environment are not considered despite the importance of this evolution for innovative product design. As a result the uncontrolled changes can easily break the crossorganizational process that links the different stakeholders in the collaborative environment. In this paper we present a framework that builds the collaboration contract from the product model and supports a controlled evolution of this contract. We leverage this framework by a set of management operations (services) that enable the contract evolution and investigate how a tailoring operation will not impact the executable cross-organizational process unless this process is maintained executable by the workflow engine. These operations are provided as services by a collaborative platform and displayed through a standard-based user interface.

show abstract

“…This idea is supported by many authors in this field, including [11] and [12]. To support the above we have presented in [9] an evaluation of C-O diagrams based on user-based tests, with the purpose of comparing the understandability of both C-O diagrams and textual notations for e-contracts. Results showed, at least in this study, that a visual representation model was more usable than its equivalent textual form.…”

Section: ç 1 Introductionmentioning

confidence: 96%

“…Previously we have introduced C-O diagrams [9], a graphical representation not only for electronic contracts (e-contracts) but also for the specification of any kind of normative text (web service composition behavior, software product lines engineering, requirements engineering, etc.). C-O diagrams allow for the representation of complex clauses describing the obligations, permissions, and prohibitions of different signatories (as defined in deontic logic), as well as reparations describing contractual clauses in cases of non-fulfillment of obligations and prohibitions.…”

Section: ç 1 Introductionmentioning

confidence: 99%

Specification and Verification of Normative Texts Using C-O Diagrams

D́ıaz

Cambronero

Martínez

et al. 2014

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

C-O diagrams have been introduced as a means to have a more visual representation of normative texts and electronic contracts, where it is possible to represent the obligations, permissions and prohibitions of the different signatories, as well as the penalties resulting from non-fulfillment of their obligations and prohibitions. In such diagrams we are also able to represent absolute and relative timing constraints. In this paper we present a formal semantics for C-O diagrams based on timed automata extended with information regarding the satisfaction and violation of clauses in order to represent different deontic modalities. As a proof of concept, we apply our approach to two different case studies, where the method presented here has successfully identified problems in the specification.Index Terms-Normative documents, electronic contracts, deontic logic, formal verification, visual models, timed automata, C-O diagrams Ç 1 INTRODUCTION I N software context, the term contract has been traditionally used as a metaphor to represent limited kinds of "agreements" between software elements at different levels of abstraction. The first use of the term in connection with software programming and design was by Meyer [1], in the context of the language Eiffel (programming-by-contracts, or design-by-contract), and relied on Hoare's notion of pre and post-conditions and invariants. Though this paradigm has proven to be useful for developing object oriented systems, it seems to have shortcomings for novel development paradigms such as service-oriented computing and componentbased development. These new applications have a more involved interaction and therefore require a more sophisticated notion of contracts.As a response, behavioral interfaces have been proposed to capture richer properties more than simple pre and postconditions [2]. With this specifications, it is possible to express contracts concerning the history of events, including causality properties. However, this approach is limited when it comes to contracts containing exceptional behavior, since the focus is mainly on the interaction concerning expected (and prohibited) behavior.In the context of service oriented architectures (SOA), there are several service contract specification languages, such as ebXML [3], WSLA [4], and WS-Agreement [5]. These standardized specification languages suffer from one or more of the following problems: they are restricted to bilateral contracts, lack formal semantics (so it is difficult to reason about them), their treatment of functional behavior is rather limited and the sub-languages used to specify security constraints are usually limited to small application-specific domains. The lack of suitable languages for contracts in the context of SOA is a clear conclusion of the survey [6] where a taxonomy is presented.Some researchers have investigated variants of deontic logic [7] to specify different aspects of software systems. Deontic logic is concerned (among other things) with the formalization of moral and legal obligati...

show abstract

A Model for Visual Specification of E-contracts

Cited by 19 publications

References 17 publications

A CNL for Contract-Oriented Diagrams

A CNL for Contract-Oriented Diagrams

Controlling the Evolution of Product-Based Collaboration Contracts

Specification and Verification of Normative Texts Using C-O Diagrams

Contact Info

Product

Resources

About