Home > Publications
Home University of Twente
Prospective Students
Intranet (internal)

EEMCS EPrints Service

27827 RERS 2016: Parallel and Sequential Benchmarks with Focus on LTL Verification
Home Policy Brochure Browse Search User Area Contact Help

Geske, M. and Jasper, M. and Steffen, B. and Howar, F. and Schordan, M. and van de Pol, J.C. (2016) RERS 2016: Parallel and Sequential Benchmarks with Focus on LTL Verification. In: Proceedings of the 7th International Symposium on Leveraging Applications of Formal Methods, Verification and Validation (II), ISoLA 2016, 10-14 Oct 2016, Corfu, Greece. pp. 787-803. Lecture Notes in Computer Science 9953. Springer Verlag. ISSN 0302-9743 ISBN 978-3-319-47168-6

Full text available as:

PDF (Publisher's version)

798 Kb
PDF (Author's version)

637 Kb

Official URL:


The 5th challenge of Rigorous Examination of Reactive Systems (RERS 2016) once again provided generated and tailored benchmarks suited for comparing the effectiveness of automatic software verifiers. RERS is the only software verification challenge that features problems with linear temporal logic (LTL) properties in larger sizes that are available in different programming languages. This paper describes the revised rules and the refined profile of the challenge, which lowers the entry hurdle for new participants. The challenge format with its three tracks, their benchmarks, and the related LTL and reachability properties are explained. Special emphasis is put on changes that were implemented in RERS - compared to former RERS challenges. The competition comprised 18 sequential and 20 parallel benchmarks. The 20 benchmarks from the new parallel track feature LTL properties and a compact representation as labeled transition systems and Promela code.

Item Type:Conference or Workshop Paper (Full Paper, Talk)
Research Group:EWI-FMT: Formal Methods and Tools
Research Program:CTIT-General
Research Project:3TU.BSR: Big Software on the Run
ID Code:27827
Deposited On:20 April 2017
More Information:statistics

Export this item as:

To correct this item please ask your editor

Repository Staff Only: edit this item