Came across this website that has some very detailed “commandments” for software development at their company. A surprisingly lengthy list of dos and don’ts related to coding, testing, designing, estimating, and managing the software lifecycle. Does your company have anything written? I often find that each company has some “lore” – some practices that characterize their approach creating high quality software. You can view this list at https://www.codethink.co.uk/commandments.html
Back in 2006, the IEEE Computer Journal published an article titled: “The Power of 10: Rules for Developing Safety- Critical Code” by Gerard J. Holzmann of the NASA/JPL Laboratory for Reliable Software. You can view our post on that article here.
Do you have practices that you believe every medical device software team should be using? Leave us a message and let us know if we can reference your practice or method and use your name in a future article we are planning on “robust software practices.”
