Contract Aware Components, 10 years after

Beugnard, Antoine; Jézéquel, Jean-Marc; Plouzeau, Noël

doi:10.4204/eptcs.37.1

Cited by 12 publications

(4 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…At first glance, computational contracts (Scholliers et al, 2015) look similar to higherorder temporal contracts. But, computational contracts go far beyond any classical contract classification scheme (Beugnard et al, 1999(Beugnard et al, , 2010, providing unprecedented power and imposing a similarly high cost. A computational contract system empowers programmers to impose arbitrary restrictions on components from the outside and in a post hoc manner.…”

Section: Higher-order Contracts Specificallymentioning

confidence: 99%

Trace contracts

MOY,

FELLEISEN

2023

J. Funct. Prog.

View full text Add to dashboard Cite

Behavioral software contracts allow programmers to strengthen the obligations and promises that they express with conventional types. They lack expressive power, though, when it comes to invariants that hold across several function calls. Trace contracts narrow this expressiveness gap. A trace contract is a predicate over the sequence of values that flow through function calls and returns. This paper presents a principled design, an implementation, and an evaluation of trace contracts.

show abstract

Section: Higher-order Contracts Specificallymentioning

confidence: 99%

Trace contracts

MOY,

FELLEISEN

2023

J. Funct. Prog.

View full text Add to dashboard Cite

show abstract

“…Other researchers [5,6] have sought to define a rule interchange language for the legal domain. There are also efforts to build common taxonomies [1,9,10,55] of financial terms and events that can be used to specify events and actions in the contract automation process.…”

Section: Related Workmentioning

confidence: 99%

FCL: A Formal Language for Writing Contracts

Farmer

2017

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Contracts are legally enforceable agreements between two or more parties. The agreements can contain temporally based conditions, such as actions taken by the contract parties or events that happen, that trigger changes to the state of the contract when the conditions become true. Since the structure of these conditions can be very complex, it can be difficult to write contracts in a natural language in a clear and unambiguous way. A better approach is to have a formal language with a precise semantics to represent contracts. Contracts expressed in such a language have a mathematically precise meaning and can be written, analyzed, and manipulated by software.This thesis presents fcl, a formal language with a precise semantics for writing general contracts that may depend on temporally based conditions. Motivated by carefully selected examples of contracts, we derive a set of desirable requirements that a formal language of contracts should support. Based on the requirements, we clearly define the notion of contract and address what it means to fulfill or breach a contract. We present the formal syntax and semantics of fcl. We also successfully formalize different kinds of contracts in fcl and develop a reasoning system for fcl.iii First and foremost, I would like to express my gratitude to my academic supervisor Dr. William M. Farmer for his unwavering support, invaluable guidance, and continuous encouragement throughout the development and advancement of my research studies and my life. My special thanks go to the members of my supervisory committee: Dr. Jacques Carette, Dr. Ridha Khedri, and Dr. Tom Maibaum for all of their valuable advices and thoughtful comments on my research work. I also appreciate the help and moral support from all of other individuals whom I have interacted with throughout my graduate studies. Furthermore, I want to extend my sincere thanks to the Natural Sciences and Engineering Research Council of Canada (NSERC) and McMaster University graduate scholarship which have provided the financial support during my doctoral studies.Last, but certainly not least, I would like to thank my dear family and friends from the bottom of my heart for all of their love, support, and encouragement.

show abstract

“…It was first implemented under the name of "design by contract" in the Eiffel language (Meyer, 1992). Beugnard, Jezequel et al (2010) propose four levels of contracts for components, being syntactical, behavioral, synchronization and quality-ofservice. The authors also presented a survey after 10 years and found that contract-aware components are becoming mainstream in several domains such as embedded systems and Service-Oriented architecture (Beugnard et al,2010).…”

Section: Related Workmentioning

confidence: 99%

“…Beugnard, Jezequel et al (2010) propose four levels of contracts for components, being syntactical, behavioral, synchronization and quality-ofservice. The authors also presented a survey after 10 years and found that contract-aware components are becoming mainstream in several domains such as embedded systems and Service-Oriented architecture (Beugnard et al,2010). These practices do enhance integrity, reliability and hence accountability of components and services.…”

Section: Related Workmentioning

confidence: 99%

Modeling Accountable Cloud Services Based on Dynamic Logic for Accountability

Zou

Wang

Orgun

2015

International Journal of Web Services Research

View full text Add to dashboard Cite

Cloud computing services have been increasingly considered by businesses as a viable option for reducing IT expenditure. However, there are often associated problems with unmanaged accountability. This paper first analyses the accountability properties of a cloud service and then proposes the accountable cloud service (ACS) model to address those problems. In addition, the authors argue that from an accountability perspective a cloud service is a proactive system that needs to be modeled differently from the traditional reactive systems. They extend traditional structural operational semantics to cater for modeling of actors as well as scenarios of inaction and exception in state transitions. This leads to the creation of a new form of a process algebra called Accountable Process Algebra (APA). They also propose an Obligation Flow Diagram (OFD) as a simple method for conflict resolution and verification for the ACS model. The ACS model enables obligation specification, validation, decomposition, machine-interpretation, monitoring and reasoning, and ultimately facilitates accountability in cloud service consumption. Using Amazon S3 service as a case study, they show how to address those known accountability problems by using our ACS model. Finally the authors discuss the applicability of their model to cloud services in general.

show abstract

Contract Aware Components, 10 years after

Cited by 12 publications

References 19 publications

Trace contracts

Trace contracts

FCL: A Formal Language for Writing Contracts

Modeling Accountable Cloud Services Based on Dynamic Logic for Accountability

Contact Info

Product

Resources

About