Extending JML for Modular Specification and Verification of Multi-threaded Programs

Rodríguez, Edwin; Dwyer, Matthew B.; Flanagan, Cormac; Hatcliff, John; Leavens, Gary T.; Robby, .

doi:10.1007/11531142_24

Cited by 46 publications

(62 citation statements)

References 31 publications

(40 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Constraint s χ 1 asks that sit be delayed until Occupied is false. This is expressed using the "when" keyword as in JML's extension for multi-threaded programming [33], though in XCD functional constraints are not allowed to use it. To relate it to JML, one can think of it as a "normal" interaction behaviour, describing a method's acceptable concurrent behaviours.…”

Section: Extending Dbc -Different Contract Typesmentioning

confidence: 99%

Xcd – Modular, Realizable Software Architectures

Kloukinas

Özkaya

2013

Formal Aspects of Component Software

View full text Add to dashboard Cite

Abstract. Connector-Centric Design (XCD) is centred around a new formal architectural description language, focusing mainly on complex connectors. Inspired by Wright and BIP, XCD aims to cleanly separate in a modular manner the high-level functional, interaction, and control system behaviours. This can aid in both increasing the understandability of architectural specifications and the reusability of components and connectors themselves. Through the independent specification of control behaviours, XCD allows designers to experiment more easily with different design decisions early on, without having to modify the functional behaviour specifications (components) or the interaction ones (connectors).At the same time XCD attempts to ease the architectural specification by following (and extending) a Design-by-Contract approach, which is more familiar to software developers than process algebras like CSP or languages like BIP that are closer to synchronous/hardware specification languages. XCD extends Designby-Contract (i) by separating component contracts into functional and interaction sub-contracts, and (ii) by allowing service consumers to specify their own contractual clauses. XCD connector specifications are completely decentralized, foregoing Wright's connector glue, to ensure their realizability by construction.

show abstract

Section: Extending Dbc -Different Contract Typesmentioning

confidence: 99%

Xcd – Modular, Realizable Software Architectures

Kloukinas

Özkaya

2013

Formal Aspects of Component Software

View full text Add to dashboard Cite

show abstract

“…However, modern software requires a specification language that can help integrate techniques from these two disparate camps. A start towards this problem in JML is found in the work of Rodríguez et al [31]. This work uses atomicity to reduce reasoning about concurrent programs to the sequential case.…”

Section: Problems In Specification Language Designmentioning

confidence: 99%

Lessons from the JML Project

Leavens

Clifton

2008

Verified Software: Theories, Tools, Experiments

Self Cite

View full text Add to dashboard Cite

Abstract.To have impact, a grand challenge should provide a way for diverse research to be integrated in a synergistic fashion. Synergy in the JML project comes from a shared specification language, and thus holds several lessons for the verifying compiler grand challenge. An important lesson is that the project should focus considerable resources on specification language design, which still contains many open research problems. Another important lesson is that, to support such a specification language, the project needs to involve groups doing research on extensible compilers and integrated development environments.

show abstract

“…This is partly because JML currently only deals with sequential programs, though there are some research efforts to extend JML to support effective specification of multithreaded programs (Rodríguez et al, 2005).…”

Section: Limitations Of Our Approachmentioning

confidence: 99%

Specifying and checking method call sequences of Java programs

Cheon

Perumandla

2007

Software Qual J

View full text Add to dashboard Cite

Abstract. In a pre and postcondition-style specification, it is difficult to specify the allowed sequences of method calls, referred to as protocols. The protocols are essential properties of reusable object-oriented classes and application frameworks, and the approaches based on the pre and postconditions, such as design by contracts (DBC) and formal behavioral interface specification languages (BISL), are being accepted as a practical and effective tool for describing precise interfaces of (reusable) program modules. We propose a simple extension to the Java Modeling Language (JML), a BISL for Java, to specify protocol properties in an intuitive and concise manner. The key idea of our approach is to separate protocol properties from functional properties written in pre and postconditions and to specify them in a regular expression-like notation. The semantics of our extension is formally defined and provides a foundation for implementing runtime checks. Case studies have been performed to show the effectiveness our approach. We believe that our approach can be adopted by other BISLs.

show abstract

Extending JML for Modular Specification and Verification of Multi-threaded Programs

Cited by 46 publications

References 31 publications

Xcd – Modular, Realizable Software Architectures

Xcd – Modular, Realizable Software Architectures

Lessons from the JML Project

Specifying and checking method call sequences of Java programs

Contact Info

Product

Resources

About