Managing risks related to the obsolescence of safety-critical embedded software verification frameworks
We all want the software in the devices we use to be top quality. However, have you considered what is meant by Software Quality? It is very difficult to articulate a set of criteria that summarises a comprehensive quality metric and software quality is a multidimensional quantity which can be measured in many ways.In this introductory article, Adam Mackay will explore what determines software quality.
Over the last few years, medicine has been a catalyst for driving progress in the innovation of medical devices and treatment plans. Digital technology is becoming embedded in every area of healthcare delivery. Medical devices are becoming more and more complex.
In this blog, Bill Steiniger dives into the importance of utilizing fully tested C and C++ code that is verified to the IEC 62304 standard, as a driver for differentiation and added value in medical devices.
In many business segments, be it transportation, industrial automation or in medical devices, industry leaders have developed finely tuned software code bases over the years. This code tends to consist of many interlocking parts with common dependencies. Small changes in one part of a project can have wide-ranging impacts on other parts of a project.
Maintaining consistent software quality across generations of production code releases is vital to maximizing reliability, functional safety and certification compliance while minimizing liability exposure in the process.
In this blog, Rob Mueller-Albrecht, Cantata Technical Support Engineer of QA Systems, dives into how to avoid frustration and resolve problems efficiently in all phases of software development, verification and certification, it is best to have the orchestra of software professionals work from the same musical arrangement.
In software engineering, we test primarily to diminish risks. Errors are costly, and testing serves as a safety net for the full software system.
However, it is not the only purpose of testing. We can also do testing for understanding, just as software engineers should do when writing a program. And racing drivers do when learning a new track or car.
The parallels between racing and software development may not be immediately evident. However, both require the design and implementation of solid processes to secure success.
This article introduces methods, techniques, and tools to ensure clarity of thinking and implementation during development of project processes.