A Systematic Mapping Study on Contract-based Software Design for Dependable Systems

TL;DR

This systematic mapping study reviews contract-based design (CbD) in software engineering, highlighting its role in creating dependable systems, analyzing existing research, and identifying future research directions to enhance software dependability.

Contribution

The paper provides a comprehensive overview of CbD in dependable software systems, analyzing 288 studies to identify research gaps and future opportunities.

Findings

CbD enhances software dependability through modular design.

Research on CbD spans multiple domains with varying maturity levels.

Identifies key gaps and future research directions in CbD for dependable systems.

Abstract

Background: Contract-based Design (CbD) is a valuable methodology for software design that allows annotation of code and architectural components with contracts, thereby enhancing clarity and reliability in software development. It establishes rules that outline the behaviour of software components and their interfaces and interactions. This modular approach enables the design process to be segmented into smaller, independently developed, tested, and verified system components, ultimately leading to more robust and dependable software. Aim: Despite the significance and well-established theoretical background of CbD, there is a need for a comprehensive systematic mapping study for reliable software systems. Our study provides an evidence-based overview of a method and demonstrates its practical feasibility. Method: To conduct this study, we systematically searched three different databases using specially formulated queries, which initially yielded 1,221 primary studies. After voting, we focused on 288 primary studies for more detailed analysis. Finally, a collaborative review allowed us to gather relevant evidence and information to address our research questions. Results: Our findings suggest potential avenues for future research trajectories in CbD, emphasising its role in improving the dependability of software systems. We highlight maturity levels across different domains and identify areas that may benefit from further research. Conclusion: Although CbD is a well-established software design approach, a more comprehensive literature review is needed to clarify its theoretical state about dependable systems. Our study addresses this gap by providing a detailed overview of CbD from various perspectives, identifying key gaps, and suggesting future research directions.