SCOOP – A Contract-Based Concurrent Object-Oriented Programming Model

Morandi, Benjamin; Bauer, Sebastian; Meyer, Bertrand

doi:10.1007/978-3-642-13010-6_3

Cited by 10 publications

(3 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…preconditions and postconditions have been added to methods, and invariants have been added to classes. Of the interesting things, Eiffel offers the generation of random tests under the contract and introduces its own multithreading model based on contracts [42]. However, for an average developer, learning new languages just because the contracts can be specified there does not seem to make sense.…”

Section: Hoare Triples Deductive Verification Code Contractsmentioning

confidence: 99%

Teaching the Discipline "Software Testing and Verification" to Future Programmers

Staroletov¹

2022

System Informatics

View full text Add to dashboard Cite

An introduction to the study of quality assurance methods is essential to understand the development of complex and reliable software. Nevertheless, the modern software industry requires the earliest possible launch of a product to the market, and the methods of formal specification and verification of programs do not find much interest among the broad mass of future programmers.In this article, the author proposes to organize a dedicated discipline and conduct seamless training in testing, test-driven development and formal verification using various methods for writing program specifications and using software tools for program checking. The purpose of discussing discipline is to redefine the attitude of future developers towards software quality, its specification and automatic checking. Within the framework of this article, the author considers his own discipline, which combines two courses -software testing and formal verification. The proposed approach of teaching is primarily practice-oriented and includes teamwork. In accordance with the current curriculum, the discipline is held in the last semester for undergraduate students (4th course). The material of the article is based on the author's five-year experience of teaching the subject to students of the Software Engineering specialty. The article offers rather voluminous and descriptive examples of specifications and programs in model languages.

show abstract

Section: Hoare Triples Deductive Verification Code Contractsmentioning

confidence: 99%

Teaching the Discipline "Software Testing and Verification" to Future Programmers

Staroletov¹

2022

System Informatics

View full text Add to dashboard Cite

show abstract

“…However, while Eiffel contract-checking contributed to improving the reliability of sequential software, it has unintended effects on concurrent programs. This limitation has been solved in SCOOP [94], a concurrency model for Eiffel. Additionally, user-specified contracts have also been used in automatic unit-test generation [91] and to provide autogenerated fixes for failing program fragments [126].…”

Section: Design By Contractmentioning

confidence: 99%

Exploring stream parallel patterns in distributed MPI environments

et al. 2019

View full text Add to dashboard Cite

En primer lugar, a mis padres. Os debo todo lo que soy y seré. Gracias por el cuidado y educación recibidos, por los buenos (y malos) momentos, por aquellos días de piscina en Playa de Madrid, por las barbacoas en la Fundación del Lesionado Medular/ASPAYM Madrid, por las comidas en "La Bodeguita" y en el Centro Municipal de Mayores Ascao. Gracias a vosotros aprendí a ser fuerte. A mamá, porque me enseñaste lo más importante, a sonreir a pesar de la adversidad, y otras cosas de menor importancia, como mantener un hogar. A papá, por enseñarme gran parte de lo que sé, el equilibrio, e iluminarme el camino; aunque fuera de forma accidental, sin tí, mi vocación sería otra. Nunca os lo podré agradecer tanto como lo merecisteis. D.E.P.En segundo lugar, a mis compañeros de trabajo: Manu, Javi Doc, y David. Por todos los momentos compartidos en el laboratorio y fuera de él; por ayudarme y presionarme para que trabajara. Sin vosotros, dudo que estuviera escribiendo estas líneas ahora. A mis compañeros de laboratorio: Guille, Mario, Javi Prieto, y José Cabrero, por las charlas y momentos de risa. A Alejandro Calderón, que siempre ha estado ahí para escucharme y echar una mano. A José Daniel, por darme la oportunadad de trabajar en el grupo y por estar ahí en los momentos difíciles que últimamente han acontecido. También a mis compañeros de trabajo del CERN: Enric, Stephan, Guilherme, Bertrand, Javi, Emmanouil "Manos", y especialmente a Axel, Jakob y Pere, por acogerme en ROOT.No voy a terminar sin mencionar a las personas que siempre estuvieron ahí (no, no me olvido de vosotros): a mi hermano, a Úrsula, a mi tía Paloma y mi tío Matías, a mi primo "el niño".

show abstract

“…The main idea of SCOOP [9,10,12] is to simplify the writing of correct concurrent programs, by allowing developers to use familiar concepts from object-oriented programming while protecting them from common concurrency errors such as data races. Empirical evidence supports the claim that SCOOP indeed simplifies reasoning about concurrent programs as opposed to more established models [11].…”

Section: Scoopmentioning

confidence: 99%

Concurrent Object-Oriented Development with Behavioral Design Patterns

Morandi

West

Nanz

et al. 2013

Software Architecture

Self Cite

View full text Add to dashboard Cite

Abstract. Architectural modeling using the Unified Modeling Language (UML) can support the development of concurrent applications, but the problem of mapping the model to a concurrent implementation remains. This paper defines a scheme to map concurrent UML designs to a concurrent object-oriented program. Using the COMET method for the architectural design of concurrent object-oriented systems, each component and connector is annotated with a stereotype indicating its behavioral design pattern. For each of these patterns, a reference implementation is provided using SCOOP, a concurrent object-oriented programming model. Given the strong execution guarantees of the SCOOP model, which is free of data races by construction, this development method eliminates a source of intricate concurrent programming errors.

show abstract

SCOOP – A Contract-Based Concurrent Object-Oriented Programming Model

Cited by 10 publications

References 6 publications

Teaching the Discipline "Software Testing and Verification" to Future Programmers

Teaching the Discipline "Software Testing and Verification" to Future Programmers

Exploring stream parallel patterns in distributed MPI environments

Concurrent Object-Oriented Development with Behavioral Design Patterns

Contact Info

Product

Resources

About