Safety software developed using formal method
CLEARSY is innovative in the packaging of software in terms of guaranteeing both the conformity of the software product and specifications to the customer needs. This warranty is possible due to the use of modelling techniques that allow, starting from the initial documents and exchanges, the creation of specifications verified by a formal method and expressed in a natural language.
This phrase allows the designers to eliminate the ambiguity of the customer requirement analysis, too often considered as developments, and provide a result entirely in line with needs. These specifications then act as the base for development created through techniques adapted for the operational constraints of the software product. CLEARSY offers contractual support to its warranty by a commitment to handle at its expense software changes related to a problem in the development of the code and the changes in these specifications if the problem is linked to a logic fault or ambiguity in the specifications.
The development of safety critical software undertaken by CLEARSY meets the development criteria of SIL2, SIL3, and SIL4 software in terms of IEC 61508 standards and, in particular, standards EN50126, EN50128, and EN50129.
Development of safety software
Because of the use of modeling techniques, CLEARSY is innovative in the development of software packages.
To accomplish this, CLEARSY bases its approach on the entire set of documents provided by the customer, expressed in natural language and including the specifications related to the software product. Formal methods allow the Company to model the latter while guaranteeing its conformity while also adapting it as much as possible to the constraints of the contractor.
Developing safety software involves ensuring its proper operation and the impossibility for the software to execute dangerous actions. It also implies a thorough and rigorous mastery of the software operation.
Therefore, CLEARSY uses its knowledge to meet the highest requirements of safety software through safety instructions developed in a structured, clear, unequivocal, verifiable, testable, and maintainable manner, completely unambiguous as far as the documentation is concerned and at all stages of the development cycle.