Be the first to like this
The FDA recommends implementing a coding standard during medical device software development. In practice, this means running a static analysis tool to detect any problematic constructs that could lead to problems down the road.
But if you think you can simply download an analyzer and go, you might consider that the FDA requires documented details associated with code quality activities.
What standard are you going to check against? What rules in the analyzer cover the standard? Which rules are you suppressing? The implementation of static analysis is enough to cause headaches, gastrointestinal discomfort, and other side-effects.
This webinar prescribes some static analysis implementation best practices to relieve your FDA compliance symptoms, including:
The benefits of static analysis and what to look for in an analyzer
How to automate static analysis execution
How to integrate static analysis within your software development processes.
How to reduce noise and stop wasting time manually triaging results