Manuel Maarek

dblp:54/236 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 2015
0000-0001-6233-6341ORCID · verified

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 3

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
3 papers
Program verification · 44% Requirements engineering and software design · 36% Programming languages and type systems · 13%
Network and information security
1 paper
Systems and software security · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

Topics — the 3 heaviest of 8, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Program verification
formal proof
0.212015
Improving Predictability, Efficiency and Trust of Model-Based Proof Activity · ICSE (2) 2015
Embedded and real-time systems
model-based design
0.212015
Improving Predictability, Efficiency and Trust of Model-Based Proof Activity · ICSE (2) 2015
Requirements engineering and software design
model-driven engineering
0.112015
Improving Predictability, Efficiency and Trust of Model-Based Proof Activity · ICSE (2) 2015

Methods — techniques the papers use, named apart from their topics

strong typing · 0.4model-based design · 0.4formal methods · 0.4OCaml · 0.4requirements specification · 0.1legal analysis · 0.1
YearPublicationVenuePosition
2015 Avoiding Security Pitfalls with Functional Programming: A Report on the Development of a Secure XML Validator
abstract
While the use of XML is pervading all areas of IT, security challenges arise when XML files are used to transfer security data such as security policies. To tackle this issue, we have developed a lightweight secure XML validator and have chosen to base the development on the strongly typed functional language OCaml. The initial development took place as part of the LaFoSec Study which aimed at investigating the impact of using functional languages for security. We then turned the validator into an industrial application, which was successfully evaluated at EAL4+ level by independent assessors. In this paper, we explain the challenges involved in processing XML data in a critical context, we describe our choices in designing a secure XML validator, and we detail how we used features of functional languages to enforce security requirements.
Damien Doligez, Christèle Faure, Thérèse Hardin, Manuel Maarek
ICSE (2)4
2015 Improving Predictability, Efficiency and Trust of Model-Based Proof Activity
abstract
We report on our industrial experience in using formal methods for the analysis of safety-critical systems developed in a model-based design framework. We first highlight the formal proof workflow devised for the verification and validation of embedded systems developed in Matlab/Simulink. In particular, we show that there is a need to: determine the compatibility of the model to be analysed with the proof engine, establish whether the model facilitates proof convergence or when optimisation is required, and avoid over-specification when specifying the hypotheses constraining the inputs of the model during analysis. We also stress on the importance of having a certain harness over the proof activity and present a set of tools we developed to achieve this purpose. Finally, we give a list of best practices, methods and any necessary tools aiming at guaranteeing the validity of the verification results obtained.
Jean-Frédéric Étienne, Manuel Maarek, Florent Anseaume, Véronique Delebarre
ICSE (2)2
2010 Liability in software engineering: overview of the LISE approach and illustration on a case study
abstract
LISE is a multidisciplinary project involving lawyers and computer scientists with the aim to put forward a set of methods and tools to (1) define software liability in a precise and unambiguous way and (2) establish such liability in case of incident. This paper provides an overview of the overall approach taken in the project based on a case study. The case study illustrates a situation where, in order to reduce legal uncertainties, the parties to a contract wish to include in the agreement specific clauses to define as precisely as possible the share of liabilities between them for the main types of failures of the system.
Daniel Le Métayer, Manuel Maarek, Valérie Viet Triem Tong, Eduardo Mazza, Marie-Laure Potet, Nicolas Craipeau, Stéphane Frénot, Ronan Hardouin
ICSE (1)2