Software development

Microprocessor-based systems in safety technology are indispensable today. Unlike with hardware, there is no need to consider wear and tear failures with software. In principle, systematic errors can already occur during the specification or development phase. This means that software errors can always be present in a programme right from the start, even if they only become apparent much later under certain conditions.

The implementation of a sufficient quality standard, taking into account the entire software life cycle and the safety integrity of all safety functions, is an essential feature of the requirements for the development of safety-related software. The software development process and the use of methodologies and error-preventing measures are specified in safety standards such as IEC 61508-3, EN 50128, ISO 26262-6, DO-178B, etc.

• Carrying out SW-FMEA, SW-FTA, SW criticality analyses
• Definition of the operating conditions of the software (memory size, MMU, DMA, CPU type, memory model, time requirements, communication interfaces, etc.)
• Introduction of tools (toolchain) that are directly involved in the SW development process chain (compiler, linker, debugging tools, analysis systems)
• Support with verification and validation planning
• Carrying out reviews, walkthroughs, white box tests, black box tests
• Creation of criteria for testing software (statement coverage, branch coverage, path coverage, condition coverage, statement coverage)