Eiffel: the language
The B-book: assigning programs to meanings
The B-book: assigning programs to meanings
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Building Reliable Component-Based Software Systems
Building Reliable Component-Based Software Systems
Ten Commandments of Formal Methods
Computer
IEEE Software
Coming and Going from UML to B: A Proposal to Support Traceability in Rigorous IS Development
ZB '02 Proceedings of the 2nd International Conference of B and Z Users on Formal Specification and Development in Z and B
Composition and Refinement in the B-Method
B '98 Proceedings of the Second International B Conference on Recent Advances in the Development and Use of the B Method
Extracting implicit contracts from .NET libraries
OOPSLA '02 Companion of the 17th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
BRILLANT: An Open Source and XML-based platform for Rigourous Software Development
SEFM '05 Proceedings of the Third IEEE International Conference on Software Engineering and Formal Methods
Safety-Oriented Design of Component Assemblies using Safety Interfaces
Electronic Notes in Theoretical Computer Science (ENTCS)
Hi-index | 0.00 |
The aim of this paper is to merge two approaches of software development: the component approach and the formal development approach. Developing software components is now a technique widely used by the software industry. These two approaches are not so distant if we consider Bertrand Meyer's opinion: it is more complicated to reuse a component without contracts. One of the difficulties with the design by contract approach is to find the contracts. This difficulty can be removed by the use of the B method. In the B method, the software properties (the contracts) are expressed in the specifications. We present in this paper an approach to generate code in the spirit of the component approach from B specifications.