Formalization of Component Substitutability

Belguidoum, Meriem; Dagnat, Fabien

doi:10.1016/j.entcs.2008.06.022

Cited by 16 publications

(5 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several techniques ensure the substitutability between components [ZW97,BD08]. These approaches are built upon the substitution principle of Liskov [LW94] in the context of object-oriented programming.…”

Section: Substitutability Checkingmentioning

confidence: 99%

A verification-driven framework for iterative design of controllers

et al. 2019

View full text Add to dashboard Cite

Controllers often are large and complex reactive software systems and thus they typically cannot be developed as monolithic products. Instead, they are usually comprised of multiple components that interact to provide the desired functionality. Components themselves can be complex and in turn be decomposed into multiple sub-components. Designing such systems is complicated and must follow systematic approaches, based on recursive decomposition strategies that yield a modular structure. This paper proposes FIDDle-a comprehensive verification-driven framework which provides support for designers during development. FIDDle supports hierarchical decomposition of components into sub-components through formal specification in terms of pre-and post-conditions as well as independent development, reuse and verification of sub-components. The framework allows the development of an initial, partially specified design of the controller, in which certain components, yet to be defined, are precisely identified. These components can be associated with pre-and post-conditions, i.e., a contract, that can be distributed to third-party developers. The framework ensures that if the components are compliant with their contracts, they can be safely integrated into the initial partial design without additional rework. As a result, FIDDle supports an iterative design process and guarantees correctness of the system at any step of development. We evaluated the effectiveness of FIDDle in supporting an iterative and incremental development of components using the K9 Mars Rover example developed at NASA Ames. This can be considered as an initial, yet substantive, validation of the approach in a realistic setting. We also assessed the scalability of FIDDle by comparing its efficiency with the classical model checkers implemented within the LTSA toolset. Results show that FIDDle scales as well as classical model checking as the number of the states of the components under development and their environments grow.

show abstract

Section: Substitutability Checkingmentioning

confidence: 99%

A verification-driven framework for iterative design of controllers

et al. 2019

View full text Add to dashboard Cite

show abstract

“…Those dimensions are (1) what is changing, (2) where the change is applied and (3) how the respective code is changed.…”

Section: Methodsmentioning

confidence: 99%

“…Various definitions of compatibility related to software components exist, both in the research [8,2,48,5] and the technical [19,34,33] literature, mostly dealing with the issue of correct replacement and interoperability.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

API Evolution and Compatibility: A Data Corpus and Tool Evaluation.

Jezek¹,

Dietrich²

2017

JOT

View full text Add to dashboard Cite

The development of software components with independent release cycles is nowadays widely supported by multiple languages and frameworks. A critical feature of any such platform is to safeguard composition by ensuring backward compatibility of substituted components. In recent years, some tooling has been developed to help developers and DevOps engineers to establish whether components are backward compatible by means of static analysis. We investigate the state of the art in this space by benchmarking such tools for Java. For this purpose, we have developed a compact benchmark data set of less than 200KB. Using this dataset, we study possible API changes of Java libraries, and whether the tools investigated can detect them. We find that only a small number of tools suitable to analyse API evolution exist. Those tools are only infrequently maintained by small communities. All tools investigated have some shortcomings in that they fail to detect certain API incompatibilities.

show abstract

“…The two first challenges are addressed in a previous work (Belguidoum and Dagnat 2007), indeed, we have proposed a formal description of component dependencies specifying the precise relation between each provided service and its requirement in the same component. We proposed a predicate logic based framework for component deployment to ensure the success and the safety of component installation, deinstallation (Belguidoum and Dagnat 2007) and substitution (Belguidoum and Dagnat 2008). However, this framework has some limitations when applied to dynamic, concurrent and distributed systems.…”

Section: Introductionmentioning

confidence: 99%

Toward a rewriting logic framework for safe and distributed component installation

Belguidoum

Belala

Latreche

2011

Electronic Workshops in Computing

Self Cite

View full text Add to dashboard Cite

Traditionally, software components are developed independently and often considered as black boxes. However, they might be dependent from each other at assembly and deployment stages and used by a third party in various environments. In a previous work (Belguidoum and Dagnat 2007), we have proposed an intra-dependency language and a predicate logic based framework for safe component deployment. In this paper, we aim to extend this work to take into account dynamic changes of concurrent and distributed systems in installation phase and overcome some predicate logic limitations. Therefore, we propose an integration of predicate logic based framework within a rewriting logic based framework. Finally, we execute it in Maude which is a high-performance implementation of rewriting logic enabling both the deployment execution and its formal analysis. We show the relevance of the Maude based deployment approach relating to the interesting features of Maude such as: genericity, concurrency, distribution and formal tools.

show abstract

Formalization of Component Substitutability

Cited by 16 publications

References 7 publications

A verification-driven framework for iterative design of controllers

A verification-driven framework for iterative design of controllers

API Evolution and Compatibility: A Data Corpus and Tool Evaluation.

Toward a rewriting logic framework for safe and distributed component installation

Contact Info

Product

Resources

About