Adopt a zero defect strategy
By adopting a zero defect strategy, and using our best in class tools, you can avoiding costly testing cycles, pay down technical debt, reduce time to market and avoid costly recalls and damage to your brand reputation and customer satisfaction.
Whether you are building an IoT device, a car infotainment system, control systems or deploying a business critical application our Static Analysis, Code Coverage, Dependency Analysis and Application Testing tools will help you reduce vulnerabilities and defects throughout the development lifecycle.
It’s well known that finding a defect in a product is more costly to fix in terms of effort and time the later it is found. At Valbrio we help you adopt a zero defect, zero vulnerability approach to software development, with what we consider to be best of breed partners and products, such as Grammatech’s CodeSonar, Verifysoft’s Testwell CTC++, Oracle’s Applications Test Suite (OATS) and Lattix, providing you with great products coupled with local technical expertise and services.
The incraesing amount of code in vehicles is increasing and the impact of software errors has raised the stakes for developers. The standards ISO 26262 and IEC 61508 have strict requirements concerning verification and validation for software development in the automotive and transport industries and the MISRA (Motor Industry Software Reliability Association) standard was created to facilitate best practices for the development of safety-critical software in vehicles.
With the Internet of Things (IoT) and Machine-to-machine (M2M) communications, the industry is facing new challenges in all markets, and with the continuous discovery of new vulnerabilities in more connected systems and sensors, customers need software systems to be secure, safe, and reliable out-of-the-box. Software errors are costly, with potential brand damage and security just part of the issue. To minimise risks the standard IEC 61508 is widely used, together with MISRA, in industrial automation where safety, security and reliability are vital.
DEFENCE AND AEROSPACE
Safety and security-critical software for aerospace or defence applications need to be developed with highest quality. The high requirements for both safety and security continue to rise. The standard DO-178C has strict requirements concerning verification and validation for software development in the avionics industry. Safety standards have also been adopted in other security and safety-critical markets such as defence, even though certifications are not mandatory.
Whether the target application is deployed trackside or onboard, software for railway and mass transit applications must have high levels of reliability, safety, security and system integrity. In order to achieve this requirements, a rigorous software-development process including usage of software testing tools is mandatory.The standards IEC 62279/ EN 50128 specify procedures and technical requirements for the development of programmable electronic systems which are used in railway control and protection applications.
Software in medical devices plays a significant role and software quality and risk management are essential in order to develop safe software. Medical devices are expected to be developed with good engineering practices and all companies active in the medical device market must ensure the highest quality of software development. The IEC/ISO 62304 standard defines a risk and quality driven software development process for the development of medical devices.
ENERGY & UTILITES
Software bugs can result in financial losses and disturbance or damage of power plants or worse still injuries or fatalities. For the development of programmable devices with safety functions the “general” standard IEC 61508 can be used. The standard IEC 61226 applies to nuclear power plants. IEC 60880 applies to the highest category A. The levels B and C are handled by the standard IEC 62138. Both standards (IEC 61508 and IEC 60880) require the usage of coding standards like MISRA.