Almost all standards related to the functional safety of systems/equipment and machinery dedicate at least one section to the Software. The IEC 61508 is the standard that best defines the activities, the methodologies, the techniques and the requirements needed to achieve a "safe" software, that is, a type of software that is able to reliably operate in critical safety functionality, and whose failure can produce catastrophic consequences such as serious injury, loss of life, damage to material goods, economic damage, or leaks in the safety of the system/apparatus or machine.
HINTSW - T & T Systems, for the realization of a software whose strength and reliability is to reduce the probability of failure at a level compatible with that required for critical security application, adopts the development model proposed by the IEC 61508- 3 based on a particular software life cycle, called the safety of the software life cycle. This life cycle rigorously establishes the business methodologies, the techniques and the documentation to be realized so that the software can be reasonably considered safe. The first phase provided for in the security life cycle adopted by HINTSW - T & T Systems is the phase of design and planning of software.
During the design and planning of the SW, HINTSW - T & T Systems is able to perform the following tasks:
The main standards for the functional safety prescribe the adoption of a particular software life cycle, called "the software security lifecycle."
The requirements of this cycle cover all aspects involved in the management of a software product, the processes of "Quality Assurance", the modification and maintenance procedures; from the methods of analysis to the testing techniques. As for software development, the standards related to safety almost always suggest to adopt the so-called "V" model.
The V lifecycle model is a well-structured method, in which each phase is implemented starting from the documentation produced in the previous step, and starts from the principle that the procedures for checking the conformity of the software with respect to the specifications, must be executed coming from the design phases.