Verification & Validation
RAMS Analysis

Its long and consolidated experience acquired in the development of complex software systems allows INTECS to offer specialised services for the analysis and verification of Reliability, Availability, Maintainability e Safety (RAMS) requirements.
Hazard Analysis
An important role is played by Hazard Analysis, which aims at the early identification of possible hazards that can cause the system to exhibit an unsafe behaviour, and to the analysis of risk mitigation measures.

INTECS applies various Hazard Analysis techniques on critical components of several systems for different  applications domain including Space, Avionic, Automotive and Railway Systems.

Hazard Analysis techniques include System-level safety analysis,  Preliminary Hazard Analysis, Hazard Analysis, RAM (Reliability, Availability, Maintainability) parameter evaluation and production of CENELEC Safety Cases.

Software Hazard Analysis
Software Hazard Analysis normally covers all the main Software Life Cycle phases, from the Software Requirements analysis to the Design phase and finally to the Coding phase. 

Among others, techniques that have been widely used are Fault Tree Analysis (FTA) and Failure Mode Effect and Criticality Analysis (FMECA).

For avionic systems the above-mentioned techniques are tailored to carry out the Software Hazard Analysis related to specific systems for “Symbology Display” and for “Control Subsystems” for aircrafts (EFA, etc.).
Avionic methodology complies with the RTCA/DO-178A (Software Considerations in Airborne Systems and Equipment Certification) standards.

Software Hazard Analysis covered the principal phases of the Software lifecycle, from the Software Requirements analysis to the Design phase and finally to the Coding phase.

At each development phase, the criticality of the different parts of the subsystem is assessed and safety recommendations are provided for the subsequent phase, in order to eliminate unsafe behaviour of the software or to mitigate hazardous consequences of possible software failures.