To content | To menu | To search
Monday 21 January 2013
By Mitch on Monday 21 January 2013, 15:34 - Standards
In the last two posts, we've seen what a software unit is, and when to do software detailed design, according to IEC 62304 and FDA Guidances.
Friday 7 December 2012
By Mitch on Friday 7 December 2012, 12:45 - Processes
In my last article, I talked about the most classical methods used to verify software: human testing (driven by test cases or not) and unit tests. I was about to talk about static analysis, that I place at a higher level of complexity in the list of verification methods, but I have to say a bit more about unit tests.
Friday 28 September 2012
By Mitch on Friday 28 September 2012, 12:10 - Misc
In two previous articles, I talked about the differences of bugs, software failures, and risks.
I left the discussion unfinished about the probability of occurence of a software failure or a defect.
I think that assessing the probability of occurence of a software failure is a hot subject. I've already seen many contradictory comments on this subject. It's also a hot subject for software manufacturers that are not well used to risk assessment.
Friday 6 July 2012
By Mitch on Friday 6 July 2012, 13:17 - Processes
Are agile methods compatible with the constraints of development set by IEC
62304 standard of class C software?
After a
series of three posts about agile methods and risks analysis. I focus in
this post on IEC 62304 class C critical software.